3 ms·

This is actually bearable compared to the new terminal suggestions in vscode. Not only does it autosuggest bizzare completions for commands, it breaks shell com

This is actually bearable compared to the new terminal suggestions in vscode. Not only does it autosuggest bizzare completions for commands, it breaks shell completions. So when I tab a file path, it shoves the absolute path into the partially typed path making it unusable.

tsujamin 10mo ago
I thought I was going crazy, but it started feeling materially worse sometime in last few weeks.
- matltc 10mo ago
  Nope, not crazy. Pretty much solely used it for years but got a lazyvim* setup last week Still has excellent integrated debugging and is more familiar than nvim, but it has really started to get in its own way the past couple minor versions *Not "lazy I'm" (though perhaps I am for letting that slide)
- pests 10mo ago
  after two decades my muscle memory in the terminal is pretty important. that + with keyboard shortcuts ive had multiple jobs ask me to "slow down" when doing screenshares as everything moves so fast.
causal 10mo ago
Yeah for anyone else (especially Mac and Linux users) who recently had this frustration thrust upon you: Go into VSCode settings and search for terminal integration > uncheck.
- wanhandle 10mo ago
  The specific setting is `terminal.integrated.suggest.enabled`.
smj-edison 10mo ago
Ohh, that's what has been happening when I've had tab completion fail recently! Thanks for mentioning it...
torben-friis 10mo ago
It’s so weird, vscode worked flawlessly for me for years and after migrating to neovim a month or two ago I keep seeing complains. Has there been a change lately and in the project, or is it just internet bias?
- hoten 10mo ago
  Recent changes have been a little invasive. The terminal auto complete was a week or so ago, and the popular Gitlens extension also recently pushed a really poor rebase interface. Besides those two in the last weeks, I can't remember any time VS Code has messed up my workflows so badly.
  - Frotag 10mo ago
    I remember thinking wtf when Python import suggestions became disabled by default. https://github.com/microsoft/pylance-release/issues/3579 https://github.com/microsoft/pylance-release/issues/3579
- reactordev 10mo ago
  Copilot
- nateb2022 10mo ago
  If you like nvim you'd probably be interested in helix (https://helix-editor.com/ https://helix-editor.com/) too
- atq2119 10mo ago
  I've seen some weird breakage recently in vscode. The C++ support failing to parse sources correctly (for LLVM), Rust debugging no longer showing vectors properly. Not sure if this is some bizarre interaction with my setup (which is pretty vanilla Ubuntu) or a regression in basic functionality brought on by an over-emphasis on AI features. It is worrying that for many months now, pretty much all the content of changelogs has been about AI.
- petre 10mo ago
  It does weird stuff. I've bitched about it do much to my workmates until they disabled autoformat features wich cause 5k line conflicts in SCM. I'm ysing codium which also does Clippy dmart stuff trying to be helpful and breaks code. They keep pushing AI junk and break functionality to the point that I'm looking for another editor with usable muliple cursors (not *vim and not helix which breaks my vim muscle memory).
sa-code 10mo ago
I don’t know if this is related, but for me the terminal is broken and causes VS Code to crash. It only happens after a command finishes executing and before the shell prompts again
teekert 10mo ago
Ha, was going to come here to complain! It completely breaks my up arrow is history search based on typed chars. First thing I do on a Linux box (and it will blow your mind) is put this in ~/.inputrc : "\e[A": history-search-backward "\e[B": history-search-forward "\e[C": forward-char "\e[D": backward-char If you think that you can just start "enhancing" people's terminal experience like it's a Windows 11 taskbar, I don't think you understand terminal users. It's all good, but make it opt in via some config file (i.e. ~/.bashrc)!
Tyriar 10mo ago
Hi from the VS Code team - I recently went into detail about why we did this in https://github.com/microsoft/vscode/issues/282268#issuecomment-3641970672 https://github.com/microsoft/vscode/issues/282268#issuecomme.... We believe it'll be beneficial overall and go a long way in lowering the bar to make the terminal less intimidating for newcomers. Conflicts with muscle memory was always a big concern which is why we made extra effort to be able to turn it off, the comment below that one outlines some steps we're making to make it more easily configurable inline. On the roll out side, this is what we observed: - It was enabled in Insiders for several months, generally only very positive reactions - It was surprising to me that we shipped this to 25% of our stable users and basically no one complained for 2 weeks before we rolled out to 100% - After hitting 100% of users we did see some backlash like this comment - Of course telemetry doesn't show the whole story, but we try to determine both whether the completion was modified and whether the command was successful after using it and both numbers stayed relatively stable since shipping in Insiders at what we consider pretty good numbers (both accept without editing and command success rate is ~80%).
- nubg 10mo ago
  It's scary to see how Microsoft tracks every single of our keystrokes in vscode.
- itopaloglu83 10mo ago
  Location, location, location. The feedback you receive is from a selection of people who’re trying new features, not people with existing patterns that is broken one of a sudden with an update while they’re trying to get stuff done.
- dobin 10mo ago
  Nobody at Microsoft has ever used this with WSL, and doing a "cd /", and getting autocomplete for "$RecycleBin" and other windows paths? It completely breaks bash autocomplete, and every single suggestion is completely wrong, in every single command i type. I, and probably most uses, just hoped this going away as soon as possible again.
  - 10mo ago

tsujamin 10mo ago

I thought I was going crazy, but it started feeling materially worse sometime in last few weeks.

matltc 10mo ago
Nope, not crazy. Pretty much solely used it for years but got a lazyvim* setup last week Still has excellent integrated debugging and is more familiar than nvim, but it has really started to get in its own way the past couple minor versions *Not "lazy I'm" (though perhaps I am for letting that slide)
pests 10mo ago
after two decades my muscle memory in the terminal is pretty important. that + with keyboard shortcuts ive had multiple jobs ask me to "slow down" when doing screenshares as everything moves so fast.

causal 10mo ago

Yeah for anyone else (especially Mac and Linux users) who recently had this frustration thrust upon you: Go into VSCode settings and search for terminal integration > uncheck.

wanhandle 10mo ago
The specific setting is `terminal.integrated.suggest.enabled`.

smj-edison 10mo ago

Ohh, that's what has been happening when I've had tab completion fail recently! Thanks for mentioning it...

torben-friis 10mo ago

It’s so weird, vscode worked flawlessly for me for years and after migrating to neovim a month or two ago I keep seeing complains. Has there been a change lately and in the project, or is it just internet bias?

hoten 10mo ago
Recent changes have been a little invasive. The terminal auto complete was a week or so ago, and the popular Gitlens extension also recently pushed a really poor rebase interface. Besides those two in the last weeks, I can't remember any time VS Code has messed up my workflows so badly.
- Frotag 10mo ago
  I remember thinking wtf when Python import suggestions became disabled by default. https://github.com/microsoft/pylance-release/issues/3579 https://github.com/microsoft/pylance-release/issues/3579
reactordev 10mo ago
Copilot
nateb2022 10mo ago
If you like nvim you'd probably be interested in helix (https://helix-editor.com/ https://helix-editor.com/) too
atq2119 10mo ago
I've seen some weird breakage recently in vscode. The C++ support failing to parse sources correctly (for LLVM), Rust debugging no longer showing vectors properly. Not sure if this is some bizarre interaction with my setup (which is pretty vanilla Ubuntu) or a regression in basic functionality brought on by an over-emphasis on AI features. It is worrying that for many months now, pretty much all the content of changelogs has been about AI.
petre 10mo ago
It does weird stuff. I've bitched about it do much to my workmates until they disabled autoformat features wich cause 5k line conflicts in SCM. I'm ysing codium which also does Clippy dmart stuff trying to be helpful and breaks code. They keep pushing AI junk and break functionality to the point that I'm looking for another editor with usable muliple cursors (not *vim and not helix which breaks my vim muscle memory).

sa-code 10mo ago

I don’t know if this is related, but for me the terminal is broken and causes VS Code to crash. It only happens after a command finishes executing and before the shell prompts again

teekert 10mo ago

Ha, was going to come here to complain! It completely breaks my up arrow is history search based on typed chars. First thing I do on a Linux box (and it will blow your mind) is put this in ~/.inputrc : "\e[A": history-search-backward "\e[B": history-search-forward "\e[C": forward-char "\e[D": backward-char If you think that you can just start "enhancing" people's terminal experience like it's a Windows 11 taskbar, I don't think you understand terminal users. It's all good, but make it opt in via some config file (i.e. ~/.bashrc)!

Tyriar 10mo ago

Hi from the VS Code team - I recently went into detail about why we did this in https://github.com/microsoft/vscode/issues/282268#issuecomment-3641970672 https://github.com/microsoft/vscode/issues/282268#issuecomme.... We believe it'll be beneficial overall and go a long way in lowering the bar to make the terminal less intimidating for newcomers. Conflicts with muscle memory was always a big concern which is why we made extra effort to be able to turn it off, the comment below that one outlines some steps we're making to make it more easily configurable inline. On the roll out side, this is what we observed: - It was enabled in Insiders for several months, generally only very positive reactions - It was surprising to me that we shipped this to 25% of our stable users and basically no one complained for 2 weeks before we rolled out to 100% - After hitting 100% of users we did see some backlash like this comment - Of course telemetry doesn't show the whole story, but we try to determine both whether the completion was modified and whether the command was successful after using it and both numbers stayed relatively stable since shipping in Insiders at what we consider pretty good numbers (both accept without editing and command success rate is ~80%).

nubg 10mo ago
It's scary to see how Microsoft tracks every single of our keystrokes in vscode.
itopaloglu83 10mo ago
Location, location, location. The feedback you receive is from a selection of people who’re trying new features, not people with existing patterns that is broken one of a sudden with an update while they’re trying to get stuff done.
dobin 10mo ago
Nobody at Microsoft has ever used this with WSL, and doing a "cd /", and getting autocomplete for "$RecycleBin" and other windows paths? It completely breaks bash autocomplete, and every single suggestion is completely wrong, in every single command i type. I, and probably most uses, just hoped this going away as soon as possible again.
- 10mo ago