Axel Beckert - 16.07.17, 23:26: > Hi, > > Axel Beckert wrote: > > So my current plan is to document the issue in README.Debian with the > > following suggestions as workaround, depending on the ncurses-term > > versions installed locally and remote: > > > > * Use "env TERM=xterm screen" (or similar). > > * Use "term screen" inside .screenrc > > * Uninstall ncurses-term locally or install ncurses-term on the remote > > > > machine. > > > > Exact wording still needs to be determined. Suggestions welcome, > > especially from users which ran into that issue and hence have a > > better feeling what works in which case and what doesn't. > > Based on the feedback on this mail, I've made a first try on > documenting ways out of that $TERM fiddling hell: > > https://anonscm.debian.org/cgit/collab-maint/screen.git/commit/?id=5aa1cd4cb > af92e2d7570b102e9069d8898ca4807
Quoting in mail: > diff --git a/debian/README.Debian b/debian/README.Debian > index 1797fc4..6d4479c 100644 > --- a/debian/README.Debian > +++ b/debian/README.Debian […] > +Q: When I'm using ssh from inside screen, I get the error message > + "Error opening terminal: screen.xterm-256color." or similar. > + > +A: The TERM variable inside a screen session (which is then passed to > + the remote shell by ssh) depends on two things: > + > + 1. Availability of of specific termcap entries locally. > + 2. Value of the TERM variable when the session was started. > + > + To avoid this error message, the best way is to start a new screen > + session under a different circumstances, but there are also ways => "under different circumstances" I am not sure whether I´d understand this as "under different circumstances" is quite unspecific. I´d think I´d rather write "with different terminal configuration" > + without starting a new sessions. You have several options: > + > + Without starting a new screen session: > + > + * Start ssh with "env TERM=screen-256color ssh". > + > + * Install ncurses-term on the remote machine and then start a new > + ssh session. (Might help, depending on the remote distribution.) > + > + Exiting the current screen session, change one of the following and > + start a new screen session: > + > + * Add "term screen-256color" to ~/.screenrc or /etc/screenrc on > + your local machine. > + > + * Start the new screen session with "env TERM=xterm screen". > + > + * Start the new screen session with "screen -T screen-256color". > + > + * Uninstall ncurses-term locally and then start a new screen > + session. (Might help, depending on the remote distribution.) Whoa, I wondered whether to give this many options, but… I think its okay :) as you added the options that IMHO works best at the beginning of the lists. > + If "screen-256color" is not available on the remote distribution > + either, especially if it's not a recent release, try just "screen" > + instead of "screen-256color". You might want to add a link to the bug report in README.Debian. I know you added a hint to it into the Changelog, but I think I´d add it here as well for people who want to know the background behind all of this. Thanks, -- Martin
signature.asc
Description: This is a digitally signed message part.
