Looking for an App for clipboard management...

[Brian Chabot]

Of the recent suggestions:

>It's called text files and emacs :)
>
I need it for use with a web browser.  And I'm a vi devotee.  emacs is
the anti-vi. (!vi?)

Plus teext files is where I am right now.  It's where I'm trying to get
*away* from.

>The equiv. in vi is :rfoo.txt.
>

Well, at least it's vi.  But I don't need it for a text editor.  I need
it for adding text to partially filled out textareas in HTML forms.

So... Those plugins where you get a dropdown of things to put in the
form?  Yeah... They don't work if they replace everything.

>Seriously, why not just have a bunch of text file boiler plates that
>you can quickly include into whatever and be done with it?  Why does
>it need to be something that you have to "point'n'click" at?
>
I'd actual,ly be fine with something that I could use a keyboard
shortcut to cycle through various clipboards if it could be configured
NOT to be a "history" clipboard... and a visual cue of which one is
loaded in the buffer would be nice... kind of like a windows list when
you alt-tab in most GUI's.

>Even if you're talking about a small help desk environment, it's
>probably easier and faster to train a small staff that "all the
>templates are <here>" and to just include them than it is to find one
>app that everyone will use and like.
>

Uhh... That staff is me.  And the text files are there.  I'm getting
sick of switching to a text editor.  There is no import function in
filling out forms, so it:

1. Find the right response file. (Easy enough)
2. Open it to a text editor (or leave it open)
3. CTRL-a CTRL-c
4. ALT-TAB
5. CTRL-v

I'd like to do something with a smaller window, where clicking on a
title of a file copies the contents to the clipboard buffer. 
*click->click->ctrl-v* Done.

So far, GCM is the closest... but the dang thing is so unstable it's
amazing.  Save your changes and you got a 60% change of it crashing and
spewing a core dump.  Open a config with one error and it dumps core. 
And the XML config uses a byte counter to verify the size of the
contents... making editing by hand a PITA.

Brian