Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatic filenames contain emojis #684

Closed
jsosulski opened this issue Jun 7, 2019 · 1 comment
Closed

Automatic filenames contain emojis #684

jsosulski opened this issue Jun 7, 2019 · 1 comment

Comments

@jsosulski
Copy link

  • OS Version: Ubuntu 18.04
  • Notable Version: 1.5.1

Current behavior

Filenames contain emojis that are used in the title. While this looks quite interesting, especially in a terminal, it is rather hard to access files this way when they start with an emoji... 😅

image

Furthermore, it seems dropbox is unable to sync files containing emojis in their path except the keyboard emoji.

image

Expected behavior

Emojis should be omitted from filenames if possible.

@fabiospampinato
Copy link
Member

Emojis should be omitted from filenames if possible.

IMHO the only characters that should be omitted from titles are disallowed characters under commonly used file systems (✅) and characters used for Markdown formatting (✅), since Markdown isn't rendered in titles/filenames.

Emoji fall under neither of those categories (we are actually rendering things like :joy: to the actual corresponding emoji for consistency though), so I don't think they should be removed.

it is rather hard to access files this way when they start with an emoji... 😅

It will become easier once we have a CLI #667, but you can also fix that today by searching for your notes via something like fzf (highly recommended).

Furthermore, it seems dropbox is unable to sync files containing emojis in their path except the keyboard emoji.

This sounds weird to me, I don't see why they would make an exception for the keyboard emoji 🤨 Plus if they are unable to synchronize those kinds of files IMHO the problem is on their side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants