Re: Re: lyx 1.20pre5 bugs and misses
On Mon, 13 May 2002 09:54:29 +0300 wrote Robin Turner [EMAIL PROTECTED]: Selection code is particularly crufty ... but Jug can it be fixed for all cases easily ? ... And I think it's not just habit, but there's a good reason for the common behavior to be so: after you hit 'paste' (whether via keyboard or mouse) you should be able to continue editing right there. If the first key you touch automatically destroys your pasted text (because it remained selected), I can't see that being anything other than an unpleasant surprise. I'm inclined to agree. Some word processor conventions come from pretending to be typewriters, but others have evolved through a long process of seeing what users need to do most often, and can do most easily. We can afford to ignore/modify some of the first group (e.g. LyX's ignoring double spaces) but, perhaps because of this, we should be careful to avoid flouting the more sensible conventions, and the pasting issue falls into this category, I think. Once we are at it: I am also always tumbling over the rather unusual way the selection works (in 1.1.6): In (almost) all X applications, selecting a text with the mouse will copy it to the selection as well, while Edit-Copy (^C) will put it in an internal paste buffer. In LyX, selecting with the mouse doesnot copy to the X-selection, while ^C does. Besides the inconsitency, I have the problem that when I want to copy a text from LyX to another application, I have to switch between mouse and keyboard: mark the text with the mouse (ok, the keyboard works as well) press ^C take the mouse and paste the text (PS: I could program my editor to insert the selection with a key-combi and use Alt tab to go there. Still, as mentioned in a recent post, drag and drop is one of the cases where even keyboard-freaks like me appreciate the pointing device.) ... And we are _really_ grateful for the fabulous tool that lyx is, honest. Amen to that. Indeed. Günter -- [EMAIL PROTECTED]
Re: Re: lyx 1.20pre5 bugs and misses
On Tue, May 14, 2002 at 10:59:14AM +0200, Guenter Milde wrote: Once we are at it: I am also always tumbling over the rather unusual way the selection works (in 1.1.6): In (almost) all X applications, selecting a text with the mouse will copy it to the selection as well, while Edit-Copy (^C) will put it in an internal paste buffer. In LyX, selecting with the mouse doesnot copy to the X-selection, while It does in 1.2.0 (actually this works slightly differently, but the effect is the same). regards john -- So what you're saying is screw the disabled and you want us to do the same ? No thanks... - Ian Hixie, bug 25537
Re: Re: lyx 1.20pre5 bugs and misses
On Mon, 13 May 2002 09:54:29 +0300 wrote Robin Turner [EMAIL PROTECTED]: Selection code is particularly crufty ... but Jug can it be fixed for all cases easily ? ... And I think it's not just habit, but there's a good reason for the common behavior to be so: after you hit 'paste' (whether via keyboard or mouse) you should be able to continue editing right there. If the first key you touch automatically destroys your pasted text (because it remained selected), I can't see that being anything other than an unpleasant surprise. I'm inclined to agree. Some word processor conventions come from pretending to be typewriters, but others have evolved through a long process of seeing what users need to do most often, and can do most easily. We can afford to ignore/modify some of the first group (e.g. LyX's ignoring double spaces) but, perhaps because of this, we should be careful to avoid flouting the more sensible conventions, and the pasting issue falls into this category, I think. Once we are at it: I am also always tumbling over the rather unusual way the selection works (in 1.1.6): In (almost) all X applications, selecting a text with the mouse will copy it to the selection as well, while Edit-Copy (^C) will put it in an internal paste buffer. In LyX, selecting with the mouse doesnot copy to the X-selection, while ^C does. Besides the inconsitency, I have the problem that when I want to copy a text from LyX to another application, I have to switch between mouse and keyboard: mark the text with the mouse (ok, the keyboard works as well) press ^C take the mouse and paste the text (PS: I could program my editor to insert the selection with a key-combi and use Alt tab to go there. Still, as mentioned in a recent post, drag and drop is one of the cases where even keyboard-freaks like me appreciate the pointing device.) ... And we are _really_ grateful for the fabulous tool that lyx is, honest. Amen to that. Indeed. Günter -- [EMAIL PROTECTED]
Re: Re: lyx 1.20pre5 bugs and misses
On Tue, May 14, 2002 at 10:59:14AM +0200, Guenter Milde wrote: Once we are at it: I am also always tumbling over the rather unusual way the selection works (in 1.1.6): In (almost) all X applications, selecting a text with the mouse will copy it to the selection as well, while Edit-Copy (^C) will put it in an internal paste buffer. In LyX, selecting with the mouse doesnot copy to the X-selection, while It does in 1.2.0 (actually this works slightly differently, but the effect is the same). regards john -- So what you're saying is screw the disabled and you want us to do the same ? No thanks... - Ian Hixie, bug 25537
Re: Re: lyx 1.20pre5 bugs and misses
On Mon, 13 May 2002 09:54:29 +0300 wrote Robin Turner <[EMAIL PROTECTED]>: > > > Selection code is particularly crufty ... but Jug can it be fixed > > > for all cases easily ? ... > > And I think it's not just habit, but there's a good reason for the > > common behavior to be so: after you hit 'paste' (whether via > > keyboard or mouse) you should be able to continue editing right > > there. If the first key you touch automatically destroys your > > pasted text (because it remained selected), I can't see that being > > anything other than an unpleasant surprise. > > I'm inclined to agree. Some word processor conventions come from > pretending to be typewriters, but others have evolved through a long > process of seeing what users need to do most often, and can do most > easily. We can afford to ignore/modify some of the first group (e.g. > LyX's ignoring double spaces) but, perhaps because of this, we should > be careful to avoid flouting the more sensible conventions, and the > pasting issue falls into this category, I think. Once we are at it: I am also always tumbling over the rather unusual way the selection works (in 1.1.6): In (almost) all X applications, selecting a text with the mouse will copy it to the selection as well, while Edit-Copy (^C) will put it in an internal paste buffer. In LyX, selecting with the mouse doesnot copy to the X-selection, while ^C does. Besides the inconsitency, I have the problem that when I want to copy a text from LyX to another application, I have to switch between mouse and keyboard: mark the text with the mouse (ok, the keyboard works as well) press ^C take the mouse and paste the text (PS: I could program my editor to insert the selection with a key-combi and use Alt tab to go there. Still, as mentioned in a recent post, drag and drop is one of the cases where even keyboard-freaks like me appreciate the pointing device.) > > ... And we are _really_ grateful for the fabulous tool that lyx > > is, honest. > > Amen to that. Indeed. Günter -- [EMAIL PROTECTED]
Re: Re: lyx 1.20pre5 bugs and misses
On Tue, May 14, 2002 at 10:59:14AM +0200, Guenter Milde wrote: > Once we are at it: I am also always tumbling over the rather unusual way the > selection works (in 1.1.6): > >In (almost) all X applications, selecting a text with the mouse will copy >it to the selection as well, while Edit-Copy (^C) will put it in an >internal paste buffer. >In LyX, selecting with the mouse doesnot copy to the X-selection, while It does in 1.2.0 (actually this works slightly differently, but the effect is the same). regards john -- "So what you're saying is "screw the disabled" and you want us to do the same ? No thanks..." - Ian Hixie, bug 25537
