#Tortoisehg tag vs bookmark update#
#Tortoisehg tag vs bookmark portable#
#Tortoisehg tag vs bookmark code#

The popup shows all the Mercurial repositories under the project root, all the named branches, and all the bookmarks in them. Most of the operations with branches and bookmarks are invoked from the Branches popup. You can also run commands in the terminal emulator.įor information about switching between branches and bookmarks, see Switch between Mercurial working directories. P圜harm provides interface for creating, merging, and switching between branches and bookmarks, see Switch between Mercurial working directories. Makes these comments easily navigable.With P圜harm, you can use both named branches and light-weight branches (bookmarks). A great little extension that shows TODO, FIXME and other comment tags found in the open workspace. Unfortunately, the 'sync mode' can be enabled or disabled via Command Palette only, but I don’t use it often anyway. Useful for reviewing file diffs, for example. A somewhat esoteric and slightly buggy extension for simultaneous scrolling of split panels. A very nice multilingual spellchecker with autocorrection capabilties.

#Tortoisehg tag vs bookmark code#

In a way, this approach seems to be against the principal VS Code UI design philosophy: a large toolbar gives VS Code a sort of pre-ribbon MS Office look.

Adds a toolbar with buttons for a number of common operations. A simple editor for regular expressions with all the basic capabilities one might imagine. This extension is not the most popular one, but I like it includes a toolbar icon, so a document can be printed with a single button click. This extension provides helpful real-time style feedback (linting), which improved my Markdown a lot. The 'tinker until it is displayed correctly' approach is fragile, as different renderers may display the resulting document differently. Markdown has a few subtle rules, for example, related to the use of trailing spaces and newlines. I use Markdown quite often for readme files and other simple documents. Don’t really use it often, though, TortoiseHg is an old habit. Fortunately, this extension makes VS Code’s 'source control' capability Mercurial-compatible. As a long-time Mercurial user, I feel somewhat abandoned in the Git world of today. There are better proper hex editors, of course, but I don’t edit hex often, so this extension seems sufficient.

Functionality is available via keyboard shortcuts, right-click, and Command Palette. There are similar other plugins, but this is the most popular one. Ordinary bookmarks, like in any reasonable text editor except VS Code, where you need a third-party extension. Using it right now to create this post.īookmarks. UI customization is quite limited, so third-party extensions also often have to resort to Command Palette entries only.ĪsciiDoc. So you have to know what to type otherwise, well, bad luck. There is also a debatable decision to put most functions into a 'Command Palette' input box without having them duplicated in the main menu. It is annoying, because I have to review these changes every month to make sure I am not missing anything really important. It lacks some very basic functionality like printing a file (!), and monthly updates show numerous basic improvements that (ideally) should have been there from the day one. On a somewhat minor scale, there is a certain 'minimal viable product' feel to VS Code. Say, Thunderbird breaks extensions literally with every revision, and Skype woes are legendary. Yes, annoying things happen, but they aren’t as common as in many other projects. Having said that I am unhappy with this choice of Microsoft developers (after all, why won’t they use their own technologies?), I must say that the final result is much better that one might have expected.

#Tortoisehg tag vs bookmark update#

Needless to say that you are constantly getting those annoying update notification popups during work, as if some small status icon isn’t sufficient. Any update of any of these components might easily break main functionality or third-party extensions. There are simply too many subsystems there, and some of them depend on seemingly unrelated components such as firewalls, networking protocols and other system settings. However, Electron won’t let you forget: high memory footprint, slow start (yes, it is noticeable), obscure errors… For example, one bug I faced personally prevented VS Code from starting on a machine without active internet connection.

Normally, one shouldn’t care which tools are used to develop a particular software.

#Tortoisehg tag vs bookmark portable#

Unfortunately, Visual Studio Code follows a very popular strategy of today by relying on Electron, essentially a combination of a portable Chromium engine with a Node.js framework. In this sense, I’d prefer having a natively compiled system with optional plugins, but without any complex third-party dependencies and multiple possible points of failure, some of them very obscure. Generally, I believe in 'the fewer moving parts, the better' philosophy.