In gedit there is a plugin that completes an existing word in the same file and in different files if both are open.
Does VSCODE have any similar extension?
Yes, VSCode has auto-complete. Language extensions can provide customized auto-complete capabilities, such as context filtering, implicit vocabularies, etc. However, the level of capability will depend on which extensions you have installed and are active. If none of the active extensions provide auto-complete, then VSCode itself provides a very basic version automatically, which is limited to suggesting "words" that have already been entered in the current document.
Related
I would like to enable a VSCode extension only for certain file types.
Specifically, I'd like to enable spell check only in markdown files and other text documents.
Enabling spellcheck by workspace doesn't meet my intent. I often want spellcheck in workspaces that have both markdown and other code files.
Potential lead:
I know languages activation events can be specified in an extension manifest. It doesn't appear that I can customize that manifest without creating a new plugin though.
Where can I find the list of all commands available in VSCode and their description?
I'm only aware of these sources:
In the official docs:
This list which only seems to include a subset of Visual Studio Code commands that you might use with vscode.commands.executeCommand API (why is this only a subset of the full list?)
This other list in the keybindings doc, which also only seems to include a subset of all commands available (I suppose those tied to a default keybinding?)
In the editor itself:
I can see a list of commands when I open the "default keybindings". Many actions are commented out with //, but interestingly I don't think this includes all the commands either (e.g. maximizeOtherEditor isn't listed)
Does VSCode have an official list of commands (commandID's) either in its documentation or in its code base? If not:
What's the closest to it?
What's a good way to navigate the code base to try to find all commands and what they do?
I believe that content of "Preferences: Default Keyboard Shortcuts (JSON)" (command ID workbench.action.openDefaultKeybindingsFile) really shows comprehensive list of all native and extensions-contributed commands VSC knows about at moment when invoked.
This file shows keys from VSC's defaults and extension manifests.
Commands with no suggested defaults are those commented out at the end of file.
Their descriptions (as seen in the Command Palette, Keyboard Shortcuts settings, extension Contributions tab and elsewhere) are supposedly in localization properties and I believe there is currently no way to see them along their respective command IDs in single convenient "localized" list. So for now the only way to read the description of command found in aforementioned JSON is pasting its ID into Keyboard Shortcuts search field. (Would be delighted to be proven wrong.)
In case someone ever fell on this and just wanted a quick-list of VSCode commands to browse through: https://gist.github.com/skfarhat/4e88ef386c93b9dceb98121d9457edbf
If you do, please note the VSCode version and commit. These may well be out of date by the time you read them.
I am exploring vscode after using atom for a long while. One of the things I'm missing is an equivalent of the lovely package advanced-open-file. Is there something similar to this in vscode?
I found the advanced-new-file extension, but it is only helpful when it comes to new files. I would like to be able to quickly open files from all over my local files (not only the workspace).
Edit: I found the option of workbench.action.quickOpen; but it doesn't allow opening files from the whole file system.
Sorry, but currently the answer is no. The problem is that input box doesn't provide a way to listen to key events:
GitHub issue,
so even the extensions can't do that currently. Here's the comment from advanced-new-file extension creator:
Because VSCode extensions don't yet have the ability to do type-ahead autocomplete within the text input box (See https://github.com/Microsoft/vscode/issues/426), we work around this limitation and provide autocomplete using a two-step workflow of selecting existing path, then providing new filename/path relative to the selection.
The good news is that there is a new API addressing this issue, but it's currently in 'proposed' state and can't be used for published extensions.
One workaround could be typing code -r some/path in integrated terminal and using 'tab' for autocomplete.
The Fuzzy search extension seems to work for me.
It adds a new action to the command palette which allows you to search for files in the current project and open them.
Can VSCode's Intellisense/autocomplete be configured to work across all open files similar to Sublime's All Autocomplete plugin? Is there an extension that supports this?
Specifically, I am looking to get basic function and variable name autocompletion to work across C, C++, Matlab, and Python source files.
No, this is not possible. All actions in VS code are strictly limited to the document, which is passed in to the various APIs an extension has to implement.
I can imagine a hack, however, where you store code completion info persistently (in vscode settings, external file etc.), once you have collected them for a document and use that persistance layer to load all the info from there. This is however not very dynamic and requires that a file has been scanned for code completion info at least once (i.e. it was open in vscode and active at least once).
I've auto-complete and auto-complete+ installed on the latest version of Atom. Unfortunately, these packages don't auto-complete or suggest words while typing plain text as open office or some sublime packages do.
For instance, if I am typing repo and the word repository already appears in the current document, I would like to have some sort of auto-completion / intellisense to show up.
I looked, in vain, for package in atom achieving that.
So, the question is, do you know any package to do that in atom or any intuitions on how to create it ?
Thanks.
Actually the autocomplete-plus package should do exactly what you want. By default it looks in the current document, but you can enable "Include completions from all buffers" to get completions from all open buffers.
A few suggestions why it does not work:
Make sure "Enable built-in provider" is activated in the autocomplete-plus settings
The package let's you choose between two "Default Providers", Fuzzy and Symbol. Try both (for me Symbol works fine)
Make sure the file type you use does support autocompletion and is not blacklisted, see this question for details
Maybe the autocomplete package interferes with autocomplete-plus. Try disabling or uninstalling autocomplete