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.

Sign up for GitHub

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

Jump to bottom

Parser settings always setting default options when loading settings. #804

Closed
vsch opened this issue Dec 28, 2019 · 1 comment
Closed

Parser settings always setting default options when loading settings. #804

vsch opened this issue Dec 28, 2019 · 1 comment
Labels
bug fixed for next release fixed :)
Milestone
V 2.9.11

Comments

@vsch
Copy link
Owner

vsch commented Dec 28, 2019 •
edited
Loading

Version 2.9.10 bug. Parser settings reduction to only include set options missed the code which set missing options when loading settings.

This causes parser settings to always have default parser settings turned on.
@vsch vsch added this to the V 2.9.11 milestone Dec 28, 2019
@vsch
Copy link
Owner Author

vsch commented Dec 28, 2019

Let me know if you are affected by this bug. I can make an EAP release with the fix.

@vsch vsch changed the title Parser settings always setting Anchor Links and GitHub Table Rendering options Parser settings always setting default options when loading settings. Dec 28, 2019
vsch added a commit that referenced this issue Dec 29, 2019
@vsch
release 2.9.11
0d72964 
* Fix settings related bugs

  * Fix: [#804, Parser settings always setting default options when loading settings.]
  * Fix: profile settings could be deleted if markdown code style settings changed and applied
    if profiles pane was opened before changing markdown code style.
  * Fix: changing profiles and applying would cause export on settings change to be triggered
    for every changed profile, instead of once for all changes.
  * Fix: wrap on typing caret jumping to end of next line if typing replaces selection.
@vsch vsch added the fixed :) label Dec 31, 2019
@vsch vsch closed this as completed Dec 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug fixed for next release fixed :)
Projects
None yet
Milestone
V 2.9.11
Development

No branches or pull requests
1 participant
@vsch