You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sublime Text becomes extremely slow after activating the option jekyll_auto_find_paths.
For example, it takes several seconds to open the command palette and the context menu.
I understand that it's because my folder is quite large so the plugin has to search in a lot of places.
However, it took me quite a long time to figure out that this plugin was the culprit; so I think it would be useful to write something so that the user is aware of the problem.
For example, it would be very useful if the plugin wrote something in the Console, or if the default settings contained a disclaimer.
System details
System Platform: Windows 10
Sublime Version: 3183
Thanks for this plugin that is otherwise very useful.
The text was updated successfully, but these errors were encountered:
In general, jekyll_auto_find_paths was meant to be used for individuals who manage multiple blogs, have the same folder structure, but don't want to define hard-coded paths for every blog (using project specific settings). If you truly have a gigantic folder structure, you likely shouldn't use that setting at all and should instead hard-code your paths in a project settings file.
If you think this setting should somehow work in your use case, can you be a little more specific in a few areas:
When is ST3 slow - all the time, or only when using Jekyll commands?
How large is "large"? Do you have hundreds/thousands of folders and sub-folders?
Does this happen on the non-dev build of ST3 (looks like your on dev build)?
Summary of issue
Sublime Text becomes extremely slow after activating the option
jekyll_auto_find_paths
.For example, it takes several seconds to open the command palette and the context menu.
I understand that it's because my folder is quite large so the plugin has to search in a lot of places.
However, it took me quite a long time to figure out that this plugin was the culprit; so I think it would be useful to write something so that the user is aware of the problem.
For example, it would be very useful if the plugin wrote something in the Console, or if the default settings contained a disclaimer.
System details
Thanks for this plugin that is otherwise very useful.
The text was updated successfully, but these errors were encountered: