Quantcast
Viewing all articles
Browse latest Browse all 5995

VSCode Terminal with Strange Behaviour on Xubuntu VM

I set up a Xubuntu VM through Oracle VM VirtualBox Manager a few weeks ago and haven't used it much but this issue has persisted pretty much since I set it up.

The native terminal is a bit slow - sometimes I need to hit enter twice for it to refresh it the command doesn't return anything in terminal (e.g. after touch index.html if I hit enter, there is no new line, though after ls there is a new command line as expected (below the contents of the current directory). This is a bit frustrating but not the main issue.

The main issue pertains to the VS Code terminal. The actual text editor works pretty much fine, however the built-in terminal for VS Code will only update when I hit spacebar or possibly a couple of other keys (I haven't texted exhaustively).

As a concrete example, if I was to type cd Documents/repos/project1/pages/, I would see the following:

  1. cd after typing in 3 characters
  2. Nothing until I hit enter, when the rest of the line would appear. Obviously, this can make it quite annoying to deal with typos.

In general, this isn't a massive problem when I can use tab completion to navigate directories etc., but as soon as tab completion isn't solving all of my problems it makes the terminal quite frustrating to use.

Note: Whilst testing as I wrote this, I found that it was also just completely freezing after the first character at times, which I hadn't seen before (still updating after hitting enter) - this was the only time I had tried to use the VM outside of full screen which maybe interfered with something?.

Some context for the specs on the VM:

  1. Base Memory: 8GB
  2. Processors: 2 (of 8)
  3. Boot order: Hard Disk, Optical, Floppy (no idea if this is relevant or useful)
  4. Video Memory: 32 MB
  5. Acceleration: 3D

Plenty of googling attempted, but can't find anything specific to this. Wondering if there's a specific VM spec I can upgrade that should tackle this or if it's a more fundamental problem?

Have looked through the VS Code terminal settings but nothing jumped out to me.

I'm unsure if this is a hardware or a software fix, so if I'm squarely in the wrong place apologies and please direct me to the best place for the problem.


Viewing all articles
Browse latest Browse all 5995

Trending Articles