emacs shell cursor movement is broken in 22.1

emacs shell cursor movement is broken in 22.1

[jimka]

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

Re: emacs shell cursor movement is broken in 22.1

[wainstead]

On Mar 13, 4:44 pm, jimka <ji...@rdrop.com> wrote:
> 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

Hi Jim,

Like you I've used shell mode for years. The problems you see started
a few years ago, showing up in the OS X build; now they are in the
Linux build as well.

This week I'm in Japan and am meeting with one of the maintainers. I
am hoping to demo these bugs to him and get his feedback. It's high
time these were addressed.

~swain

Re: emacs shell cursor movement is broken in 22.1

[jimka]

great!  that is great news


>
> Hi Jim,
>
> Like you I've used shell mode for years. The problems you see started
> a few years ago, showing up in the OS X build; now they are in the
> Linux build as well.
>
> This week I'm in Japan and am meeting with one of the maintainers. I
> am hoping to demo these bugs to him and get his feedback. It's high
> time these were addressed.
>
> ~swain

Re: emacs shell cursor movement is broken in 22.1

[Jason Rumney]

On 13 Mar, 20:44, jimka <ji...@rdrop.com> wrote:

> 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.

I have no idea why that change was made or whether there was a good
reason for it, but is there a reason why you use !!:p rather than M-p
to get the previous command? The latter puts the command at the
prompt, where commands are expected to be input.

Re: emacs shell cursor movement is broken in 22.1

[jimka]

> I have no idea why that change was made or whether there was a good
> reason for it, but is there a reason why you use !!:p rather than M-p
> to get the previous command? The latter puts the command at the
> prompt, where commands are expected to be input.

the !!:p example is just a simple example that is easy to explain
in the posting. There is nothing really special about !!:p.

Another example would be if i want to find the last command that
contained a certain word.
If i want to see the history, i type "history",  If i want to see all
the history
which contained /tmp, i use "history | grep /tmp", and i expect emacs
to be
able to edit that result with its normal full screen editing.  During
that
editing C-e and C-a should work as they do in any other full screen
editing mode.


About M-p, I think the reason people want the M-p and arrow keys to
display
history, is because shells don't normally enable full screen editing.
One reason i started using the emacs shell in the 80s was because it
did just that.
I don't see M-p and C-up-arrow as very useful substitutes for full-
screen
capability.  (i admit that i'm in the minority. most people do not
want a powerful
shell editing facility, but instead a very klunky one.)

Re: emacs shell cursor movement is broken in 22.1

[Peter Dyballa]

Am 16.03.2008 um 16:31 schrieb jimka:

> If i want to see the history, i type "history",  If i want to see all
> the history
> which contained /tmp, i use "history | grep /tmp",

Why do you use shell mechanisms? GNU Emacs has more efficient ways to  
retrieve an elderly shell command ... (comint-previous-matching-input  
or M-r for example)

--
Greetings

   Pete

We are usually convinced more easily by reasons we have found  
ourselves than by those which have occurred to others.
				– Blaise Pascal

Re: emacs shell cursor movement is broken in 22.1

[jimka]

On Mar 16, 4:49 pm, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:

>
> Why do you useshellmechanisms? GNU Emacs has more efficient ways to
> retrieve an elderlyshellcommand ... (comint-previous-matching-input
> or M-r for example)
>
>
>    Pete
>



yes it is always the case with emacs that there is a more
efficient way in terms of fewer keystokes.  but i think the
question of how to most efficiently do a job-X in emacs
is an independent question from why did the full-screen-editing
features of the emacs shell regress.  Don't you agree?

By the way i do often use C-r to find the previous comand which
matches some pattern and either press enter twice to
execute it again, or press enter to leave the search mode,
then edit the command and enter it again.  C-r has a great advantage
over M-r because it lets me see the context in which something
happened
and also lets me match things that were not shell commands
at all but might look like shell commands.

-jim

RE: emacs shell cursor movement is broken in 22.1

[Drew Adams]

> Another example would be if i want to find the last command that
> contained a certain word.

I haven't followed this thread, but you might be interested in trying
Icicles' comint (shell) mode enhancements. They let you easily complete
against past shell inputs in various ways, to reuse them.

http://www.emacswiki.org/cgi-bin/wiki/Icicles_-_Other_Search_Commands#toc7

Re: emacs shell cursor movement is broken in 22.1

[jimka]

On Mar 16, 5:59 pm, "Drew Adams" <drew.ad...@oracle.com> wrote:
> > Another example would be if i want to find the last command that
> > contained a certain word.
>
> I haven't followed this thread, but you might be interested in trying
> Icicles' comint (shell) mode enhancements. They let you easily complete
> against pastshellinputs in various ways, to reuse them.
>
> http://www.emacswiki.org/cgi-bin/wiki/Icicles_-_Other_Search_Commands...

yes there are lots and lots of interesting modes.  But what i want
is to  search in the buffer, with normal buffer search commands such
as
C-r and C-s, edit the command like a normal buffer, inserting,
deleting and overwriting, then
press ENTER to re-execute the command at the next shell prompt.

fancy completion modes are well and good, but they should not prevent
basic navigation and editing.

-jim

RE: emacs shell cursor movement is broken in 22.1

[Drew Adams]

> > > Another example would be if i want to find the last command that
> > > contained a certain word.
> >
> > I haven't followed this thread, but you might be interested 
> > in trying Icicles' comint (shell) mode enhancements. They let
> > you easily complete against pastshellinputs in various ways,
> > to reuse them.
> >
> http://www.emacswiki.org/cgi-bin/wiki/Icicles_-_Other_Search_C
> ommands...
> 
> yes there are lots and lots of interesting modes.  But what i want
> is to search in the buffer, with normal buffer search commands such
> as C-r and C-s, edit the command like a normal buffer, inserting,
> deleting and overwriting, then
> press ENTER to re-execute the command at the next shell prompt.
> 
> fancy completion modes are well and good, but they should not prevent
> basic navigation and editing.

Nothing in Icicles prevents basic navigation and editing.

It sounds like you can already do just what you want, based on your
description, above. What prevents you now from searching with C-r, editing,
and re-executing?

But as I said, I didn't follow the thread (sorry), so it's not clear to me
what you might want beyond what you say above. That's my fault. Just trying
to help. 

FWIW, 'icicle-comint-search' does what you describe above: it searches the
buffer. (But it doesn't use "normal buffer search commands such as C-r and
C-s - it gives you better search features.) When you choose the past command
that you want, you can certainly edit it and then hit ENTER to re-execute.

It's OK if I don't get it - I don't really need to understand your problem
better. If the info I gave helps, great. If not, ignore it. HTH.

Re: emacs shell cursor movement is broken in 22.1

[wainstead]

On Mar 15, 11:01 am, jimka <ji...@rdrop.com> wrote:
> great! that is great news

Hey jimka!

Well, I met with Miles Bader who, it turns out, wrote major portions
of shell-mode. I didn't know this beforehand so it was a pleasant
surprise.

I demo'd the problems for him; he had a bit of trouble though because
of some of the oddities of running Emacs on OS X; he first thought it
might have something to do with the text.

He thinks it's definitely a Lisp problem, not something wonky with the
terminal or anything. (This didn't surprise me much). shell-mode
inherits stuff from comint-mode, and he thinks the problem lies in
somebody doing a fix/kludge/improvement somewhere else which has
introduced this bug to shell-mode.

I'm going to point him to this thread and see if I can nudge him to
diagnose the bug... it seems like about thirty minutes of poking
around and he'll know what's wrong and how to fix it.

~swain

Re: emacs shell cursor movement is broken in 22.1

[wainstead]

On Mar 26, 4:43 pm, wainst...@gmail.com wrote:

> He thinks it's definitely a Lisp problem, not something wonky with the
> terminal or anything.

Oh, I just remembered he mentioned something about text having "sticky
properties" that adjoining text picks up, or does not. This was way
over my head, but it kinda makes sense given the behavior I see.

~swain