Re: emulate readline

Re: emulate readline

[despen]

fork <forkandwait@gmail.com> writes:

> Is there a way to get the behavior of this (super cool) 
> readline behavior in the minibuffer?  
>
> In my .inputrc I have this:
>
> "\e[A": history-search-backward
> "\e[B": history-search-forward
> "\eOA": history-search-backward
> "\eOB": history-search-forward
>
> So in bash I can type "ps", hit the up-arrow, and get the most recent
>  command that started with these two letters (e.g. "psql -D foobar").  
> The next time I hit up-arrow, I get "psql -U fork -D forksdb", etc.
> I would like to type M-x in emacs, then cycle through previous
>  commands like this.

M-p

Re: emulate readline

[fork]

 <despen <at> verizon.net> writes:


> 
> M-p

That doesn't match -- if I type "eva" I should be able to get "eval-region"
(since that is in my history), but it gives me my latest command "pa" instead.

Re: emulate readline

[Kevin Rodgers]

On 4/6/11 1:01 PM, fork wrote:
>   <despen<at>  verizon.net>  writes:
>>
>> M-p
>
> That doesn't match -- if I type "eva" I should be able to get "eval-region"
> (since that is in my history), but it gives me my latest command "pa" instead.

M-r REGEXP RET e.g. M-r eva RET

The missing functionality is to get M-r (previous-matching-history-element) to
use the current minibuffer contents as REGEXP, possibly anchored to only match
commands that begin with that.

Here's what I came up with:

;; Like previous-matching-history-element, but use the current minibuffer
;; contents as REGEXP:
(defun previous-matching-history-element-default ()
   (interactive)
   (previous-matching-history-element (concat "\\`" (regexp-quote
						    (minibuffer-contents)))
				     (prefix-numeric-value current-prefix-arg)))

;; Bind to M-R to preserve M-r:
(define-key minibuffer-local-map "\M-R" 'previous-matching-history-element-default)

For completeness, define next-matching-history-element-default to call
next-matching-history-element, and bind it to M-S.

-- 
Kevin Rodgers
Denver, Colorado, USA

Re: emulate readline

[Richard Riley]

despen@verizon.net writes:

> fork <forkandwait@gmail.com> writes:
>
>> Is there a way to get the behavior of this (super cool) 
>> readline behavior in the minibuffer?  
>>
>> In my .inputrc I have this:
>>
>> "\e[A": history-search-backward
>> "\e[B": history-search-forward
>> "\eOA": history-search-backward
>> "\eOB": history-search-forward
>>
>> So in bash I can type "ps", hit the up-arrow, and get the most recent
>>  command that started with these two letters (e.g. "psql -D foobar").  
>> The next time I hit up-arrow, I get "psql -U fork -D forksdb", etc.
>> I would like to type M-x in emacs, then cycle through previous
>>  commands like this.
>
> M-p

How do you make M-p work like bash filtered history (C-r, C-n from bash
line) as requested in the op?

emulate readline

[fork]

Is there a way to get the behavior of this (super cool) 
readline behavior in the minibuffer?  

In my .inputrc I have this:

"\e[A": history-search-backward
"\e[B": history-search-forward
"\eOA": history-search-backward
"\eOB": history-search-forward

So in bash I can type "ps", hit the up-arrow, and get the most recent
 command that started with these two letters (e.g. "psql -D foobar").  
The next time I hit up-arrow, I get "psql -U fork -D forksdb", etc.

I would like to type M-x in emacs, then cycle through previous
 commands like this.

Any help is appreciated!  Thanks!

Re: emulate readline

[Eli Zaretskii]

> From: fork <forkandwait@gmail.com>
> Date: Wed, 6 Apr 2011 17:04:26 +0000 (UTC)
> 
> Is there a way to get the behavior of this (super cool) 
> readline behavior in the minibuffer?  
> 
> In my .inputrc I have this:
> 
> "\e[A": history-search-backward
> "\e[B": history-search-forward
> "\eOA": history-search-backward
> "\eOB": history-search-forward
> 
> So in bash I can type "ps", hit the up-arrow, and get the most recent
>  command that started with these two letters (e.g. "psql -D foobar").  
> The next time I hit up-arrow, I get "psql -U fork -D forksdb", etc.
> 
> I would like to type M-x in emacs, then cycle through previous
>  commands like this.

Your wish has been granted!  In Emacs, this is invoked with M-s and
M-r.  That is

   M-x M-r psql RET

will show you a past command that matches "psql".

Re: emulate readline

[fork]

Eli Zaretskii <eliz <at> gnu.org> writes:

> Your wish has been granted!  In Emacs, this is invoked with M-s and
> M-r.  That is
> 
>    M-x M-r psql RET
> 
> will show you a past command that matches "psql".

Thanks! That is close, and much better than nothing, but not exactly the ease of
the up-arrow key that cycles through alternatives.  

Does anybody have any get-started elisp for this?

Re: emulate readline

[despen]

fork <forkandwait@gmail.com> writes:

> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>> Your wish has been granted!  In Emacs, this is invoked with M-s and
>> M-r.  That is
>> 
>>    M-x M-r psql RET
>> 
>> will show you a past command that matches "psql".
>
> Thanks! That is close, and much better than nothing, but not exactly the ease of
> the up-arrow key that cycles through alternatives.  
>
> Does anybody have any get-started elisp for this?

I didn't get your question the first time.

By default the up arrow just goes to the previous element.

This is close but not right:

(define-key minibuffer-local-map [(up)] 'previous-matching-history-element)

but it might lead to a solution.

I think you want the up arrow when not on the first position to do a
match.

Re: emulate readline

[fork]

 <despen <at> verizon.net> writes:

> By default the up arrow just goes to the previous element.

Yes.

> This is close but not right:
> 
> (define-key minibuffer-local-map [(up)] 'previous-matching-history-element)

Cool!

Is there a way to pass the text currently in the minibuffer to a function (which
would be bound to "up" like the above)?
 
> 
> but it might lead to a solution.
> 
> I think you want the up arrow when not on the first position to do a
> match.

Yes!

> 

Re: emulate readline

[despen]

fork <forkandwait@gmail.com> writes:

>  <despen <at> verizon.net> writes:
>
>> By default the up arrow just goes to the previous element.
>
> Yes.
>
>> This is close but not right:
>> 
>> (define-key minibuffer-local-map [(up)] 'previous-matching-history-element)
>
> Cool!
>
> Is there a way to pass the text currently in the minibuffer to a function (which
> would be bound to "up" like the above)?

Well, I just tried what seemed "intuitive" and it seems to work.

I typed:

M-x

then

m C-r

That gave me a prompt for isearch backwards
with the "m" already in place.

I hit C-r again and it pulled out the command
I was looking for "man".

Then I hit return and got the completed M-x prompt
where I could then run the command.

Try it.

I think there's an option about nesting commands in the mini-buffer
that you may have to enable.  I have this:

(setq minibuffer-max-depth nil)

Re: emulate readline

[fork]

 <despen <at> verizon.net> writes:

> 
> Well, I just tried what seemed "intuitive" and it seems to work.
> 
> I typed:
> 
> M-x
> 
> then
> 
> m C-r

<SNIP>  This works as designed, but the design isn't what I want.  I want to be
able to type the first few letters and hit an arrow key and see the options that
match the first few letters. 

The wiki has a recipe that seems to be working (thanks to Le Wang):

 http://www.emacswiki.org/emacs/MinibufferHistory

Re: emulate readline

[Peter Dyballa]

Am 06.04.2011 um 19:04 schrieb fork:

> I would like to type M-x in emacs, then cycle through previous
> commands like this.


Exactly this works with M-p! (And M-n in the other direction.) The  
functions term or terminal-emulator might give you something closer to  
an xterm. (For me shell is OK.)

--
Greetings

   Pete

Competition is the great erode of profits.

Re: emulate readline

[fork]

Peter Dyballa <Peter_Dyballa <at> Web.DE> writes:


> Exactly this works with M-p! (And M-n in the other direction.) The  
> functions term or terminal-emulator might give you something closer to  
> an xterm. (For me shell is OK.)

Hm...

Is there a setting for this?  I am running emacs OUTSIDE of any shell, so it
probably doesn't read my inputrc.

I don't want a terminal inside my emacs, I want to go search-backward-history
insdid my M-x (and when I open files too).

Re: emulate readline

[Peter Dyballa]

Am 06.04.2011 um 21:23 schrieb fork:

> I don't want a terminal inside my emacs, I want to go search- 
> backward-history

C-x ESC ESC invokes the function repeat-complex-command. This works  
outside of a terminal in GNU Emacs. It does not rewind a shell command  
once invoked in a *shell* buffer or something similar.

> insdid my M-x (and when I open files too).


What is your "M-x"? Has it a documented name one can find and look up  
in the GNU Emacs documentation?  (Then use it and not any slang one or  
two people might be using when together.) And what are your  
parentheses standing for?

--
Greetings

   Pete

The light at the end of the tunnel has been turned off due to budget  
cuts.

Re: emulate readline

[fork]

Peter Dyballa <Peter_Dyballa <at> Web.DE> writes:

> 
> C-x ESC ESC invokes the function repeat-complex-command. This works  
> outside of a terminal in GNU Emacs. It does not rewind a shell command  
> once invoked in a *shell* buffer or something similar.

Thats cool, but not what I want.

> > insdid my M-x (and when I open files too).
> 
> What is your "M-x"? 

I want to be able to replay all the commands I have typed in, subsetted by their
initial string which I have so far typed into the minibuffer, with each press of
my up-arrow key.  I don't know how to be any more specific or clearer.  This
behavior is possible at the bash shell prompt when you configure inputrc
correctly, but I want it within emacs when I am cycling through arbitrary
commands after typing M-x.

If you haven't done this in a shell, you probably dont have any idea what I am
talking about, but I am not sure how to be any more explicit -- I give an
example in my first email.

>Has it a documented name one can find and look up  
> in the GNU Emacs documentation?  (Then use it and not any slang one or  
> two people might be using when together.) 

If I knew, I would happily, but I don't.  

> And what are your  
> parentheses standing for?

They are just parantheses, not a command (like this).

Re: emulate readline

[Peter Dyballa]

Am 06.04.2011 um 21:44 schrieb fork:

> I want to be able to replay all the commands I have typed in,  
> subsetted by their
> initial string which I have so far typed into the minibuffer, with  
> each press of
> my up-arrow key.

So start with C-x ESC ESC and then arrow up! Arrow up. Arrow up. ...

>
> If you haven't done this in a shell, you probably dont have any idea  
> what I am
> talking about


Yes, I'm no bash fan, I don't have the time to browse in my past  
commands for an eternity. Or half.


Since you've got so much time to browse in your command history,  
couldn't you find some to browse the GNU Emacs documentation? The Help  
menu offers some entry points you could browse through. You might some  
concept that might come close to your wish.

--
Greetings

   Pete

"A TRUE Klingon warrior does not comment his code."

Re: emulate readline

[fork]

Peter Dyballa <Peter_Dyballa <at> Web.DE> writes:

> 
> <SNIP>
> Am 06.04.2011 um 21:44 schrieb fork:
> 
> > I want to be able to replay all the commands I have typed in,  
> > subsetted by their
> > initial string which I have so far typed into the minibuffer, with  
> > each press of
> > my up-arrow key.
> 
> So start with C-x ESC ESC and then arrow up! Arrow up. Arrow up. ...
> 
> >
> > If you haven't done this in a shell, you probably dont have any idea  
> > what I am
> > talking about
> 
> Yes, I'm no bash fan, I don't have the time to browse in my past  
> commands for an eternity. Or half.
> 
> Since you've got so much time to browse in your command history,  
> couldn't you find some to browse the GNU Emacs documentation? The Help  
> menu offers some entry points you could browse through. You might some  
> concept that might come close to your wish.

Thanks for the condescension and lack of understanding my problem, I will
refrain from replying to anymore of your snide and unhelpful emails. Just to
clarify:  I understand my problem just fine, it is a solution to the eternity of
up-arrows you mention above, and I would like to find an implementation in
emacs.  And I have wasted more time with you than I have already, so I will
refrain from randomly browsing the documentation as you so helpfully suggest.

RE: emulate readline

[Drew Adams]

> I want to be able to replay all the commands I have typed in, 
> subsetted by their initial string which I have so far typed

Others have given you some info about what comes closest in vanilla Emacs to
what you requested.

In Icicles:

1. `M-h' matches what you've typed so far in the minibuffer against the history
elements.  You can complete to them or cycle among them.

2. `M-pause' filters the current set of matching candidates to ones you've used
previously. Again, you can then complete against or cycle among those.

3. You can use `M-o' at any time (not just during completion) to insert an entry
from the current history into the minibuffer.  Again, you can complete against
or cycle among the candidates.

The difference between #1 and #2 is that #2 narrows the current set of
candidates and #1 matches directly against all history elements.

In all cases, for completion you can match using a prefix, a substring, or a
regexp - au choix.  You can use the up/down arrows to cycle among the current
matches.

There are additional history enhancements.  All are described here:

http://www.emacswiki.org/emacs/Icicles_-_History_Enhancements

Re: emulate readline

[fork]

Drew Adams <drew.adams <at> oracle.com> writes:


> 
> In Icicles:

... That looks promising -- thanks for the tip!

Re: emulate readline

[Le Wang]

On Thu, Apr 7, 2011 at 1:04 AM, fork <forkandwait@gmail.com> wrote:
>
> Is there a way to get the behavior of this (super cool)
> readline behavior in the minibuffer?
>
> In my .inputrc I have this:
>
> "\e[A": history-search-backward
> "\e[B": history-search-forward
> "\eOA": history-search-backward
> "\eOB": history-search-forward
>
> So in bash I can type "ps", hit the up-arrow, and get the most recent
>  command that started with these two letters (e.g. "psql -D foobar").
> The next time I hit up-arrow, I get "psql -U fork -D forksdb", etc.
>
> I would like to type M-x in emacs, then cycle through previous
>  commands like this.
>
> Any help is appreciated!  Thanks!

The commands you seek are (previous|next)-complete-history-element,
which are not bound to keys by default.

You also have to consider that not all mini-buffer inputs are using
the same local key-map.  I have the following code in my
initialization to bind M-p and M-n to these functions:

(mapc (lambda (map)
        (define-key map [(meta p)] 'previous-complete-history-element)
        (define-key map [(meta n)] 'next-complete-history-element))
      (list minibuffer-local-completion-map
	    minibuffer-local-isearch-map
	    minibuffer-local-map
	    minibuffer-local-must-match-map
	    minibuffer-local-ns-map))

Also see the wiki page: http://www.emacswiki.org/emacs/MinibufferHistory

--
Le

Re: emulate readline

[fork]

Le Wang <l26wang <at> gmail.com> writes:

> > Any help is appreciated!  Thanks!
> 
> The commands you seek are (previous|next)-complete-history-element,
> which are not bound to keys by default.

Yay ! Thanks so much!
 
> You also have to consider that not all mini-buffer inputs are using
> the same local key-map.  I have the following code in my
> initialization to bind M-p and M-n to these functions:
> 
> (mapc (lambda (map)
>         (define-key map [(meta p)] 'previous-complete-history-element)
>         (define-key map [(meta n)] 'next-complete-history-element))
>       (list minibuffer-local-completion-map
> 	    minibuffer-local-isearch-map
> 	    minibuffer-local-map
> 	    minibuffer-local-must-match-map
> 	    minibuffer-local-ns-map))
> 
> Also see the wiki page: http://www.emacswiki.org/emacs/MinibufferHistory

I went with the wiki page instructions to bind directly -- if I get weird
behavior, I will use your code.

Thanks so much!  This was a gaping hole in the perfect emacs experience for me ;)

Fork

Re: emulate readline

[Richard Riley]

Le Wang <l26wang@gmail.com> writes:

> On Thu, Apr 7, 2011 at 1:04 AM, fork <forkandwait@gmail.com> wrote:
>>
>> Is there a way to get the behavior of this (super cool)
>> readline behavior in the minibuffer?
>>
>> In my .inputrc I have this:
>>
>> "\e[A": history-search-backward
>> "\e[B": history-search-forward
>> "\eOA": history-search-backward
>> "\eOB": history-search-forward
>>
>> So in bash I can type "ps", hit the up-arrow, and get the most recent
>>  command that started with these two letters (e.g. "psql -D foobar").
>> The next time I hit up-arrow, I get "psql -U fork -D forksdb", etc.
>>
>> I would like to type M-x in emacs, then cycle through previous
>>  commands like this.
>>
>> Any help is appreciated!  Thanks!
>
> The commands you seek are (previous|next)-complete-history-element,
> which are not bound to keys by default.
>
> You also have to consider that not all mini-buffer inputs are using
> the same local key-map.  I have the following code in my
> initialization to bind M-p and M-n to these functions:
>
> (mapc (lambda (map)
>         (define-key map [(meta p)] 'previous-complete-history-element)
>         (define-key map [(meta n)] 'next-complete-history-element))
>       (list minibuffer-local-completion-map
> 	    minibuffer-local-isearch-map
> 	    minibuffer-local-map
> 	    minibuffer-local-must-match-map
> 	    minibuffer-local-ns-map))
>
> Also see the wiki page: http://www.emacswiki.org/emacs/MinibufferHistory
>

Nice, but this doesnt emulate the bash history fetch which will include all
histories containing the seed not just candidates beginning with the
seed.