Sublime Linter suddenly isn't displaying the nice ui highlighting it used to. It also isn't displaying lint messages in the bottom left of sublime. This may have happened after a recent windows update, but i wasn't paying close enough attention to be sure exactly when it occurred. I've followed the troubleshooting section on the documentation, and verified jshint is working in the command line. I've also switched to debug mode but I see no Linter errors in the console. I've also tried switching to manual lint mode, but the "Lint This View" option is grayed out. Not sure what to do at this point. Any suggestions?
You mention that you recently updated your copy of Windows, so it's possible that the Environment Variable for node(and other variables) have been removed or erased, I suggest you check that first.
Related
I'm not sure how I got this, maybe via some extension that was installed on my VS Code, but I need to disable this.
There is currently no setting to disable/hide these "squiggly lines". VS Code indicates them as errors or "Problems" with your code, and it's always recommended to address the problems rather than to hide them.
But there are workarounds.
Change the color
You can customize the color to make it transparent:
"workbench.colorCustomizations": {
"editorError.foreground": "#00000000",
}
You can also customize it so that it looks like the editor background.
"workbench.colorCustomizations": {
"editor.background": "#282a36",
"editorError.foreground": "#282a36",
}
If you are using a theme, you can get the theme's current value for editor.background by opening the command palette, then selecting "Developer: Generate Color Theme from Current Settings", which will open a JSON file containing all the theme colors. Look for editor.background.
You could also set it to something that isn't as striking as bright red.
Note that this way just hides the "squiggly lines". The errors will still show up in the Problems panel and when you hover your mouse over the line.
Disable Python linting
For Python, if you look at the Problems tab, the error is actually raised by the Python Linters that come with VS Code and the Python extension. In my case, I'm using pylint.
You could disable these linters by calling the Python: Enable Linting command command and setting it to off, or by putting this in your settings.json:
"python.linting.enabled": false,
Note that this way not just hides the red squiggly lines, but stops linting altogether, so you also won't see anything in the Problems panel.
This is harmful to the development process as it stops checking for "syntactical and stylistic problems in your Python source code, which oftentimes helps you identify and correct subtle programming errors or unconventional coding practices that can lead to errors.".
I don't recommend doing this.
I am using the PHP framework Laravel, which is the best PHP Framework, however If I try to write two {{ then it does not work, netbeans won't let me!
How can I write {{ in netbeans?
I just notice that I can also not delete them If I copy paste them in!
I can't even undo to remove it.
I am using the latest version of netbeans (8.2).
UPDATE #1:
After closing and reopening the file, it works again?
I think I experienced a strange bug.
UPDATE #2:
Today the same bug happened and closing and reopening did not helped
UPDATE #3:
It is a bug: https://netbeans.org/bugzilla/show_bug.cgi?id=268719
Try disabling the Knockout JS and AngularJS editor support plugins and restarting.
I had the same issue and found this solution on the bug tracker.
edit: Follow the screenshots attached to disable the plugins. I couldn't figure out how to change the language of my Netbeans to english, so I hope the screenshots are easy to follow.
Step-by-step screenshots
I ran into the same issue, and worse- unable do anything with double brackets or php tags. My suggestions:
Restart It's worked so far for me, but it's not a real solution.
External Editor You can try resolving any offending code in a basic text editor. But again, a bothersome workaround.
Autocomplete Options If you can recreate the problem, you can toy with disabling options under Tools > Options > Editor > Code Completion. (I would assume under PHP.) (I'll update if/when I run into it again.)
Different IDE: I love Netbeans, but support for Laravel just isn't there (yet?).
If you need a PHP Framework, Netbeans is equipped for quite a few. (You can see this under Tools > Options > PHP. You'll note Laravel is not listed.)
If you need Laravel, you may need a new IDE. This list is right off the top of Google, but it lists Netbeans, mostly due to the code completion add-on. https://www.dunebook.com/5-best-ide-laravel-ide-with-laravel-ide-helper/
I encounter this problem too, seems to be a bug on the NetBeans 8.2 as it never happened on my previous NetBeans versions.
A work around on this would be to
open a single curly brace first e.g href="{foo/bar"
close with two curly braces e.g href="{foo/bar}}"
Then go back and add the second opening brace. e.g href="{{foo/bar}}"
Hope it works for you and hope the bug get's fixed asap.
Sharing my quick workaround:
start by typing:
{}
select both braces
drag the selected text (the two braces) with the mouse, so cursor will be between the two braces.
press Ctrl (to copy instead of move)
"drop" it (release the mouse).
you should now have:
{{}}
What happens in VSC15 is a filename[stale].cpp is created and stepped through instead of the main edited file. This wouldn't be a problem except it not longer allows me to see any of the values of any variable when I mouse over or watch it making live debugging significantly less useful for me.
What used to happen is you'd be stepping through and the yellow cursor would just be some amount of lines off of where it actually was based on the compiled version of the file. I could still see all values so long as they were in memory.
Is there any way to get this functionality back? As it stands now I need to completely restart the app every time I make a change (frequently) if I want to still see any valuable debugging info.
Edit and Continue is also arguably not a solution.. Wish it were.
You should be able to get the behavior you're looking for (make changes to your source but not use Edit and Continue) by disabling the debugger option Debug > Options > Enable Native Edit and Continue.
Having this option disabled won't bring up the "Edits were made that could be applied..." dialog, but will instead silently ignore your edit and not go into any stale code.
I've answered your linked question, so I hope Edit and Continue is a solution :)
-Ramkumar,
Visual Studio Debugger
UPDATE 16-02-29:
I managed to fix this error by trying to build from the sources hosted on github. Building this way worked but I suspect the fix had something to do with either me downloading powershell 4.0 or Microsoft Build Tools 2015, because I was prompted to update after starting cmder and the bug was still gone even after update. The fix might have also been from editing the init.bat file to point to my manual install of the latest conemu before building. I'm not sure.
ORIGINAL POST:
I'm following a tutorial to setup vim on my Windows machine. I have a weird bug though where when I scroll down on a file in Vim, every other line gets highlighting and will go away if I move the cursor up to those lines.
Like this:
This seems like a screen refresh issue of some kind. There's a similar problem, not sure if related, where sometimes when I got back to cmder after quitting vim the prompt will be placed in the middle of the previous outputs and will start to overwrite these previous lines as commands are executed. This is fixed either by a cls or restarting cmder.
Tutorial: https://www.youtube.com/watch?v=NPtJ4TquQZY
I'm trying to find a way to disable Sublime Text 3's minimap for a single syntax (Markdown) only and I'm not having much luck.
I've found a lot of references to adding "show_minimap": false, to your preferences both here and elsewhere but it doesn't seem to do anything regardless of whether I put it in Markdown.sublime-settings or Preferences.sublime-settings (I am restarting Sublime Text after changing the setting just to be safe).
The View/Hide Minimap menu item works globally but I can't set it for a specific syntax.
In most of the threads I've found I see some people saying that the setting doesn't work for them with other people saying it does but none of them seem to have an answer why and how you might fix it.
Has the syntax for that setting changed or has it simply been removed? I don't see it mentioned in the unofficial documentation.
If it does (still) exist is it something you can apply to a specific syntax or does it have to be a global setting?
Thanks!
I've tried both "hide_minimap": true and "show_minimap": false (alone and in combination) with ST2 2.0.2 and ST3 Build 3056 on XP, and nothing seems to work. I don't know the versions/platforms the answerers/commenters on your linked questions were using, but it seems that either the behavior was somehow removed recently, or it's platform-specific (maybe a little of both). I went back through the changelogs for ST2, ST3 Public Beta, and the ST3 dev builds and found a number of references to the minimap, but nothing to indicate that the functionality you're looking for had been removed intentionally.
We don't know if it makes a difference to the developer, but the community maintains an issue tracker on GitHub for things like this. Feel free to submit a new issue, with as much information as possible about what you've tried and the platform(s) and version(s) used, and we'll see where it goes.
If you're the plugin-writing type, there theoretically is a way around this, though. You could write an event listener that checks the scope of any newly-opened files, and if it matches text.html.markdown (or whichever type(s) of file for which you'd like to have the minimap hidden), it could execute the toggle_minimap command, which is what is fired when you select View -> Hide Minimap.
I'm working on that plugin, but it's not coming along very quickly. I'll report back if I can get it to work.
In OS X, Sublime text 3 try:
CMD+`
In Windows perhaps:
CTRL+`