package wanted: browse kill-ring, but works like undo-tree

package wanted: browse kill-ring, but works like undo-tree

[Steven Degutis]

[-- Attachment #1: Type: text/plain, Size: 1045 bytes --]

I recently tried `browse-kill-ring` (on melpa) and in theory it's really
cool. But the way it works with window-configurations and such ends up
ruining my windows. Plus the way you exit out of it isn't idiomatic for an
emacs package.

I brought these up to the author but he seems uninterested in making these
fixes. Would anyone else be willing to make such a package?

Basically, when you do `M-x browse-kill-ring` (or however you'd bind it),
it would open a new window with the contents of the kill ring in rows,
separated by some kind of line. You could then move up and down between
them with 'n' and 'p', and as you do so, it would update your original
buffer live, yanking the text right into your buffer as if you pasted it.
Each time you move across the kill ring "list", it would replace in your
buffer the last snippet with the current one you're on. When you find the
one you want, you'd just do 'q' to close the window. Or you could "cancel"
the whole operation by some other key (not sure which one makes the most
sense).

-Steven

[-- Attachment #2: Type: text/html, Size: 1235 bytes --]

RE: package wanted: browse kill-ring, but works like undo-tree

[Drew Adams]

(Please send mail to this mailing list as plain text, not HTML.)

> I recently tried `browse-kill-ring` (on melpa) and in theory
> it's really cool. But the way it works with window-configurations
> and such ends up ruining my windows. Plus the way you exit out of
> it isn't idiomatic for an emacs package. 
>
> I brought these up to the author but he seems uninterested in
> making these fixes. Would anyone else be willing to make such
> a package?
>
> Basically, when you do `M-x browse-kill-ring` (or however
> you'd bind it), it would open a new window with the contents
> of the kill ring in rows, separated by some kind of line.
> You could then move up and down between them with 'n' and 'p',
> and as you do so, it would update your original buffer live,
> yanking the text right into your buffer as if you pasted it.
> Each time you move across the kill ring "list", it would
> replace in your buffer the last snippet with the current one
> you're on. When you find the one you want, you'd just do 'q'
> to close the window. Or you could "cancel" the whole
> operation by some other key (not sure which one makes the
> most sense).

No idea whether some of the extensions and alternatives covered here might help
with what you don't like about browse-kill-ring, but just in case:

http://www.emacswiki.org/BrowseKillRing

Re: package wanted: browse kill-ring, but works like undo-tree

[Le Wang]

[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]

I personally am not interested in reimplementing something helm already
does very well.  You also get the ability to filter the kill-ring for free.

But oh noes helm is so big, hehehe.  Okay, keep piecing together all the
little functionality that helm gives you by loading these rando little
libraries that may or may not be maintained any more.

Look at helm's issues list.  Thierry is a very active and responsive
maintainer.  You can't beat that.


On Tue, Apr 23, 2013 at 12:10 AM, Steven Degutis <sbdegutis@gmail.com>wrote:

> I recently tried `browse-kill-ring` (on melpa) and in theory it's really
> cool. But the way it works with window-configurations and such ends up
> ruining my windows. Plus the way you exit out of it isn't idiomatic for an
> emacs package.
>
> I brought these up to the author but he seems uninterested in making these
> fixes. Would anyone else be willing to make such a package?
>
> Basically, when you do `M-x browse-kill-ring` (or however you'd bind it),
> it would open a new window with the contents of the kill ring in rows,
> separated by some kind of line. You could then move up and down between
> them with 'n' and 'p', and as you do so, it would update your original
> buffer live, yanking the text right into your buffer as if you pasted it.
> Each time you move across the kill ring "list", it would replace in your
> buffer the last snippet with the current one you're on. When you find the
> one you want, you'd just do 'q' to close the window. Or you could "cancel"
> the whole operation by some other key (not sure which one makes the most
> sense).
>
> -Steven
>



-- 
Le

[-- Attachment #2: Type: text/html, Size: 2227 bytes --]

Re: package wanted: browse kill-ring, but works like undo-tree

[Steven Degutis]

[-- Attachment #1: Type: text/plain, Size: 1565 bytes --]

Sorry about that, didn't realize it was HTML.

Thanks for the link, I'll check it out.

-Steven


On Mon, Apr 22, 2013 at 11:23 AM, Drew Adams <drew.adams@oracle.com> wrote:

> (Please send mail to this mailing list as plain text, not HTML.)
>
> > I recently tried `browse-kill-ring` (on melpa) and in theory
> > it's really cool. But the way it works with window-configurations
> > and such ends up ruining my windows. Plus the way you exit out of
> > it isn't idiomatic for an emacs package.
> >
> > I brought these up to the author but he seems uninterested in
> > making these fixes. Would anyone else be willing to make such
> > a package?
> >
> > Basically, when you do `M-x browse-kill-ring` (or however
> > you'd bind it), it would open a new window with the contents
> > of the kill ring in rows, separated by some kind of line.
> > You could then move up and down between them with 'n' and 'p',
> > and as you do so, it would update your original buffer live,
> > yanking the text right into your buffer as if you pasted it.
> > Each time you move across the kill ring "list", it would
> > replace in your buffer the last snippet with the current one
> > you're on. When you find the one you want, you'd just do 'q'
> > to close the window. Or you could "cancel" the whole
> > operation by some other key (not sure which one makes the
> > most sense).
>
> No idea whether some of the extensions and alternatives covered here might
> help
> with what you don't like about browse-kill-ring, but just in case:
>
> http://www.emacswiki.org/BrowseKillRing
>
>

[-- Attachment #2: Type: text/html, Size: 2255 bytes --]

Re: package wanted: browse kill-ring, but works like undo-tree

[Steven Degutis]

[-- Attachment #1: Type: text/plain, Size: 2029 bytes --]

Thanks for the suggestion. I was using helm for a few months and I just
couldn't get used to it. I made ido-vertical-mode and just switched back to
ido and it's much much nicer IMPO. I'm quite terrified of ever using helm
again, so unfortunately I can't use this solution.

-Steven


On Mon, Apr 22, 2013 at 11:31 AM, Le Wang <l26wang@gmail.com> wrote:

> I personally am not interested in reimplementing something helm already
> does very well.  You also get the ability to filter the kill-ring for free.
>
> But oh noes helm is so big, hehehe.  Okay, keep piecing together all the
> little functionality that helm gives you by loading these rando little
> libraries that may or may not be maintained any more.
>
> Look at helm's issues list.  Thierry is a very active and responsive
> maintainer.  You can't beat that.
>
>
> On Tue, Apr 23, 2013 at 12:10 AM, Steven Degutis <sbdegutis@gmail.com>wrote:
>
>> I recently tried `browse-kill-ring` (on melpa) and in theory it's really
>> cool. But the way it works with window-configurations and such ends up
>> ruining my windows. Plus the way you exit out of it isn't idiomatic for an
>> emacs package.
>>
>> I brought these up to the author but he seems uninterested in making
>> these fixes. Would anyone else be willing to make such a package?
>>
>> Basically, when you do `M-x browse-kill-ring` (or however you'd bind it),
>> it would open a new window with the contents of the kill ring in rows,
>> separated by some kind of line. You could then move up and down between
>> them with 'n' and 'p', and as you do so, it would update your original
>> buffer live, yanking the text right into your buffer as if you pasted it.
>> Each time you move across the kill ring "list", it would replace in your
>> buffer the last snippet with the current one you're on. When you find the
>> one you want, you'd just do 'q' to close the window. Or you could "cancel"
>> the whole operation by some other key (not sure which one makes the most
>> sense).
>>
>> -Steven
>>
>
>
>
> --
> Le
>

[-- Attachment #2: Type: text/html, Size: 3003 bytes --]

Re: package wanted: browse kill-ring, but works like undo-tree

[Le Wang]

[-- Attachment #1: Type: text/plain, Size: 543 bytes --]

On Tue, Apr 23, 2013 at 12:45 AM, Steven Degutis <sbdegutis@gmail.com>wrote:

> Thanks for the suggestion. I was using helm for a few months and I just
> couldn't get used to it.
>

This is vague and not really helpful.  Have you filed issues to try and fix
the parts you "couldn't get used to"?  I'd like to think we can help you
get over the hump.  Helm has lots of configuration options and the defaults
aren't all that newbie friendly IMO.  But they can't get fixed unless
people bring them up (I've overridden lots of defaults).


-- 
Le

[-- Attachment #2: Type: text/html, Size: 946 bytes --]