General discussion about XEmacs

Leonard Shar | 24 Jul 2006 20:39

Terminal mode does not seem to deal with newlines "correctly"

I do M-x term
Then run /bin/csh in that terminal window.  
If I try to run (say) "less" in taht window at the end of each line of output
I get a linefeed, but no CR.  THe following line just starts at the column
position where the previous line ended.
I get similar behavior if I run vi or mutt in the window.
(The fancy terminal features of mutt seem to work OK -- it's just that the
text lines get shifted out to infinity.)

I am running xemacs 21.4 (patch 13)
When I do echo $TERM inside the terminal window it says "eterm"

Is there something special I need to do to make this work?

Thanks,
Leonard

headers

Glynn Clements | 26 Jul 2006 18:40

Re: Terminal mode does not seem to deal with newlines "correctly"


Leonard Shar wrote:

> I do M-x term
> Then run /bin/csh in that terminal window.  
> If I try to run (say) "less" in taht window at the end of each line of output
> I get a linefeed, but no CR.  THe following line just starts at the column
> position where the previous line ended.
> I get similar behavior if I run vi or mutt in the window.
> (The fancy terminal features of mutt seem to work OK -- it's just that the
> text lines get shifted out to infinity.)
> 
> I am running xemacs 21.4 (patch 13)
> When I do echo $TERM inside the terminal window it says "eterm"
> 
> Is there something special I need to do to make this work?

"stty onlcr" may help, as may adding the following to
~/.xemacs/init.el:

  (push '("/.*" . binary) process-coding-system-alist)

--

-- 
Glynn Clements <glynn <at> gclements.plus.com>

headers

Leonard Shar | 26 Jul 2006 19:47

Re: Terminal mode does not seem to deal with newlines "correctly"

"stty onclr" did not work, but 
  (push '("/.*" . binary) process-coding-system-alist)
worked perfectly.

Thank you very much.

On Wednesday 26 July 2006 09:40 am, Glynn Clements wrote:
> 
> Leonard Shar wrote:
> 
> > I do M-x term
> > Then run /bin/csh in that terminal window.  
> > If I try to run (say) "less" in taht window at the end of each line of output
> > I get a linefeed, but no CR.  THe following line just starts at the column
> > position where the previous line ended.
> > I get similar behavior if I run vi or mutt in the window.
> > (The fancy terminal features of mutt seem to work OK -- it's just that the
> > text lines get shifted out to infinity.)
> > 
> > I am running xemacs 21.4 (patch 13)
> > When I do echo $TERM inside the terminal window it says "eterm"
> > 
> > Is there something special I need to do to make this work?
> 
> "stty onlcr" may help, as may adding the following to
> ~/.xemacs/init.el:
> 
>   (push '("/.*" . binary) process-coding-system-alist)
>

(Continue reading)