-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with GNU screen #6
Comments
Just as a temporary fix, you can always use another line editor with zrc. Run The problem is some terminals handle escape sequences differently. Working with |
rlwrap also messes things up. Not only with zrc, also with tclsh. So no. I'll keep using fish or Tkcon. Which brings me to another thing, the readline history. I could open another ticket, but why not just mention it here. In fish, I can do this:
When I press up and bring that from the history, fish remembers the entire sequence and prints it entirely. rlwrap doesn't. rlwrap will print every line individually as I press up. At first I thought it was only rlwrap's fault, but then I saw that zrc without rlwrap also fails to bring the entire command sequence, printing one line at a time. Maybe that could be improved in the future? |
When I test zrc on the interactive command line, I often have these problems:
The problem seems to be related to GNU screen. I use the Fish shell in GNU screen and my terminal application is stjerm, which is almost extinct nowadays. But I don't think stjerm is to blame. The same problem is not reproducible on sakura (another terminal application), until I start a GNU screen session in sakura. Then the problems begin again.
I never had any problem with GNU screen and Fish or Bash, so I am guessing Zrc and screen don't get along too well. It's hard to find anyone who still uses stjerm, but GNU screen is very popular so it's probably a good idea to check that. Maybe tmux too, but I never used it so I don't know if it has issues with Zrc (or any other shell for that matter).
The text was updated successfully, but these errors were encountered: