vscode-debugger hangs on the "using Revise" statement - visual-studio-code

When I use Visual Studio code to debug a Julia file, it hangs on the "using Revise" statement. No debugging button seems to do anything, except the stop button. Does anyone know of a solution?
using Revise
println("Hello")

In general, when I get behavior like this, the first step is always to restart my IDE, quit Julia, and re-try. Just tested this and it works for me, can you perhaps open an issue here: https://github.com/timholy/Revise.jl if this is still an issue or provide steps to reproduce.

I finally got it working. In vs-code there is a bright blue bar at the bottom. Clicking Julia env: and changing it from v1.5 to JulaiPro_v1.5.2-1 fixed everything.
It has something to do with:
julia> Base.load_path()
3-element Array{String,1}:
"C:\\Users\\<user>\\.julia\\environments\\JuliaPro_v1.5.2-1\\Project.toml"
"C:\\Users\\<user>\\.julia\\environments\\v1.5\\Project.toml"
"C:\\Users\\<user>\\AppData\\Local\\JuliaPro-1.5.2-1\\Julia-1.5.2\\share\\julia\\stdlib\\v1.5"
The v1.5 path didn't exist.

Related

VS Code terminal showing ERROR on every line with oh-my-posh

My terminal in VS Code has since the previous update shown the word ERROR on every single line. I have installed oh-my-posh a little while back to make the terminal more pleasant to look at and give me some basic information.
Does anyone know where to look, to find the source of the error message? Tyvm :)
Update
Noticed something different when running echo $ as suggested by #kamen-minkov
When I booted Ubuntu up again and my VS Code opened from the previous state it was in the ERROR label was gone:
However. When I opened up a new tab it returned:
The only difference I can notice between the two is that there is a little, unfilled, circle/dot on the left side of the newly opened tab and not the one that opened up with VS Code. Is it some sort of debugger marking or something else? Could it be the source of the problem?
Apparently it's the Shell Integration decorations that's causing the hazards..
// settings.json
"terminal.integrated.shellIntegration.enabled": false,
"terminal.integrated.shellIntegration.decorationsEnabled": "never",
disable these settings and oh-my-posh error label will be gone :)

DOCTYPE Emmet shortcut stopped working VS Code [duplicate]

Every other snippet is working, but !+tab is not.
! snippet is not working
other snippet is working
I am using Visual Studio Code. I'm using 1.69.0. It was working before, but I wanted to add net html file, named that new.html, because I had index.html already. After that this script stopped working on every html file, but other scripts like "a", "div" etc. is working.
The v1.69.2 recovery release is out now. Emmet in html is working as it should for me now.
Looks like it will be in the Recovery Release, see https://github.com/issues?q=is%3Aissue+label%3Acandidate+repo%3Amicrosoft%2Fvscode+repo%3Amicrosoft%2Fvscode-internalbacklog+repo%3Amicrosoft%2Fvscode-remote-release+milestone%3A%22June+2022+Recovery+2%22+.
Don't know when the recovery release to Stable - presumably v1.69.2 - will be released. The .1 release is out and the fix is not in it.
It has been fixed though, see https://github.com/microsoft/vscode/issues/154375, and should be in the Insiders Build tomorrow (07/13/2022).
Testing the latest Insiders: ! is working. As is ul>li*3 type expansions (although that never stopped working for me - but it has been reported elsewhere). Should be in the v1.69.2 release out soon.
It is a known issue with the v1.69 release, see html emmet suggestion not automatically display or https://github.com/microsoft/vscode/issues/154517 for example. Lots of issues on github on ! and * not working.
So the emmet snippet will not appear automatically when you type !, but you can press Ctrl/Cmd+Space (which is the command Trigger Suggest) to make it appear and select normally.
Try Ctrl/Cmd+Space for anything emmet-related nnnnnot working in vscode v1.69.
You could also go back to v1.68 to solve the issue.
Try to write "doc" instead of "!". "doc" works for me.
On Windows 10, this worked for me:
Go to "Settings" and type "emmet.trigger" in the search
A checkbox for "Emmet: Trigger Expansion On Tab" will appear
Check the checkbox for allowing Emmet to trigger expansion on tab
After I did that, it worked just fine for !+TAB and any type of mulitpliers (i.e. li*4+TAB).
You need to check this option or put "emmet.triggerExpansionOnTab": true in settings.json to use the emmet abbreviation pressing TAB. I realized this ones what is not working:
!, lorem, >, and .
Examples of use: ul>li, li3, ul>li*3
None of them shows the preview of the emmet, and you can't use them pressing TAB without enabling the option that I sayed above, and even checking the option you won't be able to see the previews, you'll need to know them by yourself and press the TAB even though nothing showing that it's a emmet abbreviation.
You can use CTRL + SPACE too.
Edition Windows 11 Pro
Version 21H2
VSCODE Version 1.69.0
I had the same issue with the ! not working. I found another shortcut that does the same thing: type html:5, and press enter.
Looks like a bug, I have the same problem with 1.69.1, the VSC team is aware and fixing it. Should be fixed with the next release soon.
Meanwhile, you can use either HTML:5 or doc
meanwhile use "HTML:5"
enter image description here
or use "doc"
enter image description here
While #Mark's answer works, another work around would be to use the html:5 snippet which still works as expected in v1.69
Yes, I am facing this issue too since the latest update.
Somehow the solution I have got is :
You can check the box “Emmet: Use Inline Completions”
In settings by typing “emmet” in the setting’s search.
You can see the suggestion now and choose it by pressing the tab.
This is the solution I have got till now but hoping that we could have the previous version back.

Emmet html5 boilerplate shortcut not working as before [duplicate]

Every other snippet is working, but !+tab is not.
! snippet is not working
other snippet is working
I am using Visual Studio Code. I'm using 1.69.0. It was working before, but I wanted to add net html file, named that new.html, because I had index.html already. After that this script stopped working on every html file, but other scripts like "a", "div" etc. is working.
The v1.69.2 recovery release is out now. Emmet in html is working as it should for me now.
Looks like it will be in the Recovery Release, see https://github.com/issues?q=is%3Aissue+label%3Acandidate+repo%3Amicrosoft%2Fvscode+repo%3Amicrosoft%2Fvscode-internalbacklog+repo%3Amicrosoft%2Fvscode-remote-release+milestone%3A%22June+2022+Recovery+2%22+.
Don't know when the recovery release to Stable - presumably v1.69.2 - will be released. The .1 release is out and the fix is not in it.
It has been fixed though, see https://github.com/microsoft/vscode/issues/154375, and should be in the Insiders Build tomorrow (07/13/2022).
Testing the latest Insiders: ! is working. As is ul>li*3 type expansions (although that never stopped working for me - but it has been reported elsewhere). Should be in the v1.69.2 release out soon.
It is a known issue with the v1.69 release, see html emmet suggestion not automatically display or https://github.com/microsoft/vscode/issues/154517 for example. Lots of issues on github on ! and * not working.
So the emmet snippet will not appear automatically when you type !, but you can press Ctrl/Cmd+Space (which is the command Trigger Suggest) to make it appear and select normally.
Try Ctrl/Cmd+Space for anything emmet-related nnnnnot working in vscode v1.69.
You could also go back to v1.68 to solve the issue.
Try to write "doc" instead of "!". "doc" works for me.
On Windows 10, this worked for me:
Go to "Settings" and type "emmet.trigger" in the search
A checkbox for "Emmet: Trigger Expansion On Tab" will appear
Check the checkbox for allowing Emmet to trigger expansion on tab
After I did that, it worked just fine for !+TAB and any type of mulitpliers (i.e. li*4+TAB).
You need to check this option or put "emmet.triggerExpansionOnTab": true in settings.json to use the emmet abbreviation pressing TAB. I realized this ones what is not working:
!, lorem, >, and .
Examples of use: ul>li, li3, ul>li*3
None of them shows the preview of the emmet, and you can't use them pressing TAB without enabling the option that I sayed above, and even checking the option you won't be able to see the previews, you'll need to know them by yourself and press the TAB even though nothing showing that it's a emmet abbreviation.
You can use CTRL + SPACE too.
Edition Windows 11 Pro
Version 21H2
VSCODE Version 1.69.0
I had the same issue with the ! not working. I found another shortcut that does the same thing: type html:5, and press enter.
Looks like a bug, I have the same problem with 1.69.1, the VSC team is aware and fixing it. Should be fixed with the next release soon.
Meanwhile, you can use either HTML:5 or doc
meanwhile use "HTML:5"
enter image description here
or use "doc"
enter image description here
While #Mark's answer works, another work around would be to use the html:5 snippet which still works as expected in v1.69
Yes, I am facing this issue too since the latest update.
Somehow the solution I have got is :
You can check the box “Emmet: Use Inline Completions”
In settings by typing “emmet” in the setting’s search.
You can see the suggestion now and choose it by pressing the tab.
This is the solution I have got till now but hoping that we could have the previous version back.

How to fix code highlighted in red in VS Code

This happened suddenly after I restarted my computer, all of a sudden any code I type is highlighted in red. Does anyone know how to fix this? See image.
OS: Windows
UPDATE:
This is the weirdest thing, I simply restarted my computer (again), and it just disappeared. It's a shame, because I didn't get to figure out how it happened, but it's good to know about this Bisect feature in VS Code!
This might have something to do with one of your extensions acting up.
VScode has a nice feature to help you find the specific extension that's causing problems without you having to check each one individually.
VScode bisect function.
Press crtl+p then type bisect
It may be one of your extensions that makes this. You can check it by disabling them one by one(ctrl + shift +X and then choose installed). I guess maybe an extension that belongs these:enter image description here.
Hope helpful.

Really weird eclipse keyboard behavior/bug?

I am using Helios on Mac Snow Leopard. I don't know why but all of a sudden my arrow keys and delete button start not working only on Eclipse (so Eclipse ignores them) but the rest of the buttons works just fine. There is no exception/error thrown anywhere on the screen. I don't exactly know how to reproduce this malfunctioning.
All I can say, I am having exactly the same problem with this guy down here. Bad thing about it, the post sent in year 2002:s
Is there any one of you having the same issue? Any suggestions?
Edit:
Please mark "me too" on this bug report hoping that it will be fixed soon.
I was able to "restore" arrow and backspace keys by "Refreshing" the project.
UPDATE: 7/11/2017 I've not had this problem reoccur in a couple of years now. Either Eclipse fixed the problems or a more recent version of Mac OSX has fixed something. For the record I'm running Eclipse 4.5.2 on OSX 10.11.6.
UPDATE: 4/29/2011 Now it looks like this is not a Workspace or keyboard preferences issue at all. This just happened again but restoring from older Workspaces did not fix the issue. I finally had to reboot my Mac which seemed to resolve things. I'm going to try a restart in the future immediately if I see this again. I've submitted this bug with Eclipse. Please add a "me too" comment to the bug if it has not been fixed and you can reproduce this on your system.
I also have heard that on Macs, you can solve this by getting the unit to sleep either by closing the laptop lid or pulling the Apple menu down to sleep, wait a few seconds, and then starting it again. I've not tried this yet.
BTW, when this happens refreshing and other mechanisms have not worked.
UPDATE: 4/13/2011 Although the below instructions did fix my keyboard issues, I discovered other problems with my configuration and was finally forced to recover my Workspace from backups.
NOTE: This is not recommended but is here for information purposes. Typically these keys are handled by the native widget and are not defined.
So I just had the same problem under Eclipse 3.6.2.r362 on Mac OSX 10.6.7. Delete to the left and arrows not working. They worked in other applications. Option-Arrows worked fine to move a selection around. Arrows worked in the keyboard preferences window. Switching to another application and back didn't work. Restarting eclipse made no difference. Switching keyboard schemes from Emacs -> Default -> Emacs didn't work. Pressing all of the modifier keys did nothing. I tried all of the following and nothing works: Rebuilding the project, refreshing the source, restarting Eclipse.
Finally, I was able to fix this by going to the Preferences -> General -> Keys and resetting each of the bindings for the following keys. The bindings for each of the keys were blank.
Delete Previous to backspace
Line Up to up arrow
Line Down to down arrow
Previous Column to left arrow
Next Column to right arrow
This worked but then I noticed that all of the emacs key bindings were screwed. I thought they worked before so I'm not sure when this happened. I had to restore default key bindings (after writing down the ones that I had customized) and then restore my customized settings.
Makes me wonder what other key bindings have been reset and what did it. Frustrating but at least I can get back to coding.
If you see the same symptoms on Eclipse Windows, just press all your mouse buttons (including the wheel if you have one) at the same time together, and that seems to fix it.
Same weird problem, this worked for me: I just figured out that if I switch editor and then back again, backspace starts working again. (source)
For me, the root cause was my mouse.
Backspace and navigation keys did not work. I could fix this temporarily by manually setting the key bindings as described on this page.
The root cause and permanent solution was fixing the stuck 3rd mouse button on my Evoluent Vertical Grip mouse. Since I never used that button, I didn't notice that it was permanently engaged, probably from the mouse sliding off the desk on to the ground one too many times. Once I was able to get the button unstuck, the problem was solved immediately.
This was really frustrating. I spent weeks wondering why it was happening and sporadically searching the web for answers. Of course I had a temporary solution, but the fact that it kept happening was annoying. I tried reinstalling Eclipse from scratch, trying different versions and switching workspaces, but nothing worked. I'm surprised it ended up being a stuck mouse button after all that.
Also check that someone has not installed the vrapper plugin so that Eclipse accepts vi/vim like commands. If this is the case pressing i allows you access the editor window. If you are unaware that a work college has installed it (glares at someone) it can be a right $%#&$#! If installed there will be a V icon in the top toolbar. This plugin can be removed by going to the directory where Eclipse is installed in a term window and running
find . -name '\*vrapper\*' -exec rm -rf {} \;
It is that or tax you brain but supposedly increase your productively by learning all the Vim commands. Hope this helps someone...
In Windows and Linux environments I have experienced such issues when the system believes a modifier key is pressed. By pressing and releasing all modifier keys the issues often perish. However, on OSX I did not experience such issues, so this might be entirely wrong.
If the simple idea does not solve the issue, you could try to start a new workspace to see whether some preference causes the issue; or you could download a new Helios instance to check whether its working. I know, these are all serious issues, but may locate the problem.
Otherwise, you shall take a look at the question asked not long ago about keyboard issues, maybe there is some hint how to solve it.
I had the same problem with the "Delete" key in Eclipse 3.7.0 on Windows Vista. Suddenly the key stopped working and I couldn't figure out why. Recently I found a way to fix it when the problem occurs - it works for me every time:
In a code editor window in Eclipse, hoover on some method or variable or what have you, until the popup window appears with "Press 'F2' for focus" in the lower right corner. Click the popup window to switch focus, then click the editor window again so the pop-up disappears, and voilà, the Delete key works again.
Had this same issue. Turned out to be my middle button on my wireless mouse being pushed in my laptop bag. Normally I turn my mouse off, but this time I forgot. Glad that other people had this problem, otherwise I'd still be looking for the cause.
I have encountered this problem for years. It happens so infrequently however, that I almost always forget what I did to solve it. Restarting fixes it most of the time i think, and a few times "refreshing" worked, but nothing works 100% of the time.
In any case, someone on the bug report suggested just putting MacBook in Sleep cycle. This worked like a charm for me, so putting it out there for future reference.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=344290#c24
Incidentally, I have experienced similar behavior with other applications, in particular Firefox. My thought is that it has to do with key bindings in general, and any application that provides overrides for defaults in the OS (this is a pretty huge assumption, so take with a correspondingly large grain of salt). I have also had this happen to me in Xcode, but a simple restart of the application fixes, whereas with Eclipse that wasn't sufficient most of the time.
Using eclipse JUNO on Win XP I also experience this issue.
Restarting the workbench using File > Restart does not work, but closing eclipse and starting again with -clean at the command prompt the keys start functioning again, without restart windows.
Note - Just found this fix elsewhere - you can fix this on Mac OSX by force-killing finder. That worked for me perfectly. Didn't need to restart!
For some odd reason, opening the preferences window and closing it right away, solves this problem for me (other solutions here didn't work).
Just in case this helps someone... I accidentally got things working again by doing the following:
Opened the offending file from the command line (I used 'vi').
Made the edit I wanted to make and saved the file.
Went back into Eclipse to refresh and redeploy my app.
As soon as the editor (this was a JSP file, btw) refreshed, I once again had full use of arrow, delete, etc.
YMMV
Jack
MacBook Pro 10.6.8, Eclipse Helios all of a sudden delete and arrows no longer work. Reboot worked for me.
I am also facing the same problem. In my case only the delete key is not working. I am using eclipse helios in ubuntu. The solutions given here are not working. However, restarting solves the issue.
I have the suspicion that this happens after updating Java on my Mac. So after updating Java it seems to be a good idea to reboot the machine always.
I got this same problem when I started using JRobot. In one piece of code I pressed the mouse but did not release. By releasing the mouse in a later piece of code I managed to solve the issue. You can recreate this problem using the code below. Release the mouse button to solve the issue.
Robot robot;
try {
robot = new Robot();
robot.mousePress(InputEvent.BUTTON2_MASK);
//robot.mouseRelease(InputEvent.BUTTON2_MASK);
} catch (AWTException e1) {
// TODO Auto-generated catch block
e1.printStackTrace();
}
Pressing left and right mouse buttons simultaneosly multiple times worked for me.
Using eclipse Luna (4.4) on Redhat and viewing via Xming (Windows 7, 64-bit), I could not use backspace, arrows, delete or even enter, but alphanumeric worked. This problem was not intermittent, but always there from the start. For me, I found that setting a break-point in the code, running and allowing eclipse to switch perspectives fixed it every time. Hope it helps someone else as the above suggestions (ie switching editors, changing key mappings, refreshing and restarting eclipse) did not work for me.
One interesting diagnostic of the problem I had was that going to the screen where you change the key-mappings, I was able to use the delete key. But not in java files or untitled text files.
WORKED!!!
I'm using Eclipse Luna and Windows 7, but guess it works in all kinds as well.
In Eclipse, go to tab Window->preferences->General->keys
Then, find the Command "Delete" and "Delete Previous" in the list, and check if
they are assign with something or not. If it is assign with the wrong key, click in "Unbind Command".
Just select the command that you want to change and press the key that you want to be on the "binding" field.
I think it works for Next, Next Column, Previous, Previous Column, Line Up, Line Down, or whatelse you want!!
Had, similar problem with not working “enter” and “delete”, none of above methods helped me – to fix problem I had to switch to default java formatter (one I was using somehow stopped working)
For me it was that the keyboard layout accidentally changed to vietnamese language and there are inherent key mapping combinations that create trouble when editing.