Dan Davison stats.ox.ac.uk> writes:

Why? Quick edits? Remote session?

For whatever reason you're running in a terminal, there's probably
another way to do what you want with the X interface.

Also, xterm is a highly under-rated terminal emulator, and is very
configurable (give the man page a look).

Perhaps your problem is in how you choose to set things up, rather than
a real Emacs problem?

Joel

adamsonj@email.unc.edu (Joel J. Adamson) writes:

gnome-terminal is a very capable terminal emulator though, and runs
emacs fine as far as I can tell.

[The original report is quite confusing, so it's very hard to tell
exactly what the problem even is...]

-Miles

Miles Bader gnu.org> writes:

I agree, however I've found that for a lot of things where I went
"against the grain" I later found a much easier way to do things.
Editing remote files, for example, is much easier using tramp than
relying on the remote system's version of Emacs (my university has not
updated Emacs since 2000).

I also thought Xterm was crap until I gave it a real shot, and now I use
it all the time.

On Mon, Jul 14, 2008 at 08:34:11AM +0900, Miles Bader wrote:

Fair enough! Let me try to give a concrete example. I have a buffer in
Emacs-Lisp mode, and type the characters

'(defun'

Dan Davison stats.ox.ac.uk> writes:

Interesting, that happens for me too, it does really seem to be a bug in
gnome-terminal. It doesn't seem to happen if font-locking is turned
off.

Note that what emacs sends to the terminal is _not_ the same as what's
in the buffer, it's a sequence of characters which should make the
terminal render the display Emacs wants to present.