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

Default note editor setting if changed will change all previous notes #413

Open
nauxnim opened this Issue Jan 4, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@nauxnim
Copy link

nauxnim commented Jan 4, 2019

If a note was made with the default editor set to let's say Plus editor (I didn't try on other editors) but after creating an even newer note and clicked Undefault for the editor, the previous note will lose its editor preference and show the note in Plain editor when I do not set any new default editors.

How to produce:

  1. set the default note editor to Plus Editor,
  2. made a few notes, type some stuff
  3. make another new note and set Undefault for Plus Editor
  4. click back to view previous notes,

The result is that the previous notes are no longer in Plus editor and are in Plain editor, showing
https://imgur.com/u3wJGRQ

Is it possible to make it such that notes made with editors that are set as default will not revert back to Plain editor if the user undefaults in the future?
Like if I use Plus editor as default for Note 1 to Note 5, then for Note 6 I made undefault to Plain again, the Note 1 to Note 5 will still be in Plus editor. Currently on my end it is not the case, and I'm not sure if it is intended or not, hmmm.

@mobitar

This comment has been minimized.

Copy link
Member

mobitar commented Jan 4, 2019

Hmm..currently, what you're seeing is the intended behavior. When you have a default editor set, it creates a "soft" association on notes created with that editor. If you undefault and come back to the note, it will not have a hard reference to the editor, so it will resort to either your current default or plain editor.

Although, I can see the usefulness of the behavior you describe. I'll consider this for a future update.

@nauxnim

This comment has been minimized.

Copy link

nauxnim commented Jan 4, 2019

I see! Thanks for taking it into consideration.

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