Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-14 Thread Christoph Lohmann
Greetings. On Sat, 14 Mar 2015 07:39:29 +0100 Alex Pilon a...@alexpilon.ca wrote: On 03/10/2015 10:49 PM, Alex Pilon wrote: Are you thinking of something like the attached? On Wed, Mar 11, 2015 at 01:01:11PM -0400, Greg Reagle wrote: That looks fine to me, looking at it briefly, but I

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-13 Thread Samuel Holland
On March 12, 2015 11:05:10 AM CDT, Wander Nauta i...@wandernauta.nl wrote: Do most numpad-less laptop keyboards even have Insert or a middle mouse button? Macbooks have neither, I believe, and they're fairly popular. They have insert at fn+Enter. Of course, it's not labeled. -- Regards,

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-13 Thread Christoph Lohmann
Greetings. On Fri, 13 Mar 2015 17:49:45 +0100 Kai Hendry hen...@iki.fi wrote: My 2 cents: Suggestions to use 3 keys to copy paste SUCK Can we please have feature parity with MacOSX? cmd-c, cmd-v NEVER. Mac OS X users have to tortured and explictly selected for even more torture than

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Christoph Lohmann
Greetings. On Tue, 10 Mar 2015 22:02:30 +0100 Greg Reagle greg.rea...@umbc.edu wrote: On Mon, Mar 9, 2015, at 04:15 PM, Christoph Lohmann wrote: Can you please elaborate where you use both selections in parallel for different tasks and where st does interfere? [...] But this discussion

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Kai Hendry
My 2 cents: Suggestions to use 3 keys to copy paste SUCK Can we please have feature parity with MacOSX? cmd-c, cmd-v I guess cmd is that Windows key (keycode 133, Super_L?) on non-Apple hardware. Heavens know how to make cmd-c, cmd-v work in Chrome. BONUS: Keep selection in the clipboard

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Greg Reagle
On 03/10/2015 10:49 PM, Alex Pilon wrote: Are you thinking of something like the attached? That looks fine to me, looking at it briefly, but I haven't tested it (yet).

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Sébastien POHER
Le mardi 10 mars 2015 à 10:08:21, Markus Teich a écrit : Christoph Lohmann wrote: The text convinced me that st did it wrong. It is now using primary just for the selection. Are there any good suggestions for the shortcut to copy to the clipboard? Ctrl + y does interfere with everything.

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Greg Reagle
I see some people arguing *passionately* about the keybindings, as if they don't know that they can be changed. Yea we can and should have some discussion about reasonable defaults, but you can set the keys however you want in config.h. Just some perspective. Suckless people are passionate. :

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Alex Pilon
On Thu, Mar 12, 2015 at 04:35:58PM +0800, Kai Hendry wrote: My 2 cents: Suggestions to use 3 keys to copy paste SUCK Can we please have feature parity with MacOSX? cmd-c, cmd-v On Thu, Mar 12, 2015 at 08:17:22AM -0300, Amadeus Folego wrote: This can be a problem for (I think) many

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread stanio
* Alex Pilon 2015-03-12 15:17 Also, do most numpad-less laptop keyboards even have Insert all I've ever seen do. or a middle mouse button? some do have middle. all i've ever seen have at least 2 buttons. you can emulate middle button as simultaneous left+right. --s

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Wander Nauta
Do most numpad-less laptop keyboards even have Insert or a middle mouse button? Macbooks have neither, I believe, and they're fairly popular. Cheers, Wander On Thu, Mar 12, 2015 at 4:53 PM, sta...@cs.tu-berlin.de wrote: * Alex Pilon 2015-03-12 15:17 Also, do most numpad-less laptop

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Nick
Quoth Amadeus Folego: On Thu, Mar 12, 2015 at 05:05:10PM +0100, Wander Nauta wrote: Do most numpad-less laptop keyboards even have Insert or a middle mouse button? Macbooks have neither, I believe, and they're fairly popular. I thought there was a gesture to perform middle button,

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Amadeus Folego
On Thu, Mar 12, 2015 at 05:05:10PM +0100, Wander Nauta wrote: Do most numpad-less laptop keyboards even have Insert or a middle mouse button? Macbooks have neither, I believe, and they're fairly popular. I thought there was a gesture to perform middle button, was I wrong?

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Amadeus Folego
On Thu, Mar 12, 2015 at 04:35:58PM +0800, Kai Hendry wrote: My 2 cents: Suggestions to use 3 keys to copy paste SUCK Can we please have feature parity with MacOSX? cmd-c, cmd-v This can be a problem for (I think) many users of st that use this key as the modifier for tiling window

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-12 Thread Alex Pilon
On 03/10/2015 10:49 PM, Alex Pilon wrote: Are you thinking of something like the attached? On Wed, Mar 11, 2015 at 01:01:11PM -0400, Greg Reagle wrote: That looks fine to me, looking at it briefly, but I haven't tested it (yet). Sorry about the noise. It *seemed* to work before; serves me

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-11 Thread Roberto E. Vargas Caballero
I really don't like the idea of C-S-C or M3-C as these are really basic keybinds and may be used for applications. Also the proximity with C-C makes it easier to terminate a running application when you just wanted to copy some text. It is impossible to use ctrl + shift combinations in the

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-11 Thread Amadeus Folego
On Wed, Mar 11, 2015 at 08:05:37AM +0100, Roberto E. Vargas Caballero wrote: I really don't like the idea of C-S-C or M3-C as these are really basic keybinds and may be used for applications. Also the proximity with C-C makes it easier to terminate a running application when you just

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-10 Thread Alex Pilon
On Tue, Mar 10, 2015 at 05:18:49PM -0400, Greg Reagle wrote: It could go the other way and do a variant of Ctrl+C for copy and Ctrl+V for paste. I wouldn't use them directly because the programs running in st probably need those keys. So Alt+Ctrl+C/V or Shitf+Ctrl+C/V or Alt+C/V. Also, it

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-10 Thread Amadeus Folego
On Tue, Mar 10, 2015 at 05:18:49PM -0400, Greg Reagle wrote: It could go the other way and do a variant of Ctrl+C for copy and Ctrl+V for paste. I wouldn't use them directly because the programs running in st probably need those keys. So Alt+Ctrl+C/V or Shitf+Ctrl+C/V or Alt+C/V. Also, it

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-10 Thread Markus Teich
Christoph Lohmann wrote: The text convinced me that st did it wrong. It is now using primary just for the selection. Are there any good suggestions for the shortcut to copy to the clipboard? Ctrl + y does interfere with everything. Heyho, some other terminal emulators use ctrl-shift-c and

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-10 Thread Greg Reagle
On Tue, Mar 10, 2015, at 05:02 PM, Christoph Lohmann wrote: The text convinced me that st did it wrong. It is now using primary just for the selection. Are there any good suggestions for the shortcut to copy to the clipboard? Ctrl + y does interfere with everything. My two cents . . . It

Re: [dev] st: selecting text affects both primary and clipbaord

2015-03-09 Thread Greg Reagle
On Mon, Mar 9, 2015, at 04:15 PM, Christoph Lohmann wrote: Can you please elaborate where you use both selections in parallel for different tasks and where st does interfere? Hi Christoph. Well actually yes I do use both selections independently. I use clipboard selection when I explicitly

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-21 Thread k0ga
I know this isn't a democracy, but I agree with Greg, it makes more sense to only set PRIMARY, not CLIPBOARD, in selcopy. Removing the clipboard-related lines from xsetsel seems to do the trick. I've attached a patch that does just that. I agree here, it shouldn't modiy the CLIPBOARD

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-21 Thread Greg Reagle
On Sat, Feb 21, 2015 at 09:26:50AM +0100, k...@shike2.com wrote: You can do it by yourself. Clone the wiki repository and push the change. Oh, I did not know that the wiki was in a git repository. Thank you for informing me. I don't think I have permission to push (I have limited experience

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread Greg Reagle
On Thu, Feb 19, 2015, at 06:46 PM, Wander Nauta wrote: I know this isn't a democracy, but I agree with Greg, it makes more sense to only set PRIMARY, not CLIPBOARD, in selcopy. Removing the clipboard-related lines from xsetsel seems to do the trick. I've attached a patch that does just that.

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread k0ga
Hello list, I know this isn't a democracy, but I agree with Greg, it makes more sense to only set PRIMARY, not CLIPBOARD, in selcopy. Removing the clipboard-related lines from xsetsel seems to do the trick. I've attached a patch that does just that. I agree here, it shouldn't modiy the

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread stanio
* k...@shike2.com 2015-02-20 17:39 I agree here, it shouldn't modiy the CLIPBOARD seletction. Sometime is good to have different things in both selections. If nobady claims about it I will apply your patch. I'd leave it as is, in order not to break scrips which expect to read something from

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread hiro
Just allow user to set the behavior with some foot switch.

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread random832
On Fri, Feb 20, 2015, at 12:38, sta...@cs.tu-berlin.de wrote: * k...@shike2.com 2015-02-20 17:39 I agree here, it shouldn't modiy the CLIPBOARD seletction. Sometime is good to have different things in both selections. If nobady claims about it I will apply your patch. I'd leave it as is,

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread stanio
* Greg Reagle 2015-02-20 20:07 It is true that the only reason I select text in st is to copy it, but I still don't want it clobbering my clipboard. does the current behaviour break some scripts or habits of yours and how?

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread Greg Reagle
On Fri, Feb 20, 2015, at 01:50 PM, random...@fastmail.us wrote: Another reason to leave it as-is is that, while in other applications it is reasonable to select text for some purpose other than copying it (e.g. to delete it or replace it), people will not want their clipboard obliterated in

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread hiro
having more than one buffer is just annoying, and there are no well behaved X applications anyways.

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-20 Thread Greg Reagle
On Fri, Feb 20, 2015, at 02:18 PM, sta...@cs.tu-berlin.de wrote: * Greg Reagle 2015-02-20 20:07 It is true that the only reason I select text in st is to copy it, but I still don't want it clobbering my clipboard. does the current behaviour break some scripts or habits of yours and how?

[dev] st: selecting text affects both primary and clipbaord

2015-02-19 Thread Greg Reagle
When I select text in st using the mouse, it sets both the primary selection and the clipboard selection. It should only set the primary selection. The clipboard is supposed to be only for explicitly requested copying. From http://standards.freedesktop.org/clipboards-spec/clipboards-latest.txt:

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-19 Thread Amadeus Folego
On Fri, Feb 20, 2015 at 12:46:20AM +0100, Wander Nauta wrote: Hello list, I know this isn't a democracy, but I agree with Greg, it makes more sense to only set PRIMARY, not CLIPBOARD, in selcopy. Removing the clipboard-related lines from xsetsel seems to do the trick. I've attached a patch

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-19 Thread Wander Nauta
Hello list, I know this isn't a democracy, but I agree with Greg, it makes more sense to only set PRIMARY, not CLIPBOARD, in selcopy. Removing the clipboard-related lines from xsetsel seems to do the trick. I've attached a patch that does just that. Cheers, Wander On Thu, Feb 19, 2015 at 10:30

Re: [dev] st: selecting text affects both primary and clipbaord

2015-02-19 Thread Dmitrij D. Czarkoff
Greg Reagle said: - selecting but with no explicit copy should only set PRIMARY, never CLIPBOARD FWIW in suckless context selecting _is_ explicit copy. -- Dmitrij D. Czarkoff