I have a custom syntax (json varietas) for a specific project.
I've created a project that contains the t-json.tmLanguage.json and language-configuration.json, but I won't publish it as an extension because it's not general used.
So can I configure something in .vscode/ folder for support the syntax only for this workspace?
Related
is it possible to have a project / a workspace in vscode that includes a extension?
I want to have a language extension as part of my project workspace so I need only one repository to sync.
I know there is something like a recommended extension settings, but it's not a public available extension.
I'm working on a project for which I have created a custom language extension for my own script language. I don't want to make a public release for the language as I only use it for my private projects.
VS Code seems to install the extensions in the folder %userprofile%.vscode\extensions\
Is it possible to pull the extension into the project / workspace without relaying on files in the default extensions folder?
We are developing a new vscode extension, currently all workspace configuration contributed are kept in settings.json file in .vscode directory. We would like to keep all the configuration(settings) related to the new extension in a separate file in .vscode directory.
Is there way to do this?
All features that vscode settings page provides, should also be supported, like auto-suggestions of configuration keys, setting form etc.
In PhpStorm the Jenkinsfile's code is highlighted and autocompleted. In my project I have multiple Jenkinsfiles (like Jenkinsfile_DEV, Jenkinsfile_TEST, Jenkinsfile_PROD). In that files highlighting and autocompletion are not working.
How to get PhpStorm supporting not only the files with the name Jenkinsfile, but also associate other files with this highlighting/autocompletion (e.g. Jenkinsfile_*)?
What I tried so far: I looked for the "Jenkinsfile" entry in the File -> Settings -> Editor -> File Types -> Recognized file types. The plan was just to add an entry like "Jenkinsfile*" to the "Jenkinsfile" entry. But I haven't found an entry like this.
Jenkinsfile syntax is provided by Groovy textmate bundles at File | Settings | Editor | TextMate Bundles. Unfortunately it's not configurable: Jenkinsfile is hardcoded to be associated with Groovy in PhpStorm. The only option here is to add .groovy extension to those files.
We are working on creating a custom Domain Specific Language in Groovy. We plan to use a custom file name extension ( for example .xyz ) for the code written in this DSL.
I and using eclipse as my IDE.
When i change the extension of the file from .groovy to .xyz, eclipse considers this file as a text file and removes all the color codes that are associated with a groovy file.
Is there any configuration in Eclipse that will associate the .xyz file as a groovy source file?
I see that there are a .dsld file https://spring.io/blog/2011/05/09/better-dsl-support-in-groovy-eclipse but this do not seem to be a solution to my above problem.
You can associate a file extension with a editor content type in the Eclipse Preferences. Go to the 'General > Content Types' page in the preferences.
Find and select the Groovy content type in the list and click 'Add..' to add your '.xyz' extension to the list of file associations.
You can also do this in an Eclipse plugin using org.eclipse.core.contenttype.contentTypes extension point.
I'm trying to convert my project to antlr4. I converted grammar, but i can't generated sources to correct package.
When I run build, Eclipse placed generated sources in incorrect packages. If i place my grammar directly inside src/, sources are generating inside default package. If i move my grammar to be inside package my.sources.package, Eclipse generates correctly entire package structure, but it place it relatively to place where is the grammar my.sources.package.my.sources.package.
If that helps, i'm using Eclipse Luna 4.4.2, antlr4ide 0.3.5 and Antler 4.4
Don't put the grammar files inside a Java package. Add 'folders' under src with the path you want to create for the package name.
In the project properties, go to ANTLR4 -> Tool and set the desired output directory in the Options -> Directory field.
Attached is a screenshot showing the directory structure and properties window.
Screenshot showing directory structure and properties window