shell terminal is not fully functional, octave, term

Uwe Brauer writes: It should be possible to tell Octave not to use a pager. In many cases, setting the environment variable PAGER=cat does what you want. Eg, this works for git-help. There may also be an Octave setting for this. I don't understand what you mean by "unusable". I run into this issue occasionally with other programs. If I don't want the help text in the buffer, I just delete it. For the literal CRs (^M), M-% C-q C-m RET RET ! will clean those up. RFE for comint modes: We should implement "unicode newlines" in shell and similar modes by default. By that I mean that CRLF, or CR or LF not embedded in CRLF, or Unicode LINE SEPARATOR, or Control-1 0x85 NEL should be interpreted as new line function. See UAX #14 http://unicode.org/reports/tr14/. Note that this is NOT about Unicode conformance as such. It's just that (absent specific configuration by the user) UAX #14 specifies reasonable behavior that many applications will implement, and therefore will be "intuitive" to users. It's a good default. However, I suspect that full conformance to that standard will prevent shell mode and friends from handling "spinner" style progress meters properly. So we should have an option to interpret CR as `beginning-of-line-and-clear-to-end-of-line' or so, at least in some contexts (ie, when not immediately followed by LF). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta