I'm using the windows-subsystem-for-linux console. Recently it sometimes pauses when typing text, the typed text appears after a few seconds. In the past it worked fine.
I'm searching for what causes this and how I can fix it.
I thought it might be caused by the command completion in bash together with the environment from the Visual Studio Developer Command Prompt (see this question's history)
This seems not to be the case:
The delays happen without the environment from the Visual Studio Developer command prompt.
The delays also happen when I type an answer to a prompt from git add --patch.
Perhaps it is tmux (I'm using version 1.8) or byobu (version 5.74) in combination with the windows conconsole?
What causes this problem?
How can I make bash responsive again?
Related
I've had trouble using Julia in Windows Terminal for the last few releases because the ANSI escapes refuse to render properly unless I enable Legacy Console Mode which helps in CMD prompts, but not in Windows Terminal.
When launched in Terminal, it looks like this:
When launched with --color=no, it looks like this:
Which is marginally more useful, but both the inputs and outputs are muddled by the ANSI escapes, which makes the REPL effectively useless.
My workaround has been to enable the "Legacy Console" and use an alias to launch julia in a separate CMD-based window when I need REPL functionality, but this is disruptive.
I have tried various combinations of (multiple releases of) Windows Terminal (stable and dev), Powershell (stable and dev), and Legacy Console mode. There must be a configuration issue on my machine that I just can't nail down because no one else seems to have this issue.
What am I missing?
Can you file this over at https://github.com/microsoft/terminal/issues?
By all accounts, this should work. Seeing the literal escapes in the buffer like that makes me think that Julia isn't enabling ENABLE_VIRTUAL_TERMINAL_PROCESSING, which they would need for escape sequences to work. Though, if you're on a version of julia from 2021, I would presume that they're aware of that and would be setting that mode by now. (That flag was added in like, 2016)
Hopefully we can help diagnose more over at the Terminal repo ☺️
I have been using the default bash of linux for over 1 year and one of colleague recommended me switch over to using iTerm2 alongwith zsh and oh-my-zsh. He also recommended this post to install and configure those :
https://www.freecodecamp.org/news/how-to-configure-your-macos-terminal-with-zsh-like-a-pro-c0ab3f3c1156/
When i asked what are they the answer he gave me was kind of confusing, so i ask you overlords kind do tell mewhat actually those are and if you have some insights about what actually a bash is, i would be happy to learn that too :)
Thank you all
Pawan
When you are at a command line, typing in commands and reading output you are working in a program called a terminal (or console on windows). The terminal is taking your commands and forwarding them to a program, called a shell, who's job is to actually execute the commands you type in to the terminal and possibly print some output. The output from the shell is then displayed in your terminal window.
The terminal is like the web browser and the shell is like the javascript engine. Your browser takes your input (click, keypresses, mousemoves) and sends them along to javascript which processes those actions and the browser displays the results.
iTerm2 is a terminal emulator meant to be a replacement for macOS terminal and is far more feature rich. It's the terminal program providing you with a command line interface.
ZSH is a specific shell, as is bash, the same way linux is a specific operating system. There are different shells that provide different syntax, features and functionality. There's bash, cshell, fish, powershell, zsh and others.
Installing ZSH, you are essentially downloading a new program and telling your terminal to use that program (say, instead of bash) to process the commands and run scripts.
oh-my-zsh provides a way of managing your zsh configurations, themes and plugins to extend the look and functionality of your shell.
I can't reccomend this setup enough- it's like the cadillac of command lines. You have a good friend there.
Using atom-editor 1.13 with the love-ide package installed to run LOVE2d 10.2 games (windows 7)
Apparently if you create a conf.lua file in the same folder as your main.lua file you can add some configuations to main.lua. So, I've got these lines of code in my conf.lua to show console.
function love.conf(t)
t.console = true
end
But when I go back to my main.lua and type print("ballz"), all I see is a blank LOVE2d game screen with no extra console window. Not really sure if this is because I'm using atom editor or not. Everything seems to be PATH'ed correctly.
On a side note, whenever I run atom using the love-ide package it always tries to install some "dependecy files" like the hyperclick-love package, and the auto-complete-love package. These fail to install because I don't have git installed.. honestly I really don't know what git is, but neither it, hyperclick, or auto-complete seemed like requirements to run my game, so in the spirit of not installing unnecessary things onto my computer I never installed these things... annoying as it is to see this notification always pop up when I start atom. Anyone know if this is contributing to the issue, or know a way to remove these notifications or auto-download-attempts? My LOVE2d code still seems to run without these packages.
Have you set up the terminal emulator in your configuration?
(Windows only) Try using the lovec.exe executable instead of the normal love.exe. The first one attaches to the console that executed the game, the second one ignores it.
Lua has a buffered output, try adding io.stdout:setvbuf('no') to the top of main.lua
I am operating in a linux environment (not familiar to me) and I am handling a bunch of files in django. Bit embarrassing but I seem to have done something subtle to the server that disallows me from setting up separate work stations from my terminal... i.e. emacs file.py & won't work for me; it just says that the emacs window is loading but it won't actually appear - I've waited 5 minutes.
It's not a big deal as emacs file.py works fine and I can "Reset terminal" once I'm done editing the file. However, saving the file could be a problem as the saving options are different between the "&" and "without &" versions of the command. It's such a basic thing that there seems to be no info on it online... any tips?
NOTE: it all started when I mistakenly typed emacs file.py and forgot the & and now something seems to be irreversibly changed that logging in and out again doesn't fix...
When using emacs in a text terminal, start it without the &, you need to run it in foreground. To save a file, use the standard C-xC-s (if your terminal interprets the keystrokes differently, you have to configure the terminal). After saving the file, you can get back to the shell by pressing C-z. It would stop emacs, but you can get back in by typing fg or %em or similar.
To quit emacs, use C-xC-c.
I spent the last 2 days trying to make qt on windows 7 compile a samba-shared project hosted on a linux machine (which is visible on win7 as volume Z).
The problem is that after the first modification of any of the source file, the compilation simply does nothing. I mean literally, no errors, no warning. You click "rebuild", and you instantly get the green bar as if everything was recompiled (and it is a large project so it would take a while), but nothing is actually done. All I see in the compilation output is "Running Jom.exe on path" and (1 ms later) "Jom.exe returned normally"
At first I tought samba shared files were somehow changed in attributes or the like, so I checked and indeed they change to +x on the linux box, but even after resetting the original permissions the compiler silently refuses to compile. Actually it is not even invoked at all.
If I duplicate such "modified - not working" tree on the win7 machine, I have the same behaviuor, while if I duplicate the tree from the linux box straight from the beginning, qt works as expected.
I dont think its a qt issue, but I really have no clue on how to fix this, I cant even try NFS since win7 is Pro and has no additional NFS support.
Of course clearing the project an re-running qmake doesnt change anything.
Just for completeness, note that if I make some change to a source file from windows the file is indeed changed in the linux box, its just the compiler that seems not to be invoked anymore