Konsole select into primary clipboard

Fri Nov 10 19:36:48 UTC 2017

On 10 November 2017 at 13:44, Xen <list at xenhideout.nl> wrote:
>
> It's still a better system than having one archaic selection thing from the
> past that happens to live on, and then the other one from the IBM world.

CUA is pretty good. It was inspired by Apple's Human Interface
Guidelines for the Mac, but IBM formalised a PC version. There's an
excellent Wikipedia article on it:

https://en.wikipedia.org/wiki/IBM_Common_User_Access

(I can say that, because I wrote it. ;-) )

Apple moved _closer_ to CUA with Mac OS X.

GNOME uses it. KDE uses it. LXDE and Xfce use it. Windows uses it.
Almost everything does. Maybe not a complete implementation but enough
that you can work it.

But most people now only use a mouse and know almost no keyboard shortcuts.

My #1 recommendation to UI developers and testers is:

Unplug your mouse. _Now_ try to use your app. You'll probably find you
can't. Fix that and you'll find you have a much better UI for mouse
users, too.

> That just happen to coexist.
>
> With no design behind it whatsoever.

True. _Which is why it's useful and why I like it._ Because I get 2 at
once, not a fiddly selection menu or anything.

> Actually Klipper in KDE saves both :p.

A tool I used to disable or uninstall when I used KDE, because it got
in the way and annoyed me.

But whatever you prefer. I'm not saying I'm right and anyone else is
wrong, just that I like the current system.

> You really just need multiple buffers and they exist but it is just random
> chance that they do currently.

Yup. Happy accident. Works great.

> You said I need to use a compose key, I didn't know how but now I do after
> reading tutorials for some 10 minutes.

They're great!

> I didn't know it required that much setup.

Depends on desktop.

Unity/GNOME 3: install the Tweak Tool and it's a ticky-box under
Keyboard settings.

It used to be built into to both but so few people know about it,
nobody used it, so GNOME removed it -- as they do everything useful --
and Unity inherited that.

> It is still no excuse for having this dumb dead keys.

With Compose, you need no dead keys.

> Even if you don't like them, then also don't make them stupider than they
> have to be.

*Shrug* No comment.

> But the ctrl-' thing I proposed is a form of compose key.
>
> I'm not telling you to copy more than 1% of Vim.
>
> But you are falling into the "I don't like to eat oranges, so I will also
> not use the color orange" trap.

I get that a lot. I have worked for both Red Hat & SUSE. Both are
_full_ of Vi lovers, with a few Emacs lovers. Both evangelise their
editors.

Neither understand when I say I won't use anything that isn't CUA.

There's a standard editor UI -- not just menus but keyboard shortcuts,
terminology, etc. -- that _all_ GUI editors use and have used for
about 30 years now. Some console-mode/text-mode editors use it too.

I used to know about 15-12 different word processor UIs in the era of
MS-DOS. I liked and used MS Word, LocoScript, MS-DOS 5 Editor. If I
had to, I could use WordPerfect 5.1. I disliked but also worked with
and supported:
* Wordstar
* Wordstar 2000 (totally different)
* Wordstar Express/Wordstar 1512  (totally different again)
* MultiMate
* DisplayWrite
* DECwrite
* PC Write
* XyWrite
* Samna Executive
* WordPerfect 4.2 (no menus)
* Lotus Symphony
* Edlin
* VMS EDIT
... and others.

Every one had a different UI. Nothing in common. I used them all.

I hated them all to some degree, some more than others.

Then came the Mac and later Windows and it all went away. Everyone had
a File menu, an Edit menu, a View menu, etc. Everyone understood
Ctrl-O is open, Ctrl-S is save, Ctrl-P is print, Shift-Del or Ctrl-X
is cut, etc.

So I happily forgot all that proprietary nastiness and moved to the
new standard.

I am not going back for _anybody_. I don't code, I don't care about
any code-editing features. I write English and other human languages.
I don't care _how_ powerful anyone's editor is, unless it complies
with the standard UI, I'm not interested.

So unless someone does _again_ what Borland did with Sprint, 25y ago,
and rewrite Emacs to have a bog-standard UI. Files, not "buffers".
Windows and panes. All the CUA menus, commands and keystrokes, at the
console as well as in a GUI.

Then I'll look.

After the power is no use if I can't use it as a simple editor like
any other, and with vi and Emacs, I can't. So, not interested. The
mountain must come to Mohammed. ;-)

>> Then don't use one. The simplest most internationally-portable
>> keyboard is US English with a compose key.
>
>
> I didn't know. Honestly. I have been wanting to find out for a long time but
> I can't spend my entire day googling (and I'm often a bit lazy) (or too busy
> with other stuff, whatever).
>
> You gave me the pointer to look up how to do it.
>
> The energy so to speak.

Well, good! :-)

>> Then you can type anything.
>
>
> Yeah I wanted that but I couldn't, but now it doesn't do 3rd level combining
> anymore, don't know why.

That I don't know.

> But now I can compose diacritics and not be bugged by 'n thank you.

Great! You're welcome!

The thing I love about compose key sequences is that you can just
guess almost all of them.

` + letter == grave accent
' + letter == acute accent (and čarka: é, á)
" + letter == umlaut/diaresis
^ + letter == circumflex
/ + letter == line through (¢, ¥, Ł, ø)
etc. etc.
a + e == æ
o + e == œ
a + a == å
Czech style hačky are a less-than sign: ř, š, č, ť, ď
Cedilla is a comma: ç
Tilde is a tilde, obviously -- ~ + n == ñ

> But now my typing in Windows will be different unless I can do it there too
> (I hope).

https://sourceforge.net/projects/allchars/

or

https://github.com/samhocevar/wincompose

> Thanks.

You're welcome. :-)

-- 
Liam Proven • Profile: https://about.me/liamproven
Email: lproven at cix.co.uk • Google Mail/Talk/Plus: lproven at gmail.com
Twitter/Facebook/Flickr: lproven • Skype/LinkedIn/AIM/Yahoo: liamproven
UK: +44 7939-087884 • ČR/WhatsApp/Telegram/Signal: +420 702 829 053