I am using vim plugin in VSCode. Sometimes, when I am in normal mode, I like to use my mouse to navigate, especially, if it is a big file. So I scroll to the new place, click there and try to begin editing my code by going back to the insert mode. However, when I use the insert mode, the cursor goes back to where it was before.
Vim cursor does not seem to remember the position of the new cursor updated on click. Is there any way to change this behaviour?
I have found a solution, downgrade from the latest v1.17.0 to the previous one.
To do so follow these steps:
Open extension navigation
Right click the Vim extension
Select "Install another version"
Click on 1.16.0
Fixed it for me. Hope this works for others that may have this issue.
I stumbled upon this thread on github.
As for the rest of the people having issues after version 1.17.0 there is now a new version 1.17.1 that might fix some of the issues you're facing.
So looks like it was a problem in version 1.17.0 but was fixed in the update 1.17.1
Related
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.
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.
I installed GitLens in VS Code. Then it asked if I wanted to try the GitLens+ features. I clicked "Yes". Now I am stuck at the welcome screen and can't get past it. Any ideas how to get rid of this annoying screen?
Uninstall gitlens extension. Productivity extensions shouldn't reduce productivity by putting up adds that can't easily be closed.
I had the same problem, but I was able to solve it by following the steps below.
Open the sidebar extension
Click the down arrow to the right of the uninstall
Install another version
Install 11.7.0
Reload
But there was no Gitlens in the sidebar
So next
"git lens: show welcome view" in the command palette
Select "git lenses layout" in "view" of "quick setup"
Gitlens is displayed in the sidebar
Then install the latest version
Gitlens is displayed in the sidebar
I hope it helps you even a little.
Go to VS Code command Pallete and select GitLens+: Sign out of Gitlens+
that should get you to the previous experience.
you can also use the the VSCode Command Pallete to display the views you want, such as
I think I had the same issue on Windows (now I'm on my mac) so I went back to Windows, created a new account, and started the trial since logging off of my account on Windows didn't result in that scenario.
I couldn't reproduce it on Windows either.
I'm thinking that might be a glitch, I'm sure you already tried to close VSCode and open again, so, maybe try to sign out and sign in again.
If you want to remove the "home" view, use the elipses on the top right and untick it. Also, check if the other views are enabled.
The problem here is that when we install GitLens extension then all the GitLens features and buttons are added under the generic source control tab (Ctrl+shift+G). Even though GitLens creates a new tab of its own and it looks like all features and buttons are hiding behind the welcome screen. This is not the case and everything but the welcome screen is under the generic source control tab. Poor design choice indeed.
Hide GitLens+ Features from the Command Palette GitLens+: Hide GitLens+ Features
To restore from the Command Palette GitLens+: Restore GitLens+ Features
Step 1. Uninstall GitLens
This avoids fiddling with settings to try to stop it being nag-ware.
Step 2. Install Git Graph
This has the nicest "railway-track" display of commits that I have come across, although the dev seems to be not responding to contact during 2022.
An alternative is Git History, which remains under active development, although its railway-track display is less compact and efficient.
I'm checking out this Visual Studio Code but when you middle-click for scrolling as you would everywhere else it selects code instead of scrolling. Not exactly like a left click but still, annoying for me. Is there a way to solve this issue?
No, unfortunately not (yet). But you can contribute here on github to make it happen.
Since the issue has been reported but not fixed for 5 years, you should upvote that issue, and then use the autohotkey workaround:
https://github.com/qooqu/vs-code-mbutton-scroll-ahk
(You have to hold the middle-button down in vscode and drag the mouse up or down to autoscroll, and it scrolls one line at a time instead of smoothly, but it's much better than nothing.)
(To use: Install AutoHotkey, then you can download and run the linked .ahk file)
There's an extension that allows this kind of behaviour in Visual Studio.
Visual Studio Marketplace Link
Hey I just updated Sourcetree on my mac to the latest version (2.2).
Where did git-flow go?
And how do I re-enable this functionality?
I just lost myself without it!
I have the same problem here, you can still use Git-Flow
From the menu: "Repository-> Git flow /HG flow -> Next action"
Using the hotkey: "⌥+⌘+F.
But still not able to get the button back... :/
On the download page the button is also gone:
https://www.sourcetreeapp.com/
Alternative you can download the previous version here:
http://downloads.atlassian.com/software/sourcetree/SourceTree_2.1.dmg
https://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.7.0.32509.exe
UPDATE:
The have a new version of SourceTree Mac v2.2.2(51) / Win: v1.8.2 and when you have this version you can customize you toolbar by clicking on the toolbar with your right mouse button. Then you can enable the git flow button.
Downloads:
Mac v2.2.2:
https://downloads.atlassian.com/software/sourcetree/SourceTree_2.2.2.dmg
Windows v1.8.2:
https://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.8.2.exe
Here is what you can do if you have SourceTree v2.2.3. (I'm sorry but I don't have enough reputation points to attach the image)
Edit: Now I can upload the GIF, thanks!
Enabling Git-Flow button SourceTree - GIF
The corresponding Windows version is 1.8.1.0.
The hotkey is Alt+Shift+F
UPDATE: It appears that Atlassian has pulled release 1.8.1.0. When you download now, you get version 1.7.0.
Jens Schumacher has just wrote that the git-flow button will be back in the next bugfix release. As for now, as others suggested, either roll back to a previous version, or use a hotkey (Alt+Shift+F for Windows, ⌘+⌥+F for OS X).
Git-Flow button is back as of update 1.8.2.0. So this issue should be resolved: just update SourceTree and it will be back.
As many people say here, you can use the hotkey
for OSX ⌘+⌥+F
for Windows Alt+Shift+F
But, also you can configure the toolbar to show the gitflow icon again. You just have to do a right click on the toolbar, select "customize toolbar..." and drag the icon back to the place it use to be. As simple as that.
I hope it helps.