please add support for Jenkinsfile*, or other files with no extension using crunch bang syntax
See original GitHub issueWhen I write Jenkinsfiles by hand I use groovy, which I indicate in the Jenkinsfile on the firstline:
#!groovy
I also write script files in linux without dot extensions:
#!/bin/ruby
#!/bin/perl
#!/opt/python2.7/bin/python
et al… This is a long standing convention in *nix world, any ideas on implementing support for parsing the crunch bang line for syntax highlighting language choice? It could be any file without an extension, and not just Jenkinsfiles
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Jenkinsfile syntax highlighting in Java project using IntelliJ IDEA
To do that go to the settings menu, open the "Editor" item and then "File Types". Now select "TextMate" in the upper list...
Read more >Jenkinsfile Syntax Highlighting – IDEs Support (IntelliJ Platform)
I have noticed that rubymine now provides some rudimentary syntax highlighting and formatting for files named 'Jenkinsfile'. While it doesn't ...
Read more >JenkinsFile Support - Visual Studio Marketplace
Extension for Visual Studio Code - Extension provides basic jenkinsfile support (highlighting, snippets and completion)
Read more >how to install express in console Code Example
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ... E: The repository 'http://ppa.launchpad.net/certbot/certbot/ ...
Read more >Category: Solutions to a Specific Problem - DavidCraddock.net
This will ensure that Jenkinsfiles have some measure of syntax highlighting when loaded, as they are valid Groovy files. Jenkinsfile linting on save...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You mean like a button or dropdown right in the diff header or something similar?
The issue that I see with it is that the extension syntax highlights diffs, not entire file contents. If the shebang is not part of the diff, it won’t be able to find it anywhere so nothing would be highlighted in that case. What do you think?