RE: pasting many times

RE: pasting many times

[Bourgneuf Francois]

 
I have downloaded browse-kill-ring (http://www.todesschaf.org/projects/bkr.html).
It allows you to browse all the kills you did and choose the one you want to yank.

After you installed it, you'll have to add the following lines in your .emacs :

(require 'browse-kill-ring)
(browse-kill-ring-default-keybindings)

Bour9



-----Message d'origine-----
De : help-gnu-emacs-bounces+francois.bourgneuf=groupe-mma.fr@gnu.org [mailto:help-gnu-emacs-bounces+francois.bourgneuf=groupe-mma.fr@gnu.org] De la part de Drew Adams
Envoyé : mardi 24 octobre 2006 22:22
À : help-gnu-emacs@gnu.org
Objet : RE: pasting many times

    > FWIW, I happen to agree with Mathias. If I want an earlier
    > kill, I use C-y M-y.

    FWIW, I agree with Drew C-y M-yyy... is the way to go for me since I
    usually don't memorise the kill-ring by heart.

    And when we are at it.  I do not understand why M-y depends on C-y at
    all, lets just take the second entry of kill-ring by default and third
    and fourth and so on?

    Now we are already 4 forgetful people, could this be made into an
    official feature request (for after the release ;-)?

There are no official feature requests. Bring it up at emacs-devel, to
possibly  discover good counter arguments and see what others think.



_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs

Re: pasting many times

[Eli Zaretskii]

> Date: Wed, 25 Oct 2006 09:45:24 +0200
> From: "Bourgneuf Francois" <francois.bourgneuf@groupe-mma.fr>
>  
> I have downloaded browse-kill-ring (http://www.todesschaf.org/projects/bkr.html).
> It allows you to browse all the kills you did and choose the one you want to yank.

I presume you know about the "Edit->Select and Paste" menu item that's
available from the standard Emacs menu bar?  It allows you to do the
same.

the second most recent key

[vb]

Is there a way to know what was the key pressed immediately before the last 
key pressed.

Say there is a macro assigned to a certain key, and the function of this 
certain key depends on the key pressed immediately before the function was 
invoked.

Is there a way to know what key that was?

TIA,
/vb

Re: the second most recent key

[Peter Dyballa]

Am 26.10.2006 um 00:41 schrieb vb:

> Is there a way to know what key that was?

M-x view-lossage RET ?

--
Greetings

   Pete

“One cannot live by television, video games, top ten CDs, and dumb  
movies alone”
       (Amiri Baraka 1999)

Re: the second most recent key

[vb]

Wow, this was quick and it sure shows what I need and then some :-)

Thank you, Peter,

cheers,
/vb


On Wednesday 25 October 2006 16:03, Peter Dyballa wrote:
> Am 26.10.2006 um 00:41 schrieb vb:
> > Is there a way to know what key that was?
>
> M-x view-lossage RET ?
>
> --
> Greetings
>
>    Pete
>
> “One cannot live by television, video games, top ten CDs, and dumb
> movies alone”
>        (Amiri Baraka 1999)

Re: the second most recent key

[Kevin Rodgers]

vb wrote:
> Is there a way to know what was the key pressed immediately before the last 
> key pressed.
> 
> Say there is a macro assigned to a certain key, and the function of this 
> certain key depends on the key pressed immediately before the function was 
> invoked.
> 
> Is there a way to know what key that was?

(let* ((recent-keys (recent-keys))
        (keys-length (length recent-keys))) ; should be 100
   (aref recent-keys (- keys-length (length (this-command-keys)) 1)))

-- 
Kevin

Re: the second most recent key

[vb]

On Thursday 26 October 2006 08:38, Kevin Rodgers wrote:
> vb wrote:
> > Is there a way to know what was the key pressed immediately before the
> > last key pressed.
> >
> > Say there is a macro assigned to a certain key, and the function of this
> > certain key depends on the key pressed immediately before the function
> > was invoked.
> >
> > Is there a way to know what key that was?
>
> (let* ((recent-keys (recent-keys))
>         (keys-length (length recent-keys))) ; should be 100
>    (aref recent-keys (- keys-length (length (this-command-keys)) 1)))

Kevin,

thank you for spending your time writing this code. Looks like this is exactly 
what's needed, even accounting for the number of keys involved in the current 
command.

Do I understand it right that Lisp allows local variable named exactly the 
same as a function (recent-keys in your example)? An interesting feature...

cheers,
/vb

Re: the second most recent key

[David Kastrup]

vb <help-gnu-emacs@vsbe.com> writes:

> On Thursday 26 October 2006 08:38, Kevin Rodgers wrote:
>> vb wrote:
>> > Is there a way to know what was the key pressed immediately before the
>> > last key pressed.
>> >
>> > Say there is a macro assigned to a certain key, and the function of this
>> > certain key depends on the key pressed immediately before the function
>> > was invoked.
>> >
>> > Is there a way to know what key that was?
>>
>> (let* ((recent-keys (recent-keys))
>>         (keys-length (length recent-keys))) ; should be 100
>>    (aref recent-keys (- keys-length (length (this-command-keys)) 1)))
>
> Kevin,
>
> thank you for spending your time writing this code. Looks like this
> is exactly what's needed, even accounting for the number of keys
> involved in the current command.
>
> Do I understand it right that Lisp allows local variable named
> exactly the same as a function (recent-keys in your example)? An
> interesting feature...

Not just local variables, but variables in general.  Lisp symbols have
a four-fold existence: they have a value, a function, a property list,
and a name.  You can access those with `symbol-value',
`symbol-function', `symbol-plist', and `symbol-name'.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum