Re: keyboard question
On 4.07.08, Dov Feldstern wrote: Pavel Sanda wrote: On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: Does anybody still use it and could not use alternatives provided by his environment? ... Pavel is correct, there are certain features which the keymap offers which I think would be very hard to offer, especially in a system-independent manner, without keymaps (details below). ... [3 valid points in favour of LyX keymaps] ... It would be nice it these arguments could be made public permanently * in the LyX wiki or * in the Customisation guide (as preface to the keymaps section). maybe weighting the pros and cons of system bases via LyX keymap switching. I haven't followed this thread very closely, and I do not use dead keys --- I'm not sure how they're supposed to work at all --- so I don't feel qualified to provide suggestions with regard to the original problem. It isn't clear to me whether keymaps were or were not being used in this case. I suppose during the experimenting ther was one stage where both, the system and LyX defined dead keys which resulted in double-dead keys. This should of course not happen (but can arise if a pre-set keymap is activated and the system already defines dead keys). Günter
Re: keyboard question
On 4.07.08, Dov Feldstern wrote: Pavel Sanda wrote: On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: Does anybody still use it and could not use alternatives provided by his environment? ... Pavel is correct, there are certain features which the keymap offers which I think would be very hard to offer, especially in a system-independent manner, without keymaps (details below). ... [3 valid points in favour of LyX keymaps] ... It would be nice it these arguments could be made public permanently * in the LyX wiki or * in the Customisation guide (as preface to the keymaps section). maybe weighting the pros and cons of system bases via LyX keymap switching. I haven't followed this thread very closely, and I do not use dead keys --- I'm not sure how they're supposed to work at all --- so I don't feel qualified to provide suggestions with regard to the original problem. It isn't clear to me whether keymaps were or were not being used in this case. I suppose during the experimenting ther was one stage where both, the system and LyX defined dead keys which resulted in double-dead keys. This should of course not happen (but can arise if a pre-set keymap is activated and the system already defines dead keys). Günter
Re: keyboard question
On 4.07.08, Dov Feldstern wrote: > Pavel Sanda wrote: >>> On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: > Does anybody still use it and could not use alternatives provided > by his environment? ... > Pavel is correct, there are certain features which the keymap offers > which I think would be very hard to offer, especially in a > system-independent manner, without keymaps (details below). ... [3 valid points in favour of LyX keymaps] ... It would be nice it these arguments could be made public permanently * in the LyX wiki or * in the Customisation guide (as preface to the keymaps section). maybe weighting the pros and cons of system bases via LyX keymap switching. > I haven't followed this thread very closely, and I do not use dead keys > --- I'm not sure how they're supposed to work at all --- so I don't feel > qualified to provide suggestions with regard to the original problem. It > isn't clear to me whether keymaps were or were not being used in this > case. I suppose during the experimenting ther was one stage where both, the system and LyX defined dead keys which resulted in "double-dead" keys. This should of course not happen (but can arise if a pre-set keymap is activated and the system already defines dead keys). Günter
Re: keyboard question
Pavel Sanda wrote: On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. The main argument I remember was It works, so why remove it. Now we seem to have cases where it works (as expected) is not necessarily true... no, one relevant case was to be able to use the same scheme for different platforms; another argument came from Dov, probably something with hebrew things... Pavel is correct, there are certain features which the keymap offers which I think would be very hard to offer, especially in a system-independent manner, without keymaps (details below). I haven't followed this thread very closely, and I do not use dead keys --- I'm not sure how they're supposed to work at all --- so I don't feel qualified to provide suggestions with regard to the original problem. It isn't clear to me whether keymaps were or were not being used in this case. But perhaps if they were, then the user should just try to shut them off. In any case, I don't think that keymaps should ever interfere with anything, if they are shut off (if they do, it's a bug, not a problem with keymaps per se). Specifically, these are some of the features which I think would be hard to implement without keymaps: *) when moving the cursor across text in different languages, it's nice if the language is automatically changed to match the text under the cursor (similar to when placing the cursor on \emph text, the input automatically becomes \emph. I don't know how this could be done without keymaps. *) at least on my setup, which I switch the language at the keyboard level, it is switched for all applications. I find it much nicer if the language is switched only for the single application (in our case, LyX) in which I asked to switch it. An extreme example of why the alternative is annoying: if I switch the keyboard to hebrew in LyX, and then ctrl-d to view the dvi, xdvik pops up, but then doesn't recognize 'q' to close (because my keyboard is now set to Hebrew). *) At least for hebrew, we need to perform two actions when switching languages: (1) change the input to hebrew; and (2): switch the text language to hebrew. It's nice if we can perform both actions with one keypress. This is not possible, though, if the keyboard input switching happens independently of LyX. If all of the above issues can be solved without LyX's keymaps, then I don't mind having keymaps removed. But until that time, I do use keymaps. And again, I don't think it should interfere with anything for anyone who doesn't want to use them. Dov P.S. here's a link to my arguments in favor of keymaps from a previous round of discussions: http://permalink.gmane.org/gmane.editors.lyx.devel/88939 (Pavel --- thanks for remembering that this issue is important to me!)
Re: keyboard question
Pavel Sanda wrote: On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. The main argument I remember was It works, so why remove it. Now we seem to have cases where it works (as expected) is not necessarily true... no, one relevant case was to be able to use the same scheme for different platforms; another argument came from Dov, probably something with hebrew things... Pavel is correct, there are certain features which the keymap offers which I think would be very hard to offer, especially in a system-independent manner, without keymaps (details below). I haven't followed this thread very closely, and I do not use dead keys --- I'm not sure how they're supposed to work at all --- so I don't feel qualified to provide suggestions with regard to the original problem. It isn't clear to me whether keymaps were or were not being used in this case. But perhaps if they were, then the user should just try to shut them off. In any case, I don't think that keymaps should ever interfere with anything, if they are shut off (if they do, it's a bug, not a problem with keymaps per se). Specifically, these are some of the features which I think would be hard to implement without keymaps: *) when moving the cursor across text in different languages, it's nice if the language is automatically changed to match the text under the cursor (similar to when placing the cursor on \emph text, the input automatically becomes \emph. I don't know how this could be done without keymaps. *) at least on my setup, which I switch the language at the keyboard level, it is switched for all applications. I find it much nicer if the language is switched only for the single application (in our case, LyX) in which I asked to switch it. An extreme example of why the alternative is annoying: if I switch the keyboard to hebrew in LyX, and then ctrl-d to view the dvi, xdvik pops up, but then doesn't recognize 'q' to close (because my keyboard is now set to Hebrew). *) At least for hebrew, we need to perform two actions when switching languages: (1) change the input to hebrew; and (2): switch the text language to hebrew. It's nice if we can perform both actions with one keypress. This is not possible, though, if the keyboard input switching happens independently of LyX. If all of the above issues can be solved without LyX's keymaps, then I don't mind having keymaps removed. But until that time, I do use keymaps. And again, I don't think it should interfere with anything for anyone who doesn't want to use them. Dov P.S. here's a link to my arguments in favor of keymaps from a previous round of discussions: http://permalink.gmane.org/gmane.editors.lyx.devel/88939 (Pavel --- thanks for remembering that this issue is important to me!)
Re: keyboard question
Pavel Sanda wrote: On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. The main argument I remember was "It works, so why remove it". Now we seem to have cases where "it works (as expected)" is not necessarily true... no, one relevant case was to be able to use the same scheme for different platforms; another argument came from Dov, probably something with hebrew things... Pavel is correct, there are certain features which the keymap offers which I think would be very hard to offer, especially in a system-independent manner, without keymaps (details below). I haven't followed this thread very closely, and I do not use dead keys --- I'm not sure how they're supposed to work at all --- so I don't feel qualified to provide suggestions with regard to the original problem. It isn't clear to me whether keymaps were or were not being used in this case. But perhaps if they were, then the user should just try to shut them off. In any case, I don't think that keymaps should ever interfere with anything, if they are shut off (if they do, it's a bug, not a problem with keymaps per se). Specifically, these are some of the features which I think would be hard to implement without keymaps: *) when moving the cursor across text in different languages, it's nice if the language is automatically changed to match the text under the cursor (similar to when placing the cursor on \emph text, the input automatically becomes \emph. I don't know how this could be done without keymaps. *) at least on my setup, which I switch the language at the keyboard level, it is switched for all applications. I find it much nicer if the language is switched only for the single application (in our case, LyX) in which I asked to switch it. An extreme example of why the alternative is annoying: if I switch the keyboard to hebrew in LyX, and then ctrl-d to view the dvi, xdvik pops up, but then doesn't recognize 'q' to close (because my keyboard is now set to Hebrew). *) At least for hebrew, we need to perform two actions when switching languages: (1) change the input to hebrew; and (2): switch the text language to hebrew. It's nice if we can perform both actions with one keypress. This is not possible, though, if the keyboard input switching happens independently of LyX. If all of the above issues can be solved without LyX's keymaps, then I don't mind having keymaps removed. But until that time, I do use keymaps. And again, I don't think it should interfere with anything for anyone who doesn't want to use them. Dov P.S. here's a link to my arguments in favor of keymaps from a previous round of discussions: http://permalink.gmane.org/gmane.editors.lyx.devel/88939 (Pavel --- thanks for remembering that this issue is important to me!)
Re: keyboard question
Furthermore, I don't get a single quote this way, but an isolated acute accent. In other words, with such a keyboard remap, it's impossible to get a single quote in LyX. And at last, only the accents (acute, grave, circonflex...) exhibit this behavior. The double quote retains its normal dead key behavior. All this seems stranger and stranger... Why doesn't LyX react as most other apps?... this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. pavel
Re: keyboard question
On Wed, Jul 02, 2008 at 07:55:21PM +0200, Pavel Sanda wrote: Furthermore, I don't get a single quote this way, but an isolated acute accent. In other words, with such a keyboard remap, it's impossible to get a single quote in LyX. And at last, only the accents (acute, grave, circonflex...) exhibit this behavior. The double quote retains its normal dead key behavior. All this seems stranger and stranger... Why doesn't LyX react as most other apps?... this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? Andre'
Re: keyboard question
this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. pavel
Re: keyboard question
On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. The main argument I remember was It works, so why remove it. Now we seem to have cases where it works (as expected) is not necessarily true... Andre'
Re: keyboard question
On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. The main argument I remember was It works, so why remove it. Now we seem to have cases where it works (as expected) is not necessarily true... no, one relevant case was to be able to use the same scheme for different platforms; another argument came from Dov, probably something with hebrew things... pavel
Re: keyboard question
Furthermore, I don't get a single quote this way, but an isolated acute accent. In other words, with such a keyboard remap, it's impossible to get a single quote in LyX. And at last, only the accents (acute, grave, circonflex...) exhibit this behavior. The double quote retains its normal dead key behavior. All this seems stranger and stranger... Why doesn't LyX react as most other apps?... this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. pavel
Re: keyboard question
On Wed, Jul 02, 2008 at 07:55:21PM +0200, Pavel Sanda wrote: Furthermore, I don't get a single quote this way, but an isolated acute accent. In other words, with such a keyboard remap, it's impossible to get a single quote in LyX. And at last, only the accents (acute, grave, circonflex...) exhibit this behavior. The double quote retains its normal dead key behavior. All this seems stranger and stranger... Why doesn't LyX react as most other apps?... this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? Andre'
Re: keyboard question
this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. pavel
Re: keyboard question
On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. The main argument I remember was It works, so why remove it. Now we seem to have cases where it works (as expected) is not necessarily true... Andre'
Re: keyboard question
On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? yes it is still used, i remember some screem last time we discussed this. The main argument I remember was It works, so why remove it. Now we seem to have cases where it works (as expected) is not necessarily true... no, one relevant case was to be able to use the same scheme for different platforms; another argument came from Dov, probably something with hebrew things... pavel
Re: keyboard question
> Furthermore, I don't get a single quote this way, but an isolated acute > accent. In other words, with such a keyboard remap, it's impossible to > get a single quote in LyX. > > And at last, only the accents (acute, grave, circonflex...) exhibit this > behavior. The double quote retains its normal dead key behavior. > > All this seems stranger and stranger... Why doesn't LyX react as most other > apps?... this keymap part of lyx is from days when changing keymaps was not so easy as it is now under X. by default these things should be maintained in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. pavel
Re: keyboard question
On Wed, Jul 02, 2008 at 07:55:21PM +0200, Pavel Sanda wrote: > > Furthermore, I don't get a single quote this way, but an isolated acute > > accent. In other words, with such a keyboard remap, it's impossible to > > get a single quote in LyX. > > > > And at last, only the accents (acute, grave, circonflex...) exhibit this > > behavior. The double quote retains its normal dead key behavior. > > > > All this seems stranger and stranger... Why doesn't LyX react as most other > > apps?... > > this keymap part of lyx is from days when changing keymaps was not so > easy as it is now under X. by default these things should be maintained > in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. Should we get rid of our own keyboard mapping soonish then? Does anybody still use it and could not use alternatives provided by his environment? Andre'
Re: keyboard question
> > this keymap part of lyx is from days when changing keymaps was not so > > easy as it is now under X. by default these things should be maintained > > in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. > > Should we get rid of our own keyboard mapping soonish then? > > Does anybody still use it and could not use alternatives provided by his > environment? yes it is still used, i remember some screem last time we discussed this. pavel
Re: keyboard question
On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: > > > this keymap part of lyx is from days when changing keymaps was not so > > > easy as it is now under X. by default these things should be maintained > > > in X settings not in lyx. here lyx reacts as most other apps wrt keymaps. > > > > Should we get rid of our own keyboard mapping soonish then? > > > > Does anybody still use it and could not use alternatives provided by his > > environment? > > yes it is still used, i remember some screem last time we discussed this. The main argument I remember was "It works, so why remove it". Now we seem to have cases where "it works (as expected)" is not necessarily true... Andre'
Re: keyboard question
> On Wed, Jul 02, 2008 at 09:13:27PM +0200, Pavel Sanda wrote: > > > Should we get rid of our own keyboard mapping soonish then? > > > > > > Does anybody still use it and could not use alternatives provided by his > > > environment? > > > > yes it is still used, i remember some screem last time we discussed this. > > The main argument I remember was "It works, so why remove it". Now we > seem to have cases where "it works (as expected)" is not necessarily > true... no, one relevant case was to be able to use the same scheme for different platforms; another argument came from Dov, probably something with hebrew things... pavel
Re: keyboard question
Hi Hellmut, On Friday 27 June 2008 00:05 +0200, Hellmut Weber wrote: [...] Under Linux there is a nice little program 'xev' which gives you the key code for all keys. Interesting. I didn't know this, I'll check this out. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. [...] That's just what I have done, I read the docs too :-) But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). At least, I was unable to get any \bind 'c sequence working. Following Günter, I used the Meta key to get a workaround. Regards, -- Daniel Clément
Re: keyboard question
Hi Daniel, Under Linux there is a nice little program 'xev' which gives you the key code for all keys. Interesting. I didn't know this, I'll check this out. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. [...] That's just what I have done, I read the docs too :-) But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). IIRC you must indicate somewhere, sorry I don't remember correctly, that you want these special keys (accents, tilde and the like) to behave as dead keys, i.e. to work only together with another key. Hopefully somebody else in this list can indicate where to define this behaviour. HTH Hellmut -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
On 27.06.08, Hellmut Weber wrote: But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). IIRC you must indicate somewhere, sorry I don't remember correctly, that you want these special keys (accents, tilde and the like) to behave as dead keys, i.e. to work only together with another key. 1. If the accent keys are *not* defined as dead key in the XWin setup, it's relatively easy to give them a dead key behaviour in LyX by binding them to accent-* functions (if you know their names). You cannot define to get ´a - á and ´c - ç, though (but will receive ´c - ć). 2. If the accent keys are defined as dead keys in the XWin setup (usually by choosing some XKB option in xorg.conf or some xorg.conf-generating software), LyX will not see distinct keystrokes, but the X server will combine e.g. ´c to one ć event and report this to LyX. It should be possible to configure LyX to do some special action whenever receiving an ć event, however this seems not to work. I also tested with ł == lstroke which I can input via: ł == WinKey + / l ł == AltGr + l In both cases, it self-inserted even when the bind file contains \bind lstroke unicode-insert 0x00e7 # insert a ç (c with cedilla) Maybe I have to specify some modifier key. Maybe there was a name change, latinkeys.bind is outdated but the keys are self-inserting anyway. (There was a name-change in some cases with the xforms-QT transition.) Unfortunately, the German Customization guide does not specify the syntax of the key names :-( Günter
Re: keyboard question
Dear LyX gurus: why does LyX ignore: \bind cacute unicode-insert 0x00e7 while e.g. \bind M-C-comma unicode-insert 0x00e7 # insert a ç (c with cedilla) works? because Qt::Key_Comma exists, while Qt::Key_cacute does not (http://doc.trolltech.com/4.4/qt.html). in case it doesn't appeared in this thread you can use another key as cedilla dead key e.g. \bind F5 accent-cedilla and then use F5+key. changing working of dead keys as acute+c - cedilla+c should be done at XWindows-level, LyX should get the whole deadkey+key char from X. Daniel wrote other apps get cedilla while LyX acute, this seems to be miraculous :) iirc i made keyboard tricks via xmodmap and direct editing of XKeyboardConfig files in /usr/share/X11/xkb/symbols. pavel
Re: keyboard question
PS Here is what I tried: in american.kmap I put \kmod ' acute aeiouAEIOU # \kmod , cedilla native \kxmod ' c ç just a wild guess, what happen with this: \kxmod acute c ç pavel
Re: keyboard question
On Friday 27 June 2008 17:29 +0200, Pavel Sanda wrote: PS Here is what I tried: in american.kmap I put \kmod ' acute aeiouAEIOU # \kmod , cedilla native \kxmod ' c ç just a wild guess, what happen with this: \kxmod acute c ç pavel This still gives me an accented c... However, it does have a strange side effect. In order to test this, I choose remap keyboard in LyX, then point to the american.kmap edited as above. Then, my dead keys seem to be doubly dead (undead?) in the following sense: I must type _two_ spaces after a dead key so as to get the corresponding character (normally, one is enough). Furthermore, I don't get a single quote this way, but an isolated acute accent. In other words, with such a keyboard remap, it's impossible to get a single quote in LyX. And at last, only the accents (acute, grave, circonflex...) exhibit this behavior. The double quote retains its normal dead key behavior. All this seems stranger and stranger... Why doesn't LyX react as most other apps?... -- Daniel Clément
Re: keyboard question
Hi Hellmut, On Friday 27 June 2008 00:05 +0200, Hellmut Weber wrote: [...] Under Linux there is a nice little program 'xev' which gives you the key code for all keys. Interesting. I didn't know this, I'll check this out. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. [...] That's just what I have done, I read the docs too :-) But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). At least, I was unable to get any \bind 'c sequence working. Following Günter, I used the Meta key to get a workaround. Regards, -- Daniel Clément
Re: keyboard question
Hi Daniel, Under Linux there is a nice little program 'xev' which gives you the key code for all keys. Interesting. I didn't know this, I'll check this out. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. [...] That's just what I have done, I read the docs too :-) But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). IIRC you must indicate somewhere, sorry I don't remember correctly, that you want these special keys (accents, tilde and the like) to behave as dead keys, i.e. to work only together with another key. Hopefully somebody else in this list can indicate where to define this behaviour. HTH Hellmut -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
On 27.06.08, Hellmut Weber wrote: But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). IIRC you must indicate somewhere, sorry I don't remember correctly, that you want these special keys (accents, tilde and the like) to behave as dead keys, i.e. to work only together with another key. 1. If the accent keys are *not* defined as dead key in the XWin setup, it's relatively easy to give them a dead key behaviour in LyX by binding them to accent-* functions (if you know their names). You cannot define to get ´a - á and ´c - ç, though (but will receive ´c - ć). 2. If the accent keys are defined as dead keys in the XWin setup (usually by choosing some XKB option in xorg.conf or some xorg.conf-generating software), LyX will not see distinct keystrokes, but the X server will combine e.g. ´c to one ć event and report this to LyX. It should be possible to configure LyX to do some special action whenever receiving an ć event, however this seems not to work. I also tested with ł == lstroke which I can input via: ł == WinKey + / l ł == AltGr + l In both cases, it self-inserted even when the bind file contains \bind lstroke unicode-insert 0x00e7 # insert a ç (c with cedilla) Maybe I have to specify some modifier key. Maybe there was a name change, latinkeys.bind is outdated but the keys are self-inserting anyway. (There was a name-change in some cases with the xforms-QT transition.) Unfortunately, the German Customization guide does not specify the syntax of the key names :-( Günter
Re: keyboard question
Dear LyX gurus: why does LyX ignore: \bind cacute unicode-insert 0x00e7 while e.g. \bind M-C-comma unicode-insert 0x00e7 # insert a ç (c with cedilla) works? because Qt::Key_Comma exists, while Qt::Key_cacute does not (http://doc.trolltech.com/4.4/qt.html). in case it doesn't appeared in this thread you can use another key as cedilla dead key e.g. \bind F5 accent-cedilla and then use F5+key. changing working of dead keys as acute+c - cedilla+c should be done at XWindows-level, LyX should get the whole deadkey+key char from X. Daniel wrote other apps get cedilla while LyX acute, this seems to be miraculous :) iirc i made keyboard tricks via xmodmap and direct editing of XKeyboardConfig files in /usr/share/X11/xkb/symbols. pavel
Re: keyboard question
PS Here is what I tried: in american.kmap I put \kmod ' acute aeiouAEIOU # \kmod , cedilla native \kxmod ' c ç just a wild guess, what happen with this: \kxmod acute c ç pavel
Re: keyboard question
On Friday 27 June 2008 17:29 +0200, Pavel Sanda wrote: PS Here is what I tried: in american.kmap I put \kmod ' acute aeiouAEIOU # \kmod , cedilla native \kxmod ' c ç just a wild guess, what happen with this: \kxmod acute c ç pavel This still gives me an accented c... However, it does have a strange side effect. In order to test this, I choose remap keyboard in LyX, then point to the american.kmap edited as above. Then, my dead keys seem to be doubly dead (undead?) in the following sense: I must type _two_ spaces after a dead key so as to get the corresponding character (normally, one is enough). Furthermore, I don't get a single quote this way, but an isolated acute accent. In other words, with such a keyboard remap, it's impossible to get a single quote in LyX. And at last, only the accents (acute, grave, circonflex...) exhibit this behavior. The double quote retains its normal dead key behavior. All this seems stranger and stranger... Why doesn't LyX react as most other apps?... -- Daniel Clément
Re: keyboard question
Hi Hellmut, On Friday 27 June 2008 00:05 +0200, Hellmut Weber wrote: [...] > Under Linux there is a nice little program 'xev' which gives you the key > code for all keys. Interesting. I didn't know this, I'll check this out. > You could try to define your personal bind file in '$HOME/.lyx/bind/...' > You'll find info on global and local bind files somewhere in the (more > advanced ;-) LyX documentation. [...] That's just what I have done, I read the docs too :-) But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). At least, I was unable to get any \bind "'c" sequence working. Following Günter, I used the Meta key to get a workaround. Regards, -- Daniel Clément
Re: keyboard question
Hi Daniel, Under Linux there is a nice little program 'xev' which gives you the key code for all keys. Interesting. I didn't know this, I'll check this out. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. [...] That's just what I have done, I read the docs too :-) But as I said in my previous reply to Günter, I doubt that the bind file can take care of a dead key (the acute accent in my case). IIRC you must indicate somewhere, sorry I don't remember correctly, that you want these special keys (accents, tilde and the like) to behave as dead keys, i.e. to work only together with another key. Hopefully somebody else in this list can indicate where to define this behaviour. HTH Hellmut -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
On 27.06.08, Hellmut Weber wrote: >> But as I said in my previous reply to Günter, I doubt that the bind file >> can take care of a dead key (the acute accent in my case). > IIRC you must indicate somewhere, sorry I don't remember correctly, that > you want these special keys (accents, tilde and the like) to behave as > dead keys, i.e. to work only together with another key. 1. If the accent keys are *not* defined as dead key in the XWin setup, it's relatively easy to give them a "dead key behaviour" in LyX by binding them to accent-* functions (if you know their names). You cannot define to get ´a -> á and ´c -> ç, though (but will receive ´c -> ć). 2. If the accent keys are defined as dead keys in the XWin setup (usually by choosing some XKB option in xorg.conf or some xorg.conf-generating software), LyX will not "see" distinct keystrokes, but the X server will combine e.g. ´c to one "ć event" and report this to LyX. It should be possible to configure LyX to do some special action whenever receiving an "ć event", however this seems not to work. I also tested with ł == "lstroke" which I can input via: ł <== WinKey + / l ł <== AltGr + l In both cases, it self-inserted even when the bind file contains \bind "lstroke" "unicode-insert 0x00e7" # insert a ç (c with cedilla) Maybe I have to specify some modifier key. Maybe there was a name change, latinkeys.bind is outdated but the keys are self-inserting anyway. (There was a name-change in some cases with the xforms->QT transition.) Unfortunately, the German Customization guide does not specify the syntax of the key names :-( Günter
Re: keyboard question
> Dear LyX gurus: why does LyX ignore: > > \bind "cacute" "unicode-insert 0x00e7" > > while e.g. > > \bind "M-C-comma" "unicode-insert 0x00e7" # insert a ç (c with cedilla) > > works? because Qt::Key_Comma exists, while Qt::Key_cacute does not (http://doc.trolltech.com/4.4/qt.html). in case it doesn't appeared in this thread you can use another key as "cedilla dead key" e.g. \bind "F5" "accent-cedilla" and then use F5+key. changing working of dead keys as acute+c -> cedilla+c should be done at XWindows-level, LyX should get the whole deadkey+key char from X. Daniel wrote other apps get cedilla while LyX acute, this seems to be miraculous :) iirc i made keyboard tricks via xmodmap and direct editing of XKeyboardConfig files in /usr/share/X11/xkb/symbols. pavel
Re: keyboard question
> PS Here is what I tried: in american.kmap I put > > \kmod ' acute aeiouAEIOU > > # \kmod "," cedilla native > > \kxmod ' c ç just a wild guess, what happen with this: \kxmod acute c ç pavel
Re: keyboard question
On Friday 27 June 2008 17:29 +0200, Pavel Sanda wrote: > > PS Here is what I tried: in american.kmap I put > > > > \kmod ' acute aeiouAEIOU > > > > # \kmod "," cedilla native > > > > \kxmod ' c ç > > just a wild guess, what happen with this: > > \kxmod acute c ç > > pavel This still gives me an accented c... However, it does have a strange side effect. In order to test this, I choose "remap keyboard" in LyX, then point to the american.kmap edited as above. Then, my dead keys seem to be "doubly dead" (undead?) in the following sense: I must type _two_ spaces after a dead key so as to get the corresponding character (normally, one is enough). Furthermore, I don't get a single quote this way, but an isolated acute accent. In other words, with such a keyboard remap, it's impossible to get a single quote in LyX. And at last, only the accents (acute, grave, circonflex...) exhibit this behavior. The double quote retains its normal dead key behavior. All this seems stranger and stranger... Why doesn't LyX react as most other apps?... -- Daniel Clément
Re: keyboard question
Günter, The more I try, the less I understand... Nothing seems to work as it should! See the reports of my attempts below On Wednesday 25 June 2008 à 17:56 +0200, G. Milde wrote: On 25.06.08, Daniel Clément wrote: On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Not quite sure how to check this but I'd bet on single character... OK. Just let's assume this. Maybe it was not the case after all [...] Maybe LyX does not map it to ç because it does not see the defined char. Do you mean: in the kmap file, or the bind file? If the latter, it has to be something like that, because I do have some personal keybindings that work. The bind file. It uses a special naming for non-ASCII input. Looking at the bind files that ship with LyX helps: $LYXDIR/bind/latinkeys.bind contains the definition: \bind cacuteself-insert which you should change to unicode-insert ... (as proposed earlier in this thread). I tried this in my /home/daniel/.lyx/bind/swpperso.bind file. (It's the modified sciword.bind file that I use; it contains the same shortcuts as in my former SciWord.) It did not work. Then I noticed that this file eventually calls latinkeys.bind. So I tried to edit it directly, replacing the suggested line with \bind cacute unicode-insert 0x00e7 This, to my great disappointment, did not work either (always acute-accented c). Hope this helps. BTW: Alternatives that work here are 1. Combining-Key + Komma followed by c. (in my setup, X11 translates this to ç, Combining-Key is the Windows Key) 2. \bind Meta , accent-cedilla I assume \bind M-,? --tried them both however. and then Alt-, c. I tried this too, and it did not act as I wanted: M-, enters math mode!... There mus be a conflict with another binding, but I was unable to locate it. Günter I think all this is becoming unreasonably complicated. I wonder if I had not better wait for LyX 1.6. Possibly the shortcut editor will help me fix this... -- Daniel Clément
Re: keyboard question
On 26.06.08, Daniel Clément wrote: On Wednesday 25 June 2008 à 17:56 +0200, G. Milde wrote: On 25.06.08, Daniel Clément wrote: On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: I am quite sure that combo-key ´ c is inserted by LyX as unicode char ć (cacute), at least it is here. Also my text editor inserts this key combo as one character. (A combining char is inserted *behind* the accented char and recognizable e.g. when moving with cursor keys or deleting a word char by char. Try e.g. with M-x accent cedilla a: you will see an a with cedilla but this is composed of two characters: a and combining-char-cedilla.) ... The bind file. It uses a special naming for non-ASCII input. Looking at the bind files that ship with LyX helps, $LYXDIR/bind/latinkeys.bind contains the definition: \bind cacute self-insert ... It did not work. Nor does it work here. Dear LyX gurus: why does LyX ignore: \bind cacute unicode-insert 0x00e7 while e.g. \bind M-C-comma unicode-insert 0x00e7 # insert a ç (c with cedilla) works? Alternatives that work here are 2. \bind Meta , accent-cedilla I assume \bind M-,? --tried them both ... Well, it is \bind M-comma accent-cedilla I think all this is becoming unreasonably complicated. I wonder if I had not better wait for LyX 1.6. Possibly the shortcut editor will help me fix this... From my first impression, no. It does not support remapping of characters to insert. Günter PS: Then I noticed that this file eventually calls latinkeys.bind. So I tried to edit it directly, replacing the suggested line with ... You can override a keybinding if you give a new definition after the input of a standard file. (Only exception are Shift-independent bindings with ~S where the first definition wins over other ~S definitions but is overwritten by either S or non-shifted defs.) (It's the modified sciword.bind file that I use; it contains the same shortcuts as in my former SciWord.) I recommend loading the default sciword.bind in the custom bind file, e.g. # Before defining your own bindings, select one of the available default # binding sets. These are resource files (like this one) that define a # large set of (keyboard) bindings. These files live in the /bind directory of # the LyX system directory and have the .bind suffix. # # The \bind_file command looks in the LyX bind directory for a file # of the given name, so a full path should not be given. # # Currently, you can choose from the following flavors:: \bind_file cua.bind # KDE-, Windows-, Mac- and Motif-like bindings #\bind_file emacs.bind # for Emacs-like bindings. # ... # we also would like to incorporate some additional menu shortcuts # \bind_file menus.bind # English menu shortcut additions \bind_file de_menus.bind# German version
Re: keyboard question
At least something that works! On Tuesday 26 June 2008 à 09:36 +0200, G. Milde wrote: [...] Dear LyX gurus: why does LyX ignore: \bind cacute unicode-insert 0x00e7 while e.g. \bind M-C-comma unicode-insert 0x00e7 # insert a ç (c with cedilla) works? YES it does! Thanks! [...] You can override a keybinding if you give a new definition after the input of a standard file. (Only exception are Shift-independent bindings with ~S where the first definition wins over other ~S definitions but is overwritten by either S or non-shifted defs.) Interesting, but that does not account for my previous failed attempts. (It's the modified sciword.bind file that I use; it contains the same shortcuts as in my former SciWord.) I recommend loading the default sciword.bind in the custom bind file, I could have done this, but I had to actually modify some definitions in sciword.bind. (It appears to match a rather old version o SciWord...) I have more or less concluded that: once a key is dead in the keyboard setup (in the OS I mean), it cannot be used effectively in a \bind sequence. IMHO the kmap file would have been the most appropriate place to deal with this, but I was unable to get it working. However, I'm quite pleased with the workaround that you gave me. Thanks again. -- Daniel Clément
Re: keyboard question
Hi Daniel, I fear your solution is too general for my case: wouldn't it interfere with my keyboard settings in other programs? I wouldn't think so. You don't have to use this 'feature' in other contexts. If you heavily use the caps lock key then the situation is different. But in that case you can redefine any other key to become the compose key. Under Linux there is a nice little program 'xev' which gives you the key code for all keys. I point out that I am perfectly satisfied with my US int'l setup in almost every software, command line included. Since LyX is the only major program I'm having this (however little) trouble with, I was in search of a LyX-specific solution. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. I don't remeber exactly where, it's several years tackled with these problems. HTH Hellmut -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
Günter, The more I try, the less I understand... Nothing seems to work as it should! See the reports of my attempts below On Wednesday 25 June 2008 à 17:56 +0200, G. Milde wrote: On 25.06.08, Daniel Clément wrote: On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Not quite sure how to check this but I'd bet on single character... OK. Just let's assume this. Maybe it was not the case after all [...] Maybe LyX does not map it to ç because it does not see the defined char. Do you mean: in the kmap file, or the bind file? If the latter, it has to be something like that, because I do have some personal keybindings that work. The bind file. It uses a special naming for non-ASCII input. Looking at the bind files that ship with LyX helps: $LYXDIR/bind/latinkeys.bind contains the definition: \bind cacuteself-insert which you should change to unicode-insert ... (as proposed earlier in this thread). I tried this in my /home/daniel/.lyx/bind/swpperso.bind file. (It's the modified sciword.bind file that I use; it contains the same shortcuts as in my former SciWord.) It did not work. Then I noticed that this file eventually calls latinkeys.bind. So I tried to edit it directly, replacing the suggested line with \bind cacute unicode-insert 0x00e7 This, to my great disappointment, did not work either (always acute-accented c). Hope this helps. BTW: Alternatives that work here are 1. Combining-Key + Komma followed by c. (in my setup, X11 translates this to ç, Combining-Key is the Windows Key) 2. \bind Meta , accent-cedilla I assume \bind M-,? --tried them both however. and then Alt-, c. I tried this too, and it did not act as I wanted: M-, enters math mode!... There mus be a conflict with another binding, but I was unable to locate it. Günter I think all this is becoming unreasonably complicated. I wonder if I had not better wait for LyX 1.6. Possibly the shortcut editor will help me fix this... -- Daniel Clément
Re: keyboard question
On 26.06.08, Daniel Clément wrote: On Wednesday 25 June 2008 à 17:56 +0200, G. Milde wrote: On 25.06.08, Daniel Clément wrote: On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: I am quite sure that combo-key ´ c is inserted by LyX as unicode char ć (cacute), at least it is here. Also my text editor inserts this key combo as one character. (A combining char is inserted *behind* the accented char and recognizable e.g. when moving with cursor keys or deleting a word char by char. Try e.g. with M-x accent cedilla a: you will see an a with cedilla but this is composed of two characters: a and combining-char-cedilla.) ... The bind file. It uses a special naming for non-ASCII input. Looking at the bind files that ship with LyX helps, $LYXDIR/bind/latinkeys.bind contains the definition: \bind cacute self-insert ... It did not work. Nor does it work here. Dear LyX gurus: why does LyX ignore: \bind cacute unicode-insert 0x00e7 while e.g. \bind M-C-comma unicode-insert 0x00e7 # insert a ç (c with cedilla) works? Alternatives that work here are 2. \bind Meta , accent-cedilla I assume \bind M-,? --tried them both ... Well, it is \bind M-comma accent-cedilla I think all this is becoming unreasonably complicated. I wonder if I had not better wait for LyX 1.6. Possibly the shortcut editor will help me fix this... From my first impression, no. It does not support remapping of characters to insert. Günter PS: Then I noticed that this file eventually calls latinkeys.bind. So I tried to edit it directly, replacing the suggested line with ... You can override a keybinding if you give a new definition after the input of a standard file. (Only exception are Shift-independent bindings with ~S where the first definition wins over other ~S definitions but is overwritten by either S or non-shifted defs.) (It's the modified sciword.bind file that I use; it contains the same shortcuts as in my former SciWord.) I recommend loading the default sciword.bind in the custom bind file, e.g. # Before defining your own bindings, select one of the available default # binding sets. These are resource files (like this one) that define a # large set of (keyboard) bindings. These files live in the /bind directory of # the LyX system directory and have the .bind suffix. # # The \bind_file command looks in the LyX bind directory for a file # of the given name, so a full path should not be given. # # Currently, you can choose from the following flavors:: \bind_file cua.bind # KDE-, Windows-, Mac- and Motif-like bindings #\bind_file emacs.bind # for Emacs-like bindings. # ... # we also would like to incorporate some additional menu shortcuts # \bind_file menus.bind # English menu shortcut additions \bind_file de_menus.bind# German version
Re: keyboard question
At least something that works! On Tuesday 26 June 2008 à 09:36 +0200, G. Milde wrote: [...] Dear LyX gurus: why does LyX ignore: \bind cacute unicode-insert 0x00e7 while e.g. \bind M-C-comma unicode-insert 0x00e7 # insert a ç (c with cedilla) works? YES it does! Thanks! [...] You can override a keybinding if you give a new definition after the input of a standard file. (Only exception are Shift-independent bindings with ~S where the first definition wins over other ~S definitions but is overwritten by either S or non-shifted defs.) Interesting, but that does not account for my previous failed attempts. (It's the modified sciword.bind file that I use; it contains the same shortcuts as in my former SciWord.) I recommend loading the default sciword.bind in the custom bind file, I could have done this, but I had to actually modify some definitions in sciword.bind. (It appears to match a rather old version o SciWord...) I have more or less concluded that: once a key is dead in the keyboard setup (in the OS I mean), it cannot be used effectively in a \bind sequence. IMHO the kmap file would have been the most appropriate place to deal with this, but I was unable to get it working. However, I'm quite pleased with the workaround that you gave me. Thanks again. -- Daniel Clément
Re: keyboard question
Hi Daniel, I fear your solution is too general for my case: wouldn't it interfere with my keyboard settings in other programs? I wouldn't think so. You don't have to use this 'feature' in other contexts. If you heavily use the caps lock key then the situation is different. But in that case you can redefine any other key to become the compose key. Under Linux there is a nice little program 'xev' which gives you the key code for all keys. I point out that I am perfectly satisfied with my US int'l setup in almost every software, command line included. Since LyX is the only major program I'm having this (however little) trouble with, I was in search of a LyX-specific solution. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. I don't remeber exactly where, it's several years tackled with these problems. HTH Hellmut -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
Günter, The more I try, the less I understand... Nothing seems to work as it should! See the reports of my attempts below On Wednesday 25 June 2008 à 17:56 +0200, G. Milde wrote: > On 25.06.08, Daniel Clément wrote: > > On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: > > > > Could you find out whether the character inserted via dead-´ + c is > > > *one* character (c with accent) or > > > *two* characters (c + combining acute acctent) > > > Not quite sure how to check this but I'd bet on "single character"... > > OK. Just let's assume this. > Maybe it was not the case after all [...] > > > > Maybe LyX does not map it to ç because it does not "see" the defined char. > > > Do you mean: in the kmap file, or the bind file? If the latter, it has > > to be something like that, because I do have some personal keybindings > > that work. > > The bind file. It uses a special naming for non-ASCII input. Looking at the > bind files that ship with LyX helps: > > $LYXDIR/bind/latinkeys.bind contains the definition: > > \bind "cacute""self-insert" > > which you should change to "unicode-insert ..." (as proposed earlier in this > thread). I tried this in my /home/daniel/.lyx/bind/swpperso.bind file. (It's the modified sciword.bind file that I use; it contains the same shortcuts as in my former SciWord.) It did not work. Then I noticed that this file eventually calls latinkeys.bind. So I tried to edit it directly, replacing the suggested line with \bind "cacute" "unicode-insert 0x00e7" This, to my great disappointment, did not work either (always acute-accented c). > > Hope this helps. > > > BTW: Alternatives that work here are > > 1. "Combining-Key + Komma" followed by c. (in my setup, X11 translates > this to ç, Combining-Key is the Windows Key) > > 2. \bind "Meta ," "accent-cedilla" I assume \bind "M-,"? --tried them both however. > and then Alt-, c. I tried this too, and it did not act as I wanted: M-, enters math mode!... There mus be a conflict with another binding, but I was unable to locate it. > > Günter I think all this is becoming unreasonably complicated. I wonder if I had not better wait for LyX 1.6. Possibly the shortcut editor will help me fix this... -- Daniel Clément
Re: keyboard question
On 26.06.08, Daniel Clément wrote: > On Wednesday 25 June 2008 à 17:56 +0200, G. Milde wrote: > > On 25.06.08, Daniel Clément wrote: > > > On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: I am quite sure that "combo-key ´ c" is inserted by LyX as unicode char ć (cacute), at least it is here. Also my text editor inserts this key combo as one character. (A combining char is inserted *behind* the accented char and recognizable e.g. when moving with cursor keys or deleting a word char by char. Try e.g. with "M-x accent cedilla a": you will see an a with cedilla but this is composed of two characters: a and combining-char-cedilla.) ... > > The bind file. It uses a special naming for non-ASCII input. Looking > > at the bind files that ship with LyX helps, > > $LYXDIR/bind/latinkeys.bind contains the definition: > > \bind "cacute" "self-insert" ... > It did not work. Nor does it work here. Dear LyX gurus: why does LyX ignore: \bind "cacute" "unicode-insert 0x00e7" while e.g. \bind "M-C-comma" "unicode-insert 0x00e7" # insert a ç (c with cedilla) works? > > Alternatives that work here are > > > > 2. \bind "Meta ," "accent-cedilla" > I assume \bind "M-,"? --tried them both ... Well, it is \bind "M-comma" "accent-cedilla" > I think all this is becoming unreasonably complicated. I wonder if I had > not better wait for LyX 1.6. Possibly the shortcut editor will help me > fix this... >From my first impression, no. It does not support remapping of characters to insert. Günter PS: > Then I noticed that this file eventually calls latinkeys.bind. So I > tried to edit it directly, replacing the suggested line with ... You can override a keybinding if you give a new definition after the input of a "standard" file. (Only exception are Shift-independent bindings with ~S where the first definition "wins" over other ~S definitions but is overwritten by either S or non-shifted defs.) > (It's the modified sciword.bind file that I use; it contains the same > shortcuts as in my former SciWord.) I recommend loading the default sciword.bind in the custom bind file, e.g. # Before defining your own bindings, select one of the available default # binding sets. These are resource files (like this one) that define a # large set of (keyboard) bindings. These files live in the /bind directory of # the LyX system directory and have the .bind suffix. # # The \bind_file command looks in the LyX bind directory for a file # of the given name, so a full path should not be given. # # Currently, you can choose from the following flavors:: \bind_file cua.bind # KDE-, Windows-, Mac- and Motif-like bindings #\bind_file emacs.bind # for Emacs-like bindings. # ... # we also would like to incorporate some additional menu shortcuts # \bind_file menus.bind # English menu shortcut additions \bind_file de_menus.bind# German version
Re: keyboard question
At least something that works! On Tuesday 26 June 2008 à 09:36 +0200, G. Milde wrote: [...] > > Dear LyX gurus: why does LyX ignore: > > \bind "cacute" "unicode-insert 0x00e7" > > while e.g. > > \bind "M-C-comma" "unicode-insert 0x00e7" # insert a ç (c with cedilla) > > works? YES it does! Thanks! [...] > You can override a keybinding if you give a new definition after the > input of a "standard" file. (Only exception are Shift-independent > bindings with ~S where the first definition "wins" over other ~S > definitions but is overwritten by either S or non-shifted defs.) Interesting, but that does not account for my previous failed attempts. > > (It's the modified sciword.bind file that I use; it contains the same > > shortcuts as in my former SciWord.) > > I recommend loading the default sciword.bind in the custom bind file, I could have done this, but I had to actually modify some definitions in sciword.bind. (It appears to match a rather old version o SciWord...) I have more or less concluded that: once a key is "dead" in the keyboard setup (in the OS I mean), it cannot be used effectively in a \bind sequence. IMHO the kmap file would have been the most appropriate place to deal with this, but I was unable to get it working. However, I'm quite pleased with the workaround that you gave me. Thanks again. -- Daniel Clément
Re: keyboard question
Hi Daniel, I fear your solution is too general for my case: wouldn't it interfere with my keyboard settings in other programs? I wouldn't think so. You don't have to use this 'feature' in other contexts. If you heavily use the caps lock key then the situation is different. But in that case you can redefine any other key to become the compose key. Under Linux there is a nice little program 'xev' which gives you the key code for all keys. I point out that I am perfectly satisfied with my "US int'l" setup in almost every software, command line included. Since LyX is the only major program I'm having this (however little) trouble with, I was in search of a LyX-specific solution. You could try to define your personal bind file in '$HOME/.lyx/bind/...' You'll find info on global and local bind files somewhere in the (more advanced ;-) LyX documentation. I don't remeber exactly where, it's several years tackled with these problems. HTH Hellmut -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
[sorry if double post, previous one did not work] On Tuesday 24 June 2008 18:31 +0200, Abdelrazak Younes wrote: [...] Maybe try this: \bind 'c unicode-insert 0x00e7 Abdel. It looked promising, but it did not work (still gives accented c). I don't know why \kxmod ' c ç in the kmap file does not work. Isn't exactly what sect. 4.4.1 of Customization says? Also, I tried a normal US keyboard setting (without dead keys): it did not change anything. So the dead keys are not the problem. It looks like some other setting has precedence over the ones made in bind or kmap files... -- Daniel Clément
Re: keyboard question
On 25.06.08, Daniel Clément wrote: [sorry if double post, previous one did not work] On Tuesday 24 June 2008 18:31 +0200, Abdelrazak Younes wrote: [...] Maybe try this: \bind 'c unicode-insert 0x00e7 It looked promising, but it did not work (still gives accented c). ... It looks like some other setting has precedence over the ones made in bind or kmap files... Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Both look similar at screen but are different representations. Deleting a two character combination sometimes(?) leaves the accent or the letter. The M-x accent-* functions insert two character combinations. Maybe LyX does not map it to ç because it does not see the defined char. Günter
Re: keyboard question
Hi Daniel, my system is gentoo linux, KDE-3.5, LyX 1.5.3 1.5.5 1.6svn (a few weeks old I have the problem that I sometimes wnat to have ç (in french texts) and also å (in swedish texts). The solution I found already several years ago is to have a bash start script in the Autostart folder, in which I define: xmodmap -e clear Lock xmodmap -e keycode 66 = Multi_key Since I nearly never use the caps lock key I redefine it in this way as 'compose' key. There are files like /usr/share/keymaps/include/compose.latin1 which show you the transformations of compose+key+key to different symbols. For the above examples I have to type caps lock 'c' ',' and caps lock 'a' 'a' one after the other. This works inside LyX, vim and also on the command line. HTH Hellmut Also, I tried a normal US keyboard setting (without dead keys): it did not change anything. So the dead keys are not the problem. BTW My LOCALE is de as well as my keyboard setting -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
Günter, On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: [...] Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Not quite sure how to check this but I'd bet on single character... Both look similar at screen but are different representations. Deleting a two character combination sometimes(?) leaves the accent or the letter. The M-x accent-* functions insert two character combinations. ... because this latter behavior you describe is what I get (erase accented c, accent remains) when I specify american.kmap while trying to tweak it. By default (i.e. no kmap file selected) I can erase the accented c at once. (BTW I couldn't paste the character in question from LyX into this message.) Maybe LyX does not map it to ç because it does not see the defined char. Do you mean: in the kmap file, or the bind file? If the latter, it has to be something like that, because I do have some personal keybindings that work. Günter -- Daniel Clément
Re: keyboard question
On 25.06.08, Daniel Clément wrote: On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Not quite sure how to check this but I'd bet on single character... OK. Just let's assume this. (BTW I couldn't paste the character in question from LyX into this message.) Maybe you are not using a utf-8 enabled mailer. Maybe LyX does not map it to ç because it does not see the defined char. Do you mean: in the kmap file, or the bind file? If the latter, it has to be something like that, because I do have some personal keybindings that work. The bind file. It uses a special naming for non-ASCII input. Looking at the bind files that ship with LyX helps: $LYXDIR/bind/latinkeys.bind contains the definition: \bind cacute self-insert which you should change to unicode-insert ... (as proposed earlier in this thread). Hope this helps. BTW: Alternatives that work here are 1. Combining-Key + Komma followed by c. (in my setup, X11 translates this to ç, Combining-Key is the Windows Key) 2. \bind Meta , accent-cedilla and then Alt-, c. Günter
Re: keyboard question
[sorry if double post, previous one did not work] On Tuesday 24 June 2008 18:31 +0200, Abdelrazak Younes wrote: [...] Maybe try this: \bind 'c unicode-insert 0x00e7 Abdel. It looked promising, but it did not work (still gives accented c). I don't know why \kxmod ' c ç in the kmap file does not work. Isn't exactly what sect. 4.4.1 of Customization says? Also, I tried a normal US keyboard setting (without dead keys): it did not change anything. So the dead keys are not the problem. It looks like some other setting has precedence over the ones made in bind or kmap files... -- Daniel Clément
Re: keyboard question
On 25.06.08, Daniel Clément wrote: [sorry if double post, previous one did not work] On Tuesday 24 June 2008 18:31 +0200, Abdelrazak Younes wrote: [...] Maybe try this: \bind 'c unicode-insert 0x00e7 It looked promising, but it did not work (still gives accented c). ... It looks like some other setting has precedence over the ones made in bind or kmap files... Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Both look similar at screen but are different representations. Deleting a two character combination sometimes(?) leaves the accent or the letter. The M-x accent-* functions insert two character combinations. Maybe LyX does not map it to ç because it does not see the defined char. Günter
Re: keyboard question
Hi Daniel, my system is gentoo linux, KDE-3.5, LyX 1.5.3 1.5.5 1.6svn (a few weeks old I have the problem that I sometimes wnat to have ç (in french texts) and also å (in swedish texts). The solution I found already several years ago is to have a bash start script in the Autostart folder, in which I define: xmodmap -e clear Lock xmodmap -e keycode 66 = Multi_key Since I nearly never use the caps lock key I redefine it in this way as 'compose' key. There are files like /usr/share/keymaps/include/compose.latin1 which show you the transformations of compose+key+key to different symbols. For the above examples I have to type caps lock 'c' ',' and caps lock 'a' 'a' one after the other. This works inside LyX, vim and also on the command line. HTH Hellmut Also, I tried a normal US keyboard setting (without dead keys): it did not change anything. So the dead keys are not the problem. BTW My LOCALE is de as well as my keyboard setting -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
Günter, On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: [...] Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Not quite sure how to check this but I'd bet on single character... Both look similar at screen but are different representations. Deleting a two character combination sometimes(?) leaves the accent or the letter. The M-x accent-* functions insert two character combinations. ... because this latter behavior you describe is what I get (erase accented c, accent remains) when I specify american.kmap while trying to tweak it. By default (i.e. no kmap file selected) I can erase the accented c at once. (BTW I couldn't paste the character in question from LyX into this message.) Maybe LyX does not map it to ç because it does not see the defined char. Do you mean: in the kmap file, or the bind file? If the latter, it has to be something like that, because I do have some personal keybindings that work. Günter -- Daniel Clément
Re: keyboard question
On 25.06.08, Daniel Clément wrote: On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Not quite sure how to check this but I'd bet on single character... OK. Just let's assume this. (BTW I couldn't paste the character in question from LyX into this message.) Maybe you are not using a utf-8 enabled mailer. Maybe LyX does not map it to ç because it does not see the defined char. Do you mean: in the kmap file, or the bind file? If the latter, it has to be something like that, because I do have some personal keybindings that work. The bind file. It uses a special naming for non-ASCII input. Looking at the bind files that ship with LyX helps: $LYXDIR/bind/latinkeys.bind contains the definition: \bind cacute self-insert which you should change to unicode-insert ... (as proposed earlier in this thread). Hope this helps. BTW: Alternatives that work here are 1. Combining-Key + Komma followed by c. (in my setup, X11 translates this to ç, Combining-Key is the Windows Key) 2. \bind Meta , accent-cedilla and then Alt-, c. Günter
Re: keyboard question
[sorry if double post, previous one did not work] On Tuesday 24 June 2008 18:31 +0200, Abdelrazak Younes wrote: [...] > Maybe try this: > > \bind "'c" "unicode-insert 0x00e7" > > Abdel. > It looked promising, but it did not work (still gives accented c). I don't know why \kxmod ' c ç in the kmap file does not work. Isn't exactly what sect. 4.4.1 of "Customization" says? Also, I tried a "normal" US keyboard setting (without dead keys): it did not change anything. So the dead keys are not the problem. It looks like some other setting has precedence over the ones made in bind or kmap files... -- Daniel Clément
Re: keyboard question
On 25.06.08, Daniel Clément wrote: > [sorry if double post, previous one did not work] > On Tuesday 24 June 2008 18:31 +0200, Abdelrazak Younes wrote: > [...] > > Maybe try this: > > \bind "'c" "unicode-insert 0x00e7" > It looked promising, but it did not work (still gives accented c). ... > It looks like some other setting has precedence over the ones made in > bind or kmap files... Could you find out whether the character inserted via dead-´ + c is *one* character (c with accent) or *two* characters (c + combining acute acctent) Both look similar at screen but are different representations. Deleting a two character combination sometimes(?) leaves the accent or the letter. The M-x accent-* functions insert two character combinations. Maybe LyX does not map it to ç because it does not "see" the defined char. Günter
Re: keyboard question
Hi Daniel, my system is gentoo linux, KDE-3.5, LyX 1.5.3 1.5.5 1.6svn (a few weeks old I have the problem that I sometimes wnat to have ç (in french texts) and also å (in swedish texts). The solution I found already several years ago is to have a bash start script in the Autostart folder, in which I define: xmodmap -e "clear Lock" xmodmap -e "keycode 66 = Multi_key" Since I nearly never use the caps lock key I redefine it in this way as 'compose' key. There are files like /usr/share/keymaps/include/compose.latin1 which show you the transformations of ++ to different symbols. For the above examples I have to type 'c' ',' and 'a' 'a' one after the other. This works inside LyX, vim and also on the command line. HTH Hellmut Also, I tried a "normal" US keyboard setting (without dead keys): it did not change anything. So the dead keys are not the problem. BTW My LOCALE is de as well as my keyboard setting -- Dr. Hellmut Weber [EMAIL PROTECTED] Degenfeldstraße 2 tel +49-89-3081172 D-80803 München-Schwabing mobil +49-172-8450321 please: No DOCs, no PPTs. why: tinyurl.com/cbgq
Re: keyboard question
Günter, On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: [...] > Could you find out whether the character inserted via dead-´ + c is > *one* character (c with accent) or > *two* characters (c + combining acute acctent) Not quite sure how to check this but I'd bet on "single character"... > > Both look similar at screen but are different representations. > Deleting a two character combination sometimes(?) leaves the accent or > the letter. The M-x accent-* functions insert two character combinations. ... because this latter behavior you describe is what I get (erase accented c, accent remains) when I specify "american.kmap" while trying to tweak it. By default (i.e. no kmap file selected) I can erase the accented c at once. (BTW I couldn't paste the character in question from LyX into this message.) > > Maybe LyX does not map it to ç because it does not "see" the defined char. Do you mean: in the kmap file, or the bind file? If the latter, it has to be something like that, because I do have some personal keybindings that work. > > Günter -- Daniel Clément
Re: keyboard question
On 25.06.08, Daniel Clément wrote: > On Wednesday 25 june 2008 à 12:19 +0200, G. Milde wrote: > > Could you find out whether the character inserted via dead-´ + c is > > *one* character (c with accent) or > > *two* characters (c + combining acute acctent) > Not quite sure how to check this but I'd bet on "single character"... OK. Just let's assume this. > (BTW I couldn't paste the character in question from LyX into this > message.) Maybe you are not using a utf-8 enabled mailer. > > Maybe LyX does not map it to ç because it does not "see" the defined char. > Do you mean: in the kmap file, or the bind file? If the latter, it has > to be something like that, because I do have some personal keybindings > that work. The bind file. It uses a special naming for non-ASCII input. Looking at the bind files that ship with LyX helps: $LYXDIR/bind/latinkeys.bind contains the definition: \bind "cacute" "self-insert" which you should change to "unicode-insert ..." (as proposed earlier in this thread). Hope this helps. BTW: Alternatives that work here are 1. "Combining-Key + Komma" followed by c. (in my setup, X11 translates this to ç, Combining-Key is the Windows Key) 2. \bind "Meta ," "accent-cedilla" and then Alt-, c. Günter
keyboard question
Hello, I use a US int'l keyboard --though I am French-- for more convenient access to brackets, parentheses... in scientific software. I have the dead keys setup, getting accented characters by typing the accent, then the character. However, the cedilla-c: ç is obtained by acute accent + c. This is the case in almost every program. But LyX gives me an accented c! How could I teach LyX to type the cedilla-c instead? I tried to tweak a kmap file (details below) but I did not succeed so far. BTW, OS is Linux Ubuntu. Thanks, -- Daniel Clément PS Here is what I tried: in american.kmap I put \kmod ' acute aeiouAEIOU # \kmod , cedilla native \kxmod ' c ç No luck. What am I doing wrong?
Re: keyboard question
On 24.06.08, Daniel CLEMENT wrote: I use a US int'l keyboard I have the dead keys setup, getting accented characters by typing the accent, then the character. However, the cedilla-c: ç is obtained by acute accent + c. This is the case in almost every program. But LyX gives me an accented c! I suppose that it is converted to character 'ć' (263, 0x107) 0107LATIN SMALL LETTER C WITH ACUTE by the OS and inserted as-is by LyX. How could I teach LyX to type the cedilla-c instead? I tried to tweak a kmap file (details below) but I did not succeed so far. I suppose you can do without a kmap file and use a bind file to bind ć to ç but I do not know about the required syntax. Günter
Re: keyboard question
On Tuesday 24 June 2008 15:13 +0200, G. Milde wrote: On 24.06.08, Daniel CLEMENT wrote: I use a US int'l keyboard I have the dead keys setup, getting accented characters by typing the accent, then the character. However, the cedilla-c: ç is obtained by acute accent + c. This is the case in almost every program. But LyX gives me an accented c! I suppose that it is converted to character 'ć' (263, 0x107) 0107 LATIN SMALL LETTER C WITH ACUTE by the OS and inserted as-is by LyX. Sure, but why doesn't the OS convert to ç like in most other programs? LyX must have something to do with it. How could I teach LyX to type the cedilla-c instead? I tried to tweak a kmap file (details below) but I did not succeed so far. I suppose you can do without a kmap file and use a bind file to bind ć to ç but I do not know about the required syntax. Günter Well, since the ć does not appear in any bind file that I know, I thought a kmap file was a more appropriate. Anyhow, I tried \bind 'c ç and \bind ç ç ... neither worked (still getting ć). I miss the correct syntax! -- Daniel Clément
Re: keyboard question
Daniel CLEMENT wrote: ... neither worked (still getting ć). I miss the correct syntax! Maybe try this: \bind 'c unicode-insert 0x00e7 Abdel.
keyboard question
Hello, I use a US int'l keyboard --though I am French-- for more convenient access to brackets, parentheses... in scientific software. I have the dead keys setup, getting accented characters by typing the accent, then the character. However, the cedilla-c: ç is obtained by acute accent + c. This is the case in almost every program. But LyX gives me an accented c! How could I teach LyX to type the cedilla-c instead? I tried to tweak a kmap file (details below) but I did not succeed so far. BTW, OS is Linux Ubuntu. Thanks, -- Daniel Clément PS Here is what I tried: in american.kmap I put \kmod ' acute aeiouAEIOU # \kmod , cedilla native \kxmod ' c ç No luck. What am I doing wrong?
Re: keyboard question
On 24.06.08, Daniel CLEMENT wrote: I use a US int'l keyboard I have the dead keys setup, getting accented characters by typing the accent, then the character. However, the cedilla-c: ç is obtained by acute accent + c. This is the case in almost every program. But LyX gives me an accented c! I suppose that it is converted to character 'ć' (263, 0x107) 0107LATIN SMALL LETTER C WITH ACUTE by the OS and inserted as-is by LyX. How could I teach LyX to type the cedilla-c instead? I tried to tweak a kmap file (details below) but I did not succeed so far. I suppose you can do without a kmap file and use a bind file to bind ć to ç but I do not know about the required syntax. Günter
Re: keyboard question
On Tuesday 24 June 2008 15:13 +0200, G. Milde wrote: On 24.06.08, Daniel CLEMENT wrote: I use a US int'l keyboard I have the dead keys setup, getting accented characters by typing the accent, then the character. However, the cedilla-c: ç is obtained by acute accent + c. This is the case in almost every program. But LyX gives me an accented c! I suppose that it is converted to character 'ć' (263, 0x107) 0107 LATIN SMALL LETTER C WITH ACUTE by the OS and inserted as-is by LyX. Sure, but why doesn't the OS convert to ç like in most other programs? LyX must have something to do with it. How could I teach LyX to type the cedilla-c instead? I tried to tweak a kmap file (details below) but I did not succeed so far. I suppose you can do without a kmap file and use a bind file to bind ć to ç but I do not know about the required syntax. Günter Well, since the ć does not appear in any bind file that I know, I thought a kmap file was a more appropriate. Anyhow, I tried \bind 'c ç and \bind ç ç ... neither worked (still getting ć). I miss the correct syntax! -- Daniel Clément
Re: keyboard question
Daniel CLEMENT wrote: ... neither worked (still getting ć). I miss the correct syntax! Maybe try this: \bind 'c unicode-insert 0x00e7 Abdel.
keyboard question
Hello, I use a US int'l keyboard --though I am French-- for more convenient access to brackets, parentheses... in scientific software. I have the "dead keys" setup, getting accented characters by typing the accent, then the character. However, the cedilla-c: ç is obtained by "acute accent + c". This is the case in almost every program. But LyX gives me an accented c! How could I teach LyX to type the cedilla-c instead? I tried to tweak a kmap file (details below) but I did not succeed so far. BTW, OS is Linux Ubuntu. Thanks, -- Daniel Clément PS Here is what I tried: in american.kmap I put \kmod ' acute aeiouAEIOU # \kmod "," cedilla native \kxmod ' c ç No luck. What am I doing wrong?
Re: keyboard question
On 24.06.08, Daniel CLEMENT wrote: > I use a US int'l keyboard I have the "dead keys" setup, getting > accented characters by typing the accent, then the character. > However, the cedilla-c: ç is obtained by "acute accent + c". This is the > case in almost every program. But LyX gives me an accented c! I suppose that it is converted to character 'ć' (263, 0x107) 0107LATIN SMALL LETTER C WITH ACUTE by the OS and inserted as-is by LyX. > How could I teach LyX to type the cedilla-c instead? I tried to tweak a > kmap file (details below) but I did not succeed so far. I suppose you can do without a kmap file and use a bind file to bind ć to ç but I do not know about the required syntax. Günter
Re: keyboard question
On Tuesday 24 June 2008 15:13 +0200, G. Milde wrote: > On 24.06.08, Daniel CLEMENT wrote: > > I use a US int'l keyboard I have the "dead keys" setup, getting > > accented characters by typing the accent, then the character. > > > However, the cedilla-c: ç is obtained by "acute accent + c". This is the > > case in almost every program. But LyX gives me an accented c! > > I suppose that it is converted to character 'ć' (263, 0x107) > 0107 LATIN SMALL LETTER C WITH ACUTE > by the OS and inserted as-is by LyX. Sure, but why doesn't the OS convert to ç like in most other programs? LyX must have something to do with it. > > How could I teach LyX to type the cedilla-c instead? I tried to tweak a > > kmap file (details below) but I did not succeed so far. > > I suppose you can do without a kmap file and use a bind file to > bind ć to ç but I do not know about the required syntax. > > Günter Well, since the ć does not appear in any bind file that I know, I thought a kmap file was a more appropriate. Anyhow, I tried \bind "'c" "ç" and \bind "ç" "ç" ... neither worked (still getting ć). I miss the correct syntax! -- Daniel Clément
Re: keyboard question
Daniel CLEMENT wrote: ... neither worked (still getting ć). I miss the correct syntax! Maybe try this: \bind "'c" "unicode-insert 0x00e7" Abdel.
Keyboard question: i with two dots?
Hi,
sorry for the silly question, but perhaps someone knows an easy
answer. I've been searching the web, but so far to no avail.
How do you call the i with two dots, and how can I enter in into
LyX?
In LaTeX, it would be \{\i} (in case that helps...) ;-)
Of course, I could use ERT in LyX, but it would be more fun if i
could convince my XWindows to do it directly via keyboard...
Many thanks,
Andreas
--
Dr. Andreas Busch
Department of Politics and [EMAIL PROTECTED]
International Relations Web: http://users.ox.ac.uk/~busch
University of OxfordTel. (+44)-1865-278 704
3 George Street MewsFax. (+44)-1865-278 725
Oxford OX1 2AA, United Kingdom
Re: Keyboard question: i with two dots?
On Mon, Dec 16, 2002 at 05:49:22PM +, Andreas Busch wrote:
In LaTeX, it would be \{\i} (in case that helps...) ;-)
Of course, I could use ERT in LyX, but it would be more fun if i
could convince my XWindows to do it directly via keyboard...
Compose-i- works here.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: Keyboard question: i with two dots?
On Mon, 16 Dec 2002 19:15:37 +0100, Andre Poenitz [EMAIL PROTECTED] wrote:
On Mon, Dec 16, 2002 at 05:49:22PM +, Andreas Busch wrote:
In LaTeX, it would be \{\i} (in case that helps...) ;-)
Of course, I could use ERT in LyX, but it would be more fun if i
could convince my XWindows to do it directly via keyboard...
Compose-i- works here.
Andre'
Many thanks! I knew there had to be a simple solution...
Andreas
--
Dr. Andreas Busch
Department of Politics and [EMAIL PROTECTED]
International Relations Web: http://users.ox.ac.uk/~busch
University of OxfordTel. (+44)-1865-278 704
3 George Street MewsFax. (+44)-1865-278 725
Oxford OX1 2AA, United Kingdom
Keyboard question: i with two dots?
Hi,
sorry for the silly question, but perhaps someone knows an easy
answer. I've been searching the web, but so far to no avail.
How do you call the i with two dots, and how can I enter in into
LyX?
In LaTeX, it would be \{\i} (in case that helps...) ;-)
Of course, I could use ERT in LyX, but it would be more fun if i
could convince my XWindows to do it directly via keyboard...
Many thanks,
Andreas
--
Dr. Andreas Busch
Department of Politics and [EMAIL PROTECTED]
International Relations Web: http://users.ox.ac.uk/~busch
University of OxfordTel. (+44)-1865-278 704
3 George Street MewsFax. (+44)-1865-278 725
Oxford OX1 2AA, United Kingdom
Re: Keyboard question: i with two dots?
On Mon, Dec 16, 2002 at 05:49:22PM +, Andreas Busch wrote:
In LaTeX, it would be \{\i} (in case that helps...) ;-)
Of course, I could use ERT in LyX, but it would be more fun if i
could convince my XWindows to do it directly via keyboard...
Compose-i- works here.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: Keyboard question: i with two dots?
On Mon, 16 Dec 2002 19:15:37 +0100, Andre Poenitz [EMAIL PROTECTED] wrote:
On Mon, Dec 16, 2002 at 05:49:22PM +, Andreas Busch wrote:
In LaTeX, it would be \{\i} (in case that helps...) ;-)
Of course, I could use ERT in LyX, but it would be more fun if i
could convince my XWindows to do it directly via keyboard...
Compose-i- works here.
Andre'
Many thanks! I knew there had to be a simple solution...
Andreas
--
Dr. Andreas Busch
Department of Politics and [EMAIL PROTECTED]
International Relations Web: http://users.ox.ac.uk/~busch
University of OxfordTel. (+44)-1865-278 704
3 George Street MewsFax. (+44)-1865-278 725
Oxford OX1 2AA, United Kingdom
Keyboard question: i with two dots?
Hi,
sorry for the silly question, but perhaps someone knows an easy
answer. I've been searching the web, but so far to no avail.
How do you call the "i" with two dots, and how can I enter in into
LyX?
In LaTeX, it would be \"{\i} (in case that helps...) ;-)
Of course, I could use ERT in LyX, but it would be more fun if i
could convince my XWindows to do it directly via keyboard...
Many thanks,
Andreas
--
Dr. Andreas Busch
Department of Politics and [EMAIL PROTECTED]
International Relations Web: http://users.ox.ac.uk/~busch
University of OxfordTel. (+44)-1865-278 704
3 George Street MewsFax. (+44)-1865-278 725
Oxford OX1 2AA, United Kingdom
Re: Keyboard question: i with two dots?
On Mon, Dec 16, 2002 at 05:49:22PM +, Andreas Busch wrote:
> In LaTeX, it would be \"{\i} (in case that helps...) ;-)
>
> Of course, I could use ERT in LyX, but it would be more fun if i
> could convince my XWindows to do it directly via keyboard...
Compose-i-" works here.
Andre'
--
Those who desire to give up Freedom in order to gain Security,
will not have, nor do they deserve, either one. (T. Jefferson)
Re: Keyboard question: i with two dots?
On Mon, 16 Dec 2002 19:15:37 +0100, Andre Poenitz <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 16, 2002 at 05:49:22PM +, Andreas Busch wrote:
> In LaTeX, it would be \"{\i} (in case that helps...) ;-)
>
> Of course, I could use ERT in LyX, but it would be more fun if i
> could convince my XWindows to do it directly via keyboard...
> Compose-i-" works here.
>
> Andre'
Many thanks! I knew there had to be a simple solution...
Andreas
--
Dr. Andreas Busch
Department of Politics and [EMAIL PROTECTED]
International Relations Web: http://users.ox.ac.uk/~busch
University of OxfordTel. (+44)-1865-278 704
3 George Street MewsFax. (+44)-1865-278 725
Oxford OX1 2AA, United Kingdom
