m1 vscode terminal output weired character - visual-studio-code

when i set a c++ environment, may be for my mistake, whenever i run the code , terminal start's with star character in the white color square.
so i want to fix it, i reset a vscode, but nothing haapen(not only delete vscode but also stored setting)(searching internet)
after all i reset m1 mac, but unfortunatly it still output star character. i want' to know how to fix it.

Related

Eclipse IDE weird blinking space

Does anyone know how to get rid of this thing?
there is this cursor in the terminal
It acts weird with backspacing and removes whole line or doesn't remove and returns to the beginning of line.
I tried restarting eclipse and terminal it didn't help
Usually it single blinking space here it's double space: https://i.stack.imgur.com/tD1kW.png
Tried restarting eclipse, terminal. Didn't help

Terminal cursor in VSCode obscures the command I type so I can't fully see it

When I start to type a command in VSCode terminal, the cursor sort of multiplies and partly obscures the command, so I can't fully read it, as on this picture (it reads "git status"). Besides, if I try out different styles in the settings, the cursor won't change - it remains the same.
VSCode 1.74.1/Mac OS High Sierra 10.13
enter image description here
Changing fonts doesn't help. I tried to reinstall the app, but it's all the same.

VS Code debugging insanity

VS Code Version: 1.47.3 running on OSX Catalina 10.15.3
I've been debugging the current extension project for the past few days without any issues.
Then suddenly, insanity enters my life.
The debugger is still running. Breakpoints have all turned to hollow circles and say they are unbound. The code still stop on these breakpoints, but the line is no longer highlighted, just has a greyish outline, and the variables now show their definition, not their values.
I feel like I have hit a keyboard shortcut and switched to some obscure, unhelpful debug mode, but I cannot find a setting or shortcut that describes doing such a thing.
What did I do, how do I get back to normal debugging? Can anyone help?
Here's screenshot, the debugger is running, the grey outline box is usually filled yellow, or green, the breakpoint is usually a filled circle, and mouse over usually shows the value on the variable, not any more :-(
Tried changing many settings, nothing worked.
Then deleted the node_module folder and ran npm install, et voila!
What changed in there I have no idea. Nothing was installed or removed for some time, but there you are, the mysteries of VS Code debugging.

vscode on mac is incorrectly highlighting text around text blocks

It is very annoying to see that background around code is lighter then the rest of the program. When the cursor moves the highlighting moves up and down to full window width. Can you please propose solution how to turn this highlighting off. Same problem is in output of task log, and in file explorer.
I have deleted all the settings and Application data and I have same problem. I have installed vscode on windows and I do not have this problem with same settings.
Unfortunately this is an issue in Chromium. You can work around this by starting VS Code with --disable-gpu from the command line.
Sean
It appears this can be fixed for some users by selecting a different color profile in macOS display settings. Note that you have to change this separately for all monitors that you use.
For me, "Apple RGB" will show these blocks, and switching to "LED Cinema Display" or "iMac" solves the issue.
See also: https://github.com/Microsoft/vscode/issues/12473#issuecomment-269024219

Emacs - cursor misalignment, and disappearing text

I've been using a copy of emacs (in a Debian VM I ssh to with putty) at work for a couple of months now, and up until now everything has been working brilliantly... but this morning I'm trying to edit a file in shell-script-mode, and am seeing some weird behavior with text around the cursor.
Basically, when I type the following ( [ ] represents my cursor):
export DATABASE[]
After I've typed the first few characters of the variable name the export statement disappears and the variable name aligns to the left margin, and all I end up seeing is (with the cursor out in the wilderness):
DATABASE []
If I then hit CTRL-L, the screen refreshes, and I see the text as it should be displayed... until I start typing, and then the buffer start acting strangly again (characters disappearing, moving, cursor ending up in the wrong place, etc)
I've not, to my knowledge, added anything to my .emacs file since this last worked as I expect it to, so I'm at a loss as to what could be happening here. It doesn't seem specific to sh-mode either - I've tested a few other file types and observed similar strange behavior. Are there any emacs afficianados out there who might be able to point me in the right direction to figure out what's wrong here?
Thanks in advance
I'm not sure what to suggest, but this sounds awfully like an issue with the terminal: I suspect that Emacs redraws the current line whenever it changes and I guess it tries to do so incrementally. If something's got out of whack with your terminal, then it seems quite plausible that the current word would get written at the start of the line (all Emacs sent) and your cursor would get abandoned "out in the wilderness" :-)
Obviously, this is a new change. Since it doesn't sound like the sort of issue that would be caused by Elisp configurations in your .emacs, you should check whether you've recently upgraded one of
PuTTY
Emacs version
SSH version (unlikely...)
Then maybe the relevant tool will have something in the changelog (which maybe you can disable via a config?)
One thing you could check: you say this isn't just SH-mode. Is it "any mode with syntax highlighting"? Maybe Emacs just sends over the wire the text with the current colour?
I had a similar problem of disappearing text using PuTTY / Emacs / Remote AWS Ubuntu when running ABCL LISP in a shell window.
The solution was: I had changed my foreground and background font colors (essentially reversed) in PuTTY but had neglected to change the bold fonts, so they were disappearing into the background.