OSDir


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Konsole select into primary clipboard


Liam Proven schreef op 10-11-2017 22:37:
> On 10 November 2017 at 21:31, Xen <list at xenhideout.nl> wrote:
>> 
>> I think a better system than a menu is when you decide the buffer at 
>> the end
>> of your action.
> 
> MS-Word does that. It drives me crazy.

Didn't know that.

>> You could hold down a key combination (e.g.  ctrl-c) and if you hold 
>> it down
>> for longer than a second a menu pops up with a choice of 1 2 3 and 4.
>> 
>> Bit hard to paste that way though.
> 
> Ew! Sounds horrid. As before -- happy for anyone to use it if they
> want, but I'd like the main OS and standard apps to use the normal way
> that everyone's used since 1984, please.

Except you haven't.

You have been using an archaic side effect that pretty much no one has 
been using, to augment a system that otherwise would be too limited.

Yes and In Windows I Just Use Notepad As Another Scratch Pad but I 
haven't found a good, or I have never found a good notepad in Linux for 
that.

So I have been rarely bugged by the lack of "scratch pad" in Windows.

In Linux, against my wishes, I use Klipper for a modicum of that, but it 
is unreliable because it is unintended and you can lose your history.


>> Vim only has ctrl-x, no "del" button.
>> 
>> This constantly risks overwriting your save buffer and makes the 
>> program
>> unusable.
> 
> I didn't know that. Thanks, I've learned something today! :-)

Well imagine the following block:

"Text
text

Leave
Leave"

You want to cut the 2 lines of text, and then delete the white line.

But if you first copy those 2 lines and then press "dd" on the white 
line, the deletion will now have overwritten your save buffer.

With 'luck' your save buffer will have been moved to a higher number, so 
it might be sitting in "1", but actually I believe the text you saved is 
now actually in buffer "0".

There is a dedicated buffer only used for "copies". Now you have to use 
it using "0p.

Provided you don't have dead keys because that will $%#@ everything up.

So the problem with Vi is that they don't differentiate between delete 
and cut.

And that the primary clipboard is used for both.


>> Well I mean make left-shift + right alt the compose key by default.
>> 
>> Interferes with nothing.
> 
> As you wish. I use Right Alt, AltGr.

How do you type Euro key?

Oh you answered.

>> Now how to tell people...

> But IBM didn't copy the DEC Compose key. Sun did, IBM left it out.
> 
> And so had to produce dozens of different variants for languages with
> extra letters than the US ASCII A-Z, 0-9, $ set. French, German, all
> the Scandinavian and Nordic languages -- all rich countries who bought
> PCs and all needed their own keyboards.
> 
> Result: chaos.
> 
> If they'd given everyone a Compose key, supported it in DOS and said
> "if you want é, press Compose+e+'..." then we'd all have the US layout
> and a lot of pain would have been avoided.

I still feel something good would have been lost.

Now that I know how to type the Euro I guess I can put the compose on 
the same button as you have.

But apple normally also just uses key combinations right?

I mean clearly if dead keys are this stupid then compose is superior.

I prefer to have it on right-ctrl actually but right-alt is faster...

In the past while I was programming I would switch layouts but this was 
always annoying.

I still prefer a good dead-keys thing, in fact in the Netherlands we 
have always used US keyboard layout for computers.

We had Dutch layout for typing machines, but switched to US layout for 
computers.

The only issue with dead keys is that they have to be similar.

So we never had the "multitude of different keyboards".

The problem with Compose is that it is completely hidden.

Combination keys can be put directly on the keyboard.

How is a novice going to learn about these combinations?

If it was purely for proze I would never step away from the Windows dead 
keys.

It only "bugs" while doing <--.

And only slightly, but you get used to that and it never bugs you after 
that.

The biggest problem is while coding :p.

Particularly because you couldn't, and can't, "fix" applications to a 
certain keyboard layout between restarts.

> Compose + E + =
> 
> â?¬
> 
> There you go. :-)

Thanks.

> No, I know, but I would be resistant to anything from Vim's weird
> old-fashioned (even anachronistic) UI being made more widespread. It
> exists in its own little world and I'm happy to leave it there!

Lol. Afraid of contamination.

> Fair enough. But you can't just delete!

Yes well.

I guess it dates from the problems terminals had with arrow keys and key 
combinations.

It would be easy enough to add "ctrl-shift-right" to Vim honestly.

They already have ctrl-right...

Then make sure the "x" key doesn't overwrite things...

Make sure the undo buffer is per-word by default...

Ensure visual selection selects entire lines and not the first character 
of the line you happen to be at...

And so on and so on. There are plenty of things you can improve.

This "counting lines" thing is very annoying.

Where you have to use mental resources ahead of time to calculate the 
number of lines you want to delete instead of doing it visually.

Then I'm sure you can find a way...

To introduce a "cut" key as well.

In fact shift-X is "backspace", I mean, I get that it is for their 
command mode, but...

shift-X would be more natural as a cut operation.

Space and backspace do cursor movements in command mode... which is just 
always confusing to me even after many years and typically never what 
you want because you have (a) arrow keys and (b) hjkl keys.

So I also don't need "enter" to do "down".

So you can start cutting away all of the nonsense and in the end you 
will have a leaner machine that will more approach something sensible 
and then you will definitely get room I think to fix the anomalies.

But yeah whatever.

> https://en.wikipedia.org/wiki/Canon_Cat

Well you have your own goals to go after ;-).

> The Czechs don't consider the diacritical marks as "accents" over a
> normal letter. Like the Scandinavians, they are extra letters, tagged
> on the end of the alphabet.
> 
> Norwegian: A-Z, Ã?, Ã?, Ã?
> Swedish: A-Z, Ã?, Ã?, Ã?
> 
> Czech: A-Z, Ã?, Ã?, Ä?, Å?, Å , Ž
> 
> (I may have the order wrong.)
> 
> So, no dead keys. They need their own special keys, because they are
> not combinations, they are single letters.
> 
> But there are dead keys in the International layout in Windows, and
> people use an accent on its own -- ´ -- instead of an apostrophe.
> 
> "Liam´s book" instead of "Liam's book". If you look, it takes much
> more space. The gap between M and S is bigger with the accent than an
> actual apostrophe. This drives me _crazy_.

Not in monospace ;-).

But yeah.

So Czech also would not like compose key combinations for those letters?

> Compose is a wonderful one. Once you get used to it, you will wonder
> how you ever lived without it, I promise you!

Yeah I get that it solves the issue and sometimes I drooled about it in 
my sleep.... No just kidding.

But it seems that for practical purposes a dedicated feature set for a 
specific layout is more pleasant.

I could say "better".

But it needs to be done _right_.

If you can't do it right, as is in Linux usually the case, then yeah you 
need the simplest solution.

I never explored all of the KDE options in the Advanced Tab.

You can't select "alt-shift" as the key layout change key in the 
settings.
But you can select it using a special option in the advanced tab.

Little did I know.

Okay so there are people who have tried to fix the thing and apparently 
succeeded but it doesn't work for me.