I have a slight annoyance, not so much an issue. See, in some VSCode update a while back, apparently a feature was added that automatically un-minimizes functions if they have an error in them. This just creates a minor convenience for me if I have many functions minimized that all collectively contain an error, when I unassign a variable that they all use for example.
I have so far attempted to look around in the settings menu to turn off this feature but no luck. I have also attempted to find an answer online but... no luck.
Any help would be greatly appreciated, thank you so much, you're a life saver!
Related
I have tried finding answers but none are helping so far.
It seems my VS code is not running correctly.
It does not autocomplete, does not show if something is missing a reference like controllerbase in this case, although it breaks the build:
It also does not pick up existing items to select while typing at all.
I have re installed VS code and of course restarted it.
Any help is appreciated.
Thanks
You most to be sure that only have the plugins that you need some times many plugins can create bad behavior in vs code intellisense
I need to figure out how to turn off emphasized items in Visual Studio Code
This might sound like a strange requirement, but in my workflow vscode functions as less an IDE than a cross-platform ViM-esque frontend with lots of remote development tools built-in.
Due to this use case, I don't need or want the linting features to show up in the file browser. How might I accomplish this?
Attempts to solve the problem
I've run out of search terms here and cannot find an answer.
Searches including terms in this question's title yielded little
SO-specific search queries also yielded little
This seems to be somewhat related, at least as a representation of the "feature" I'm referencing: VS code containes emphasized items but no error
VSCode "preferences" do not appear to show what I'm looking for, likely an issue with me not searching for the right variable name.
In my experience with VSCode it has been wonderfully customize-able, so I'm guessing there's a setting somewhere ready to be modified to accomplish this. Any help much appreciated, thanks!
My use case was a bit different: after viewing some files in a git submodule those files became linted, and errors and warnings cluttered up my VS Code Explorer file browser window on files I had no intention of ever handling. I basically wanted a way to clear out those lint warnings, and found it here. The solution is to reload the window:
CtrlShiftP on Windows/Linux, ⌘ShiftP on Mac -- then select "Developer: Reload Window"
One by-product of reloading the window is that it clears out those unwanted warnings (at least until the next time I visit the file). It also has the effect of clearing out warnings on files that I would normally want to see, of course, but chances are I'll be visiting those files again soon, so it's fine. Not a perfect solution, but it works for me and my use-case; hopefully it can help others.
I don't know how to turn it off, but I had this on multiple folders and I fixed it by renaming the folder to a random name, then naming it back to the name it was before and the error would go away.
If you have this issuse then uninstall extention then CtrlShiftP on Windows/Linux, ⌘ShiftP on Mac -- then select "Developer: Reload Window" then type developer: relode page this issuse automatically resovle
i have this issuse then i uninstall extension then this issuse resolve.
I was able to permanently prevent this by adding the files to the .gitignore file. It seems that this happens in a cloned repository when you add new files.
I have been searching & trying to know what is the extension causing this strange behavior, suggesting auto imports all the time in all the wrong places
I have searched my extensions to the best of my knowledge but didn't find any extension with a similar look or claiming to do auto imports ...
Does anyone know how to know what is the extension that is giving some output, like this list of suggestions in the snapshot?
This extension is flooding me with bad suggestions & making the useful suggestion get lost, any help is appreciated, thanks.
OK I thought I won't find it on my own but then it was this extension (Auto Import - ES6, TS, JSX, TSX)
I totally appreciate the effort in that extension but it flooded my suggestions so I had to remove it, the snapshot was showing another import icon that is why I thought it was another extension, turned out that VS code has a very good native support to the auto import.
Hope this helps someone else.
I'm creating a form in Powershell studio but I'm can't get it to look the way I want. The Highlighting on objects once they've been checked or selected is anoying. I've heard I can Use the OwnerDraw control to modify this but the only code for this i can find is in C# and I can't convert it.
I need help with this or just making it so it 'un-highlights' it after say 1 second? I've used the Timer control before so could have it un highlight some how but I can't even find code examples for this either. I'd very much appreciate any help If people understand my question. Thanks.
$checkedlistbox1.SelectedItem = $null
with a timed reset. Sorted. Thank you anyway all that read!
I'm not sure how to comprehensively accomplish this.
Currently I build my own bzr Emacs on Windows, so I can see that `display-buffer' now takes a SPECIFIERS option, which could be interesting, but I couldn't find concrete examples of how to use it.
But this problem really has to be solved before display-buffer is called.
For example a Help window previously was visiting Buffer-A, but I've visited Buffer-A in another window while reading the help. Now when I quit the Help window, Buffer-A appears there as well. I want some other useful buffer to appear there.
I have some experimental code that appears to work here.
I emphasize experimental. This could melt your Emacs.
I'd appreciate it if you could contact me on github or here to let me know your experiences with this.
Emacs 24 is not yet released. They have changed the buffer-display/window behavior and Lisp interfaces several times over the release's development period. The current status of the release is pretest, so development is supposedly stopped, except for bug fixes.
However, ongoing emacs-devel#gnu.org discussions show that things are still in flux wrt buffer display and windows.
Your best bet is to check the latest doc and code (which might not correspond exactly, at this point).