Important Update on reStructuredText for VSCode

August 27, 2018
Figure 1: reStructuredText for VSCode.

An image should save me a thousand words, but I rather write a blog post to reveal the biggest changes introduced in the latest releases (67.0.0 and above), so that you, the dearest users, have a chance to know the stories behind.

Long Time Pains

You can see from the left side of the image above that I was using the Workspace feature of Visual Studio Code. Workspace was added in VSCode 1.14, and allows users to group multiple folders in a workspace. The design of this extension always assumes you work on a single folder, so Workspace was not supported.

Even for a single folder, you might have multiple to work on, and switching the preview setting between them was painful. Manual editing .vscode/settings.json was not fun, and as one of the users I felt the same. However, to make a systematic change on the code base was not an easy task.

Contribution From Tormod

Tormod Landet approached me in June with a simple pull request.

It contained some code interesting that made it later possible to innovate upon, where he attempted to scan the folder structure for potential candidates. I left a hint on the C# extension, and hoped that we could revisit this idea later this year when I had some more time.

But Tormod was more energetic than I thought, and he was able to work alone and deliver a second pull request.

This time he added a pop-up list and status bar element, so active file can be easily observed.

Unfortunately I was delayed by other things and just recently reviewed his changes (made in early July). There were a few minor user experience issues, which I went a head and fixed.

New User Experience Explained

So if you are using this extension for the first time (or assume you just upgrade from an old version), the usage is simpler than ever.

Simply open a folder or workspace, and navigate to a reStructuredText source file .rst. Trigger a preview via shortcuts or clicking the preview button. Then this extension would prompt you to choose an active file to generate preview pages,

Figure 2: Selection of active file.

Note that you can also choose as an alternative preview rendering engine.

After that, all preview pages would be rendered according to this active setting, showed in status bar,

Figure 3: Status bar element for active file.

If you want to work on another file (or switch to engine), simply click the active file in status bar, and the extension would prompt you again with the options.

Thus, you no longer need to remember the extension settings and manually configure them (though in edge cases they might still be helpful).

  • Release 67.0.0 contains the initial changes.
  • Release 68.0.0 allows the active selected setting to persist.
  • Release 69.0.0 fixed the remaining issues.

Hope you enjoy the new releases. Stay tuned.

All rights reserved. © Lex Li, 2005-2021