Re: 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.
Right! I had
PAGER=less
So setting it to cat, helped for the case of using octave
like this:
M-x shell
octave.
However the octave pkg implements what is called
inferior-octave a sort of derived shell mode, which allows
you to send regions of your octave file directly to the
octave executable. However for this implementation changing
the pager does not help.
Any suggestion where in the octave code the shell is used,
in a way that the PAGER setting *does* not have any effect??[1]
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.
Yes, but that the buffer turns "unusable" can also happen if
the result of some octave operation contains many digits,
then I also receive that message and of course I don't want
to delete anything.
Uwe
Footnotes:
[1] Octave-inf uses comint of course.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta