From: jimka <jimka@rdrop.com>
To: help-gnu-emacs@gnu.org
Subject: emacs shell cursor movement is broken in 22.1
Date: Thu, 13 Mar 2008 13:44:16 -0700 (PDT) [thread overview]
Message-ID: <3c0dda17-2476-4d2b-b1f2-c101b4a0f576@s13g2000prd.googlegroups.com> (raw)
I've used the emacs shell for 20 years and emacs 22.1 has added a
bunch
of "features" which make like difficult.
Can someone explain to me how to make the cursor navigation functions
work in a more sane way.
E.g.,
1) if i use the shell command !!:p to print the previous shell
command.
In previous versions of emacs i could simply edit that line and press
return and
it would enter it as the next input to the shell. Now, emacs 22.1
ignores it
when i press enter on such a line.
2) if i use !!:p to print the shell command such as "ls -R
xyzzy*.x.y.*"
then move the curser up to the line and insert something at the
beginning of the line
like cd /xyzzy; so that the new line content is "cd /xyzzy;ls -R
xyzzy*.x.y.*"
At that point if i press C-E to go to the end of the line and C-A to
go to
the beginning of the line, the cursor stops at the ls -l, and does not
move back to the REAL
beginning of the line. I've checked and C-A is still bound to move-
beginning-of-line
and i looked at the elisp code for move-beginning-of-line and cannot
figure out
why it is not really going to the beginning, and how to influence it
to do sl.
3) similarly on the above line "cd /xyzzy;ls -R xyzzy*.x.y.*" pressing
C-K
only cuts the part from cd /xyzzy;. ie. it does not cut to the end of
the line
like it did for the past 20 years. kill-line seems to still be bound
to kill-line
and in every other mode kill-line really kills the rest of the line.
Can someone please give me some clues about what is going wrong?
Maybe it is some minor mode i need to disable???
many thanks
-jim
next reply other threads:[~2008-03-13 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 20:44 jimka [this message]
2008-03-15 2:41 ` emacs shell cursor movement is broken in 22.1 wainstead
2008-03-15 15:01 ` jimka
2008-03-26 20:43 ` wainstead
2008-03-26 20:45 ` wainstead
2008-03-16 0:42 ` Jason Rumney
2008-03-16 15:31 ` jimka
2008-03-16 15:49 ` Peter Dyballa
[not found] ` <mailman.8981.1205682606.18990.help-gnu-emacs@gnu.org>
2008-03-16 16:03 ` jimka
2008-03-16 16:59 ` Drew Adams
[not found] ` <mailman.8984.1205686774.18990.help-gnu-emacs@gnu.org>
2008-03-16 17:51 ` jimka
2008-03-16 19:16 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3c0dda17-2476-4d2b-b1f2-c101b4a0f576@s13g2000prd.googlegroups.com \
--to=jimka@rdrop.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).