fsnotes: [BUG] Pasting images results in various buggy outcomes

One thing really blocking me from 100% leaving Evernote behind is working with images.

It would be so great to be able to hit ⌘V and have the editor do these things silently behind the scenes:

  1. save the PNG data from the clipboard to a {guid}.png file in an /i folder at the root level of local (synced) storage
  2. create the relative markdown code to link the image in. E.g. ![](/i/16ac95ce-1edd-483b-86d4-3f728b00d01f.png)
  3. paste this code into the editor at the cursor location

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 16 (9 by maintainers)

Commits related to this issue

Most upvoted comments

Ah, yes, it’s working only on iOS at this moment. Will be implemented in next release 🤝

Another bug:

  1. make new note (note1) in Folder1
  2. paste image
  3. FSNotes creates /Folder1/i/1.jpg and links it
  4. now, make note (note2) in Folder2
  5. paste image
  6. FSNotes creates /i/1.jpg as well (in /Folder2/i/...)
  7. now, move note2 into Folder1…
  8. poof, images are gone

I think it is a bad idea to use such a basic naming scheme (1, 2, 3…). It should use GUID instead, tracked internally to avoid any duplication. That way, when note is moved, image can move with it as well, and keep folder structure correct and all links will still work, no risk of overwriting or collision.

Keep it here I think