For a long time inside of Visual Studio 2019, and also pretty much everywhere else in windows, my command prompt has cut out the first few lines/characters when opening it.
Meaning something like this:
Ends up looking like this:
I've tried playing around with the cmd prompt preferences for window and buffer size but it changes nothing.
Does anyone know how to fix this?
Related
I am currently using Visual Studio Code for my local development. I use the terminal for commands but have realized it will sometimes input something like ^[[A instead of the last command I ran when I hit the up button. This is occurring on Bash and my zsh terminal. I am using a Mac as well. Is there any further configuration I need to do in order to show my last command and not this weird symbol that keeps showing up?
The command shows up like this
Okay, I think this solution helped: https://stackoverflow.com/a/40347121/19633998
Basically all boils down to what sort of configuration your terminal has. Mine was defaulted to bin/zsh. Changed it to bin/bash and it seems to be working at the moment.
Hey i was coding a C program with vscode today and out of nowhere when I runned my code through code runner the output looked like this
and when I switched it to the regular bash terminal it looks like this
It seems to run the program fine and for bash it runs terminal commands normally so this might only be the font of the terminal.. How can i fix this back?
this is my settings.json
Edit: Typing on the terminal made me realized that as I type, the text cursor comes glitched in the already printed text which might mean that it is not only the fault of the font?
I know this question looks like dozen of others: but, I am trying to get insight into why this script acts the way it does and if there is any draw back to it like memory leak or other.
The script its simple:
cd "C:\me\python\.venv" && start C:\me\python\.venv\env\Scripts\activate
There is a windows that opens briefly then closes then another command window opens with the virtual environment open as I need. This question is not about the virtual environment in any way. I am trying to understand the command window.
It seems buggy that a command window opens to change directories then closes and then another opens the virtual environment in another window. I can live with this I guess until I run across a seemless way to do this; but, isn't there a better way to do this?
Is the window opening then closing the behavior of the command prompt when changing directories? No! The script could be written simply as:
start C:\me\python\.venv\env\Scripts\activate
and there is still an occurence of a window opening prior to the window with the virtual environment started.
Is there any after affects from doing it this way, like background process open or memory leak or what have you?
Anyone know where to read the "readme" on this behavior?
Thank you much!
Use this code:
cd "C:\me\python\.venv" && C:\me\python\.venv\env\Scripts\activate
the start command is not necessary and that's what opens one more window and lets the previous one close.
This command create a new windows asynchronously.
here is what is happening
I had no issue when i installed it first, everything was fine, but second time i opened my VSC this happend.
I tried changing to xterm-256color but it didn't work.
The data in screenshot showed terminal escape characters that changed
the text color back and forth.
and the thing that received output did not know how to handle those
(not a real terminal emulator) (but thought output is a tty)
You could try to set term to 'dumb'
I am looking for a way to have my Notepad++ window open for editing my code and run it line by line or by sections (more than 1 line) while I am editing. It would be like having a real IDE; the output could be shown in the same window (Notepad++) or directly in the Octave window.
I have tried what many many sites say. That is, writing this:
C:\Software\Octave-3.6.4\bin\Octave\Octave-3.6.5.exe "$(FULL_CURRENT_PATH)"
in the Run window in Notepad++, saving and giving it a shortcut. However, it is still not working. When I tried to run it, the black window starts showing-up but then it disappears and nothing else happens. In my Notepad++ window I have only one line (for now) where I have tried just "b=4" or "3*4". I have done this with and without semicolon at the end. Nothing happens.
I have Windows 8.0, Notepad 6.5.5 and Octave-3.6.4. I already change the octaverc file in Octave to make it work with Notepad++. I have work already only in the command line in Octave and is working fine. The Octave I installed was exactly "octave-3.6.4-vs2010-setup", it says it was compiled for Visual Studio 10. Is that the reason why this is not working?
Any help will be appreciated...
regarding Octave not processing the command: use supposed command line outside the N++ and see if it works. If not, find a way to make it working, then transfer it back to N++ (and use the token "$(FULL_CURRENT_PATH)" instead of concrete filename)
regarding running the code in smaller portions: if you app can accept the code directly in the command line (SQL command line tools I use can do this), then you can use token "$(CURRENT_WORD)" what stands for content of current selection (all tokens are in wiki)