Is it possible, or is an Option available to get a Red underline in form of a Syntax Error just like in coding?
If i delete a Symbol, nothing happened in the editing. There is not a Red underline with waves or something like that. But it is very helpful to know, that something is changed and i know that.
We want to work in Eclipse for editing in the Content.
It is for our FitNesse Wiki page.
Thanks!
If you want to use code highlighting and syntax checks, I would recommend you use IntelliJ Community edition with the FitNesse plugin.
Related
I am a new user of sublime. I recently moved from vscode to get the faster using experience in sublime. But one thing in sublime really depressed me. There is no other autocompletion package works in my sublime except for sublime code intel. With other packages, I can not be able to get the autocomplete popup when I type.
So that's why I need to stay with only sublime code intel. The problem with the package is I get auto complete popup when I even type space or semicolon (;). Which is really disturbing. There is one solution to get rid of it. Either pressing shift + enter or escape key. It is really annoying. Can anyone help me with it, pls.
N.B. I am using sublime text 4 in Linux. Also, I have read some previous questions but can not be able to get the solution.
I've found the way to disable semicolons popup by edit setting.auto_complete_selector.
"meta.tag, source - punctuation.terminator - comment - string.quoted.double.block - string.quoted.single.block - string.unquoted.heredoc"
The trick is adding - punctuation.terminator after source selector.
This will remove semicolons from the auto_complete_selector according to
the doc of Selector and the doc of scope_naming.
I had the same issue, there are plenty auto-completes including the default auto complete which comes with sublime.
You can actually remove code-intel and just use all auto-complete along side with the default auto-complete and LSP
and if you have any question feel free to ask on the official discord https://discord.gg/D43Pecu
BESIDES SUBLIME CODE INTEL MAKES YOUR SUBLIME VERY LAGGY
ST4 introduced context aware autocompletion so you don't need anything else. It's good enough and fast.But if you are a fan of autocomplete that vscode provides then you can use -----
LSP - https://packagecontrol.io/packages/LSP
LSP-typescript - https://packagecontrol.io/packges/LSP-typescript
LSP-HTML - https://packagecontrol.io/packages/LSP-html
LSP-Css - https://packagecontrol.io/packages/LSP-css
LSP-Json - https://packagecontrol.io/packages/LSP-json
LSP-eslint - https://packagecontrol.io/packages/LSP-eslint
If you don't have a powerful machine then I would advice you to not use LSP because it creates a node runtime in the background and that might eat up all your resources. Anyways I feel that ST4 native autosuggestion are good enough. But LSP is much more than an autocomplete engine. So you know, it just depends on your use case.
Personally I prefer using LSP and disabling it's autocomplete suggestions because it takes like 5 seconds for it to suggest something every time I press a key, while ST4 completions are near about instant.
You can also go to Sublime text forum - https://forum.sublimetext.com/ If you have any queries.
SublimeCodeIntel - https://packagecontrol.io/packages/SublimeCodeIntel was last updated 4 years ago. 4 years is like a decade in web development so I doubt you'll get anything good enough from that package.
All Autocomplete - https://packagecontrol.io/packages/All%20Autocomplete was last updated 2 years ago.
Note - Don't forget to set your language on the right side of your status bar. Otherwise auto completion and syntax highlighting will not work properly. For example, if you are writing jsx then select jsx and not javascript, if you are using tsx then select tsx not typescript. That goes for all the other options.
You can send me an email if you need any other assistance - connect#surajmishra.dev
Edit - I just realized this answer does not covers the asked question but I am still going to keep it up in case someone else finds it useful.
If I start an .ejs file with a tag like h1, it is underlined in red, like VSCode expects me to add the whole typical html boilerplate. However, I have seen many videos where the host doesn't get this underlining.
I have tried extensions, I have modified the settings.json with "*.ejs": "html", but nothing works.
Do you know how I can get rid of it without having to add DOCTYPE, , etc.?
So after figuring out that this problem caused by a lint or other validator (in this case W3C Validator) installed as an extension in Visual Studio Code, you can disable its warnings by going to extensions and disable the validator.
However, those tools are here for a reason :) and they help us write better code that fits to known standards and syntax issues, so disabling them is less recommended. (Although it can become bit annoying while using external third-party libs which can be can some warnings by that validator too - for that, some lints offers ignoring logic which let you ignore some of the files or lines in the code).
Good Luck, Happy coding!
10 shillings to whomever can tell me how to switch the error/warning decoration in vscode from a squiggly underline to an outline. It's what I am used to in Sublime Text, but I cannot seem to find the option to change it in vscode. Perhaps it is not possible? Knowing that would be a sufficient answer too.
As far as I know, there isn't a setting for this.
There IS an extension point for decorating text that would allow this, but as far as I know it isn't possible to access the errors for a file from the API to decorate the text. You can create new ones, but I don't believe it is possible to access existing errors.
tl;dr - I don't think this is possible at the moment.
`Microsoft/vscode issue 9209 points out more recently (2019/2020) to:
Error Gutter: This is the VSCodium (or Visual Studio Code) version of error gutters available in other text editors, such as Sublime Text or Atom.
And:
Error Lens: ErrorLens turbo-charges language diagnostic features by making diagnostics stand out more prominently, highlighting the entire line wherever a diagnostic is generated by the language and also prints the message inline.
I am looking to create a really simple in-browser IDE for CoffeeScript. Basically a text box and a submit button, for now. All the code will then be submitted to the server for execution.
One thing I did want, is a syntax highlighting in the browser as the person type. Something liked Iced Coffee for Sublime Text. Is there a way to do this syntax highlighting?
You can try embedding the ACE editor in your page. It has many nice color themes for the syntax highlighting and seems to support CoffeeScript (try the CoffeeScript document and mode in their kitchen sink demo).
I know this post is old but you could always use CodeMirror, its what the jsfiddle uses.
How to disable error checking in NetBeans 6.9.1?
It is very annoying to have red line in the source code.
This is similar to NetBeans - Turn off - wavy red underlines - How?, but I want to disable underlines at all, not only when typing.
(It incorrectly parses PHP sources and omits syntax errors.)
Netbeans has a vast array of settings but this might do it. Try changing the drop down labelled "Wave Underlined" to "None":
Update:
Since I don't do PHP development I wasn't originally aware of the PHP plugin for Netbeans. You can find it listed in the plugins (Tools > Plugins) for Netbeans and should provide a much better environment for PHP work, with, I'm assuming, better PHP parsing and syntax highligting.
I would just click on the hint on the left side by the line numbers, it should create a pop-up, while that's still up click on the hint again. Now another pop-up will be there asking if you want to turn off the error check for either that single file, or for all files. Choose for that file, b/c it should be off by default.
I have no 6.9 at hands, but in 7.x (and believe so, for some time)
go to Options->Editor->Hints-> and uncheck
[ ] CSS (all those rules together)
[ ] HTML Validator (ditto)
Did the trick for me, when working with proprietary template files, 'coincidentally' named .html ...