-
Notifications
You must be signed in to change notification settings - Fork 48
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
Need to redefine the entire "sublime-setting" default configuration to use custom configuration #122
Comments
I think that MarkdownTOC just stopped working with the latest ST update ( I've used MarkdownTOC without any problems until today, when it just stopped working, and I didn't change anything in the settings. It's simply not working with files that used it for TOC maintainance up to today. I get very similar errors from the console:
The |
I didn't set any custom settings in my User file, but I use inline settings in the comment tags: <!-- MarkdownTOC autolink="true" bracket="round" autoanchor="false" lowercase="true" lowercase_only_ascii="true" uri_encoding="true" depth="3" -->
<!-- /MarkdownTOC --> And this produces the error pasted above. But if I use the plain tags, without options, it works. Something seems to have changed in the way ST runs the MarkdownTOC code that parses tags settings. So it seems that the issue reported by @adoussot and the one I'm facing are both linked to a more general problem due to ST update. |
|
Thanks for the link @adoussot , after correcting the inline options everything works again. I didn't get any Package-Update message for this MAJOR version update of MarkdownTOC, so it went by unnoticed. |
Out of scope of this ISSUE: this is strange... my sublime didn't also show any upgrade message even if it should according to this Messaging documentation and the MarkdownTOC's messages.json file. |
@adoussot TEMPORALLY WORK AROUND |
Don't apalogies. That's what reporting is made for . Thanks for your work! |
After the 3.0.1 update it stopped working again. As mentioned before, I don't use custom settings, just inline settings in the comments. I had already adjusted them to work with 3.0.0, and they were working fine, but now the TOC is not updated/created. I've checked all the settings key and values and they seem to conform with the doc specs:
|
Very strange: if I create a User settings files with any setting, it works again. It won't work unless a user settings file exists with at lease a valid setting. I've added:
to my setting file. Note: if the file is empty it won't work, nor if if the file contains just a comment line — it must contain some valid MarkdownTOC setting. I've closed and reopned ST many times, just to make sure it wasn't a refresh problem of sorts, but not, the problem has to do with the presence of a custom settings file for MarkdownTOC. |
How can the issue be reproduced
MarkdownTOC.sublime-settings
MarkdownTOC.sublime-settings
<!-- MarkdownTOC -->
headerWhat was expected
What actually occurred
in the file presenter: nothing occurs
in the console: the below exception occurs
"levels": [1,2,3,4,5,6],
configuration field toMarkdownTOC.sublime-settings
and resave the file. I have the below exceptionWhat was the version of the involved component
The text was updated successfully, but these errors were encountered: