"Peter S. Housel" <[EMAIL PROTECTED]> writes:
> > Ever since the libtermcap / libncurses consolidation, change emacs has
> > problems positioning the cursor and properly updating the screen for
> > character-only devices like the console. It also affects the display
> > in an xterm in non-X mode
|"Russell L. Carter" <[EMAIL PROTECTED]> writes:
|
|> Yup! And also for 19.34b... I've searched all over for the
|> source of this problem, glad to know I'm not alone. However,
|> it only affects one of my three -current boxes, so apparently there is
|> bit of cruft lying around, but I haven
> Ever since the libtermcap / libncurses consolidation, change emacs has
> problems positioning the cursor and properly updating the screen for
> character-only devices like the console. It also affects the display
> in an xterm in non-X mode, i.e., when DISPLAY is *not* set.
>
> This is emacs 2
"Russell L. Carter" <[EMAIL PROTECTED]> writes:
> Yup! And also for 19.34b... I've searched all over for the
> source of this problem, glad to know I'm not alone. However,
> it only affects one of my three -current boxes, so apparently there is
> bit of cruft lying around, but I haven't bee
|Hi,
|
|Ever since the libtermcap / libncurses consolidation, change emacs has
|problems positioning the cursor and properly updating the screen for
|character-only devices like the console. It also affects the display
|in an xterm in non-X mode, i.e., when DISPLAY is *not* set.
|
|This is emacs
