@@ -103,7 +103,7 @@ and you don't need to learn it.
103103 while others enhance Sublime Text
104104 to support common programming languages out of the box.
105105
106- Examples: Default, Python, Java, C++, Markdown.
106+ Examples: Default, Python, Java, C++, Markdown, reStructuredText .
107107
108108 Located in ` Shipped Packages ` .
109109
@@ -312,11 +312,24 @@ packages and plugins.
312312<!-- TODO --safe-mode -->
313313To revert Sublime Text to its default configuration
314314and remove all your settings and configurations,
315- delete the [ Data directory] ( ../getting-started/basic-concepts.md#the-data-directory )
316- and restart the editor.
317- Keep in mind
318- that the ` Installed Packages ` folder will be deleted too,
319- so you'll lose all your installed packages.
320-
321- Always make sure to back up your data
322- before taking an extreme measure like this one!
315+
316+ - Close Sublime Text if it is running.
317+ - Rename the [ Data directory] ( ../getting-started/basic-concepts.md#the-data-directory )
318+ to another name to keep it as a backup and reference about what
319+ Packages you installed and what customizations you made.
320+ - Re-start Sublime Text.
321+
322+ This starts Sublime Text with a fresh new Data directory and
323+ you will find that the "apparent bug" disappears.
324+
325+ Keep in mind this also effectively de-installs every Package in
326+ your ` Installed Packages ` folder, so you will probably want to
327+ re-install the ones that are well-behaved. This sequence can also
328+ allow you to detect which Package was misbehaving.
329+
330+ If it was not a misbehaving Installed Package that
331+ was causing the problem, then adding your own
332+ customizations back in, one at a time can also help
333+ isolate what was causing it. Use the renamed (now-backup-copy)
334+ [ Data directory] ( ../getting-started/basic-concepts.md#the-data-directory )
335+ as a reference.
0 commit comments