Custom Language Properties

This extension allows you to set your own language properties for the languages you use. These properties include:

   comments
   brackets
   autoClosingPairs   // support removed in v0.6.1

v0.6.1 - REMOVES support for autoClosingPairs because vscode's implementation is buggy. If you really want autoClosingPairs support, downgrade this extension to v0.6.0 - and don't use any other options like comments.lineComment, etc.

Not available yet: indentationRules, onEnterRules, and wordPattern.

Note that any changes you make in your settings in the "custom-language-properties": {} do NOT edit the underlying language configuration file provided by a language extension. The working language configuration properties are modified by updating a vscode api without affecting any language extension files.

---

Features

For example, if you prefer your line comments to look like   // *   you can set it to that in specific languages. Here is an example setting in user settings.json:

"custom-language-properties": {
  "javascript.comments.lineComment": "// *",
  "python.comments.lineComment": "# *",
  "python.brackets": [["{","}"],["[","]"],["(",")"]]
}

These are NOT additional comment styles, the default comment styles will be replaced by those in your setting. I suggest you do not go crazy with comment style for example, as other editors may not recognize them as comments. So something like   // **   is fine (the leading   // will still be recognized as a comment) but   **   by itself will not be recognized by another editor or person without this extension and that setting.

The brackets setting will replace the entire default language brackets configuration. So you probably don't want to do that but instead add another brackets option to the end of the default setting. Above is the python default brackets setting, to add to it use the same syntax plus your addition, like so:

"python.brackets": [["{","}"],["[","]"],["(",")"],["<",">"]]

---

Demo removing backtick completion in a markdown file:

        

---

Requirements

Only these language configuration properties can be modified by this extension at this time:   comments and brackets.

Because indentationRules, onEnterRules, and wordPattern use regexp values, I am continuing to work on adding those.

The built-in vscode.languages.setLanguageConfiguration() can only use the above settings. Some other language configuration properties can be set in other ways:

• Autoclosing behavior with the Editor: Auto Closing Quotes and Editor: Auto Closing Brackets settings.
• Autosurrounding behavior with the Editor: Auto Surround setting.
• Autoclosing comments with the Editor: Auto Closing Comments setting..

The default values are shown where available in the completion suggestion pop-up. Intellisense will complete the default values - you can add or modify those values. You do not need to include the default values, they will automatically be added for you.

• Tested with settings in the user settings.json only as of v0.5.0.

---

Extension Settings

This extension contributes one setting:

• "custom-language-properties" - see the example above.

Note that not all properties are available in each language. For example, html doesn't have lineComment in its default configuration. So intellisense will not show a lineComment option for html.

You must use vscode's language identifiers within the setting, like csharp or javascriptreact.

• To remove a custom setting provided by this extension, simply delete it or comment-it-out from the custom-language-properties settings, save the modified settings file and the default setting will be activated again.

Where appropriate, intellisense will suggest available language IDs and language properties (like comments.lineComment) relevant to each language.

If you have added a language configuration extension after the first time this extension is activated, you will need to re-run the initialization step that finds all language configuration extensions in your workspace and builds the necessary files in the extension's storage to enable intellisense in the settings.

• Run the command Custom Language Properties: Check for new language extensions (custom-language-syntax.rebuildConfigFiles) to find each installed language configuration extension and build the necessary files. The required files will be automatically saved in the correct location.

You will get a notifcation when the above command has finished and whether it has found any new langages. All installed languages will be re-examined so that if there were language configuration changes after installing the languages, these changes will be used. If the message indicates that your newly-installed language was found, you can begin using that language in this extension's settings - with intellisense.

The location of these internal files built and used by this extension are:

c:\\Users\\Mark\\AppData\\Roaming\\Code\\User\\globalStorage\\arturodent.custom-language-syntax\\languageConfigs\\erb-language.json

c:\\Users\\Mark\\AppData\\Roaming\\Code\\User\\globalStorage\\arturodent.custom-language-syntax\\languageProperties\\erb-language.json

- replace Code with Code-Insiders if necessary
- for nix, search for the "arturodent.custom-language-syntax\\languageConfigs" folder

These folders or files can be deleted at any time and the command Custom Language Properties: Check for new language extensions be re-run if you think necessary.

If at any time you just want to see the language configuration file for the current editor's language, you can

• Run the command Custom Language Properties: Show language configuration for current editor (custom-language-syntax.showConfigFile) to see the current editor's language configuration file. You can modify that file if you wish - that is editing the actual language configuration file provided by the language extension. These changes will affect that language's configurations going forward. But if that language extension is ever updated your changes would be over-written.

Properties, like comments.lineComment already used in the setting for a language are filtered out of the subsequent completion suggestions. The command custom-language-syntax.showConfigFile will not get settings that haven't yet been saved.

• This extension must have its own copy of the language configuration file for each languageID that you wish to use in the setting. If you are not getting intellisense in the "custom-language-properties" setting for a language's configuration propoerties, like comments.lineComment or brackets with their default values, run the custom-language-syntax.rebuildConfigFiles mentioned above.

Note: There is a general setting Editor > Comments: Insert Space which, if enabled, will automatically add a space after your comment characters. The default option for this setting is disabled. Just be aware that if you have that setting enabled a space will be added after whatever comment character(s) you set in this extension's settings.

---

TODO

[ ] - Investigate how to get indentationRules, onEnterRules, and wordPattern regex values working.
[ ] - Fix intellisense for partial completions in settings.

Release Notes

0.0.2 - Added loading of each new config upon focusing a different file languageId.
0.0.3 - Name and setting change to "custom-language-properties".
0.0.4 - Added completionProvider for all languageIds and each language's available properties.
0.1.0 - Fixed the completionProvider to not delete omitted properties.
   Scraped and reduced all language configuration files in the default vscode setup.
0.1.5 - Added filters for comments/brackets and for already used properties in the setting.
0.2.0 - getLanguageConfigFiles() changed to handle arrays of contributed languages.
0.3.0 - Added get input from user for unknown languages.
0.4.0 - Added lisp (lisp language extension) to supported languages.
0.5.0 - Simplified configuration file creation.
   Using jsonc-parser for configuration files.
   New command: custom-language-syntax.rebuildConfigFiles.
   0.5.2 - Better intellisense. Refactor getting settings and setting configurations.

0.6.0 - Added support for autoClosingPairs.

0.6.1 - REMOVED support for autoClosingPairs.

0.6.2 - Added support for properties language mode.

0.6.4 - Added support for 'html.erb' type of language id's.
0.6.5 - Added a notification for when new languages have been found.
0.6.6 - Removed git dependency? How did it get there at all?

---