Re: Dead keys still not working with xforms 0.88
On Mon, Dec 11, 2000 at 11:35:25PM +0100, Lars Gullik Bjønnes wrote: something must have changed... do others also see this problem with dead keys and XForms 0.88? Lgb Not directly related I know, but in pre2 (I have not tried the more recent cvs) I am unable to use the numerical pad. I use it to get / and * on a single strokeç I'm using xforms .88 and I hadn't this issue with previous versions, although this did happen for previous 1.1.6cvs. I guess that I should know better and use the key debug level, but I was curious if any one has (had) this particular problem. -- José
Re: Dead keys still not working with xforms 0.88
Jose Abilio Oliveira Matos [EMAIL PROTECTED] writes: | On Mon, Dec 11, 2000 at 11:35:25PM +0100, Lars Gullik Bjønnes wrote: | | something must have changed... do others also see this problem with | dead keys and XForms 0.88? | | Lgb | | Not directly related I know, but in pre2 (I have not tried the more recent | cvs) I am unable to use the numerical pad. I use it to get / and * on a single | strokeç | I'm using xforms .88 and I hadn't this issue with previous versions, | although this did happen for previous 1.1.6cvs. It seems that somehow the keybindings for the numerical pad is not used. Lgb
Re: Spellchecker popup woes
"Allan" == Allan Rae [EMAIL PROTECTED] writes: Allan It does beg the question: Do we need/want document scope Allan options? (Which such a direct link implies) I do not think it will be necessary for the spellchecker. At most, we will need options for each language. JMarc
Re: Problems with viewing figures with dvi on 1.1.6pre
On Wed, Dec 06, 2000 at 09:56:14AM +1030, Ben Cazzolato wrote: Guys I'm having problems with the DVI viewer and figures with lyx1.1.6pre2. I think it has to do with the full path being used. The process initated by lyx when viewing DVI is xdvi.bin -name xdvi -paper a4 /home/bscazz/consult/britax/proposal.dvi Same goes for all my figures. Any ideas? The bug is really in xdvi: it requires the current directory to be '/home/bscazz/consult/britax/' in order to view the eps figures, namely if you run xdvi from another directory by using the full path, it will not show the figures. (The xdvi man page says that if the file name does not begin with a slash, then xdvi will look (for eps files) in the directory containing the DVI file, but it doesn't seem to work). I've attached a fix for this problem: before viewing any file, LyX changes the current directory to the directory of this file. PS: Maybe changing the directory should be done only for DVI viewing. Are there other cases of viewers that requires changing of the directory ? patch.gz
Re: Dead keys still not working with xforms 0.88
On Tue, Dec 12, 2000 at 10:19:55AM +0100, Lars Gullik Bjønnes wrote: I began looking at this... but I am not going too look any further until I get a good bug report. Until then I will just put it down as "not-a-bug". Ok, I got the point. Do you see this behaviour? Lgb -- José
Re: Dead keys still not working with xforms 0.88
Jose Abilio Oliveira Matos [EMAIL PROTECTED] writes: | On Tue, Dec 12, 2000 at 10:19:55AM +0100, Lars Gullik Bjønnes wrote: | I began looking at this... but I am not going too look any further | until I get a good bug report. | | Until then I will just put it down as "not-a-bug". | | Ok, I got the point. Do you see this behaviour? Hard to say, since I am using a laptop with weird KP_ keys. But no, I don't belive so since I get the correct keysym. Lgb
Re: Key-binding documentation dilemma
On Mon, Dec 04, 2000 at 01:33:55PM +0100, Lars Gullik Bjønnes wrote: Allan Rae [EMAIL PROTECTED] writes: | On Fri, 1 Dec 2000, Angus Leeming wrote: | | Gentlemen, | | I've written the inset proposed by Jean-Marc. Currently, it's a little | cumbersome to use: [snip I really do not want it done this way... I agree 100%! This is *not* appropriate for documentation... -- John Weiss "Not through coersion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Re: Key-binding documentation dilemma
On Fri, Dec 01, 2000 at 01:39:05PM -0500, Amir Karger wrote: On Fri, Dec 01, 2000 at 05:27:05PM +0900, Miyata Shigeru wrote: Why don't you write a perl script to parse users' lyxrc, preference, ui and bind files, and to update UserGuide.lyx? But then, each user would need a local copy of that file. (I guess you would put it in /tmp?) Seems kind of complicated. It will also consume disk space. No... not a good idea. Plus, it excludes one set of default bindings (e.g. Emacs) in favor of another (e.g. CUA). We need to document *all* bindings, and the place for that is in the Reference Manual. More to come shortly... -- John Weiss "Not through coersion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Re: Key-binding documentation dilemma
On Thu, Nov 30, 2000 at 12:22:12PM -0800, Mike Ressler wrote: Hi, I'm working on updating the keyboard shortcuts in the docs (starting with the User Guide). Given that I'm former editor-in-chief of the LyX Documentation Effort and remain its floating spiritual guide, I think it's time I weigh in on this... 1. Different manuals will need different approaches. It's already been mentioned that the Tutorial should pretty much run with the default bindings, whatever they are. This makes sense; a user reading the Tutorial ain't gonna know or care how to change his keybindings. For the UG and EG, a) Prefer the default bindings; b) However, when deemed necessary, also document the other major binding(s) *in* *addition* *to* the default (either parenthetically or in footnotes; c) Finally, and above all else, do whatever is most appropriate for the flow of the text. This, preservation of readability, takes priority over all else. 2. Full documentation of all bindings belongs in the Reference Manual. Someone else noted that we should document the bindings with the functions, as we currently do. This is by design, folks. If necessary, we can reorganize the RM a bit, junk unused chapters, and move bindings to prominence. An appendix in the UG would, therefore, be redundant. Just refer to the Reference Manual. 3. The RefMan needs a new chapter, one listing keybindings. a) Each major section would be for a particular flavor: (i) Menus and Generic Defaults (ii) CUA-like Default Bindings (iii) Emacs-like Default Bindings b) Within each major section, bindings would be grouped by function/purpose. c) Each group of bindings would be listed by keystroke and sorted lexically. d) Each keybinding would refer to the appropriate reference entry in the chapter documenting lyxfunc's. If no such reference exists, add one. e) For the sake of the printed version, every section/subsection/whatever will make use of "muticols" and be put in at least two columns per page. (Online readers can always use the TOC-menu to navigate.) f) If appropriate, we'll put pagebreaks into this chapter so that users can print out "quick-reference" sheets for the group(s) of bindings they use the most. So say I! -- John Weiss "Not through coersion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Re: Key-binding documentation dilemma
John Weiss [EMAIL PROTECTED] writes: | On Fri, Dec 01, 2000 at 01:39:05PM -0500, Amir Karger wrote: | On Fri, Dec 01, 2000 at 05:27:05PM +0900, Miyata Shigeru wrote: | Why don't you write a perl script to parse users' lyxrc, preference, ui and | bind files, and to update UserGuide.lyx? | | But then, each user would need a local copy of that file. (I guess you would | put it in /tmp?) Seems kind of complicated. | | It will also consume disk space. No... not a good idea. | | Plus, it excludes one set of default bindings (e.g. Emacs) in favor of | another (e.g. CUA). We need to document *all* bindings, and the place | for that is in the Reference Manual. I must admit that I'd like an apendix a lot better. ... Lgb
Re: Key-binding documentation dilemma
"John" == John Weiss [EMAIL PROTECTED] writes: John On Mon, Dec 04, 2000 at 01:33:55PM +0100, Lars Gullik Bjønnes John wrote: Allan Rae [EMAIL PROTECTED] writes: | On Fri, 1 Dec 2000, Angus Leeming wrote: | | Gentlemen, | | I've written the inset proposed by Jean-Marc. Currently, it's a little | cumbersome to use: I really do not want it done this way... John I agree 100%! This is *not* appropriate for documentation... Why? JMarc
Re: Dead keys still not working with xforms 0.88
"Lars" == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars _or_ really since this is supposed to be handled by lyxlookup, Lars something has changed there? No, I had reverted lyxlookup mostly to the state it was in 1.1.5 (I remove dependency on xforms headers, since it does not make sense). I just commited this. I'll try to look further. JMarc
Re: Key-binding documentation dilemma
On 12 Dec 2000, Lars Gullik Bjønnes wrote: John Weiss [EMAIL PROTECTED] writes: | Plus, it excludes one set of default bindings (e.g. Emacs) in favor of | another (e.g. CUA). We need to document *all* bindings, and the place | for that is in the Reference Manual. I must admit that I'd like an apendix a lot better. Give me a chance to get everything written up. When I'm finished, we can play the appendix vs no appendix game and see how things look. I'm actually beginning to agree more with John on this one, but I'd like to see them in action first. My worry about the Reference Manual is that the keybinding section is likely to be the ONLY section that isn't completely out of date. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Possible bug-type thing
Currently using the version supplied with Mandrake 7.2. On my screen resolution of 800x600 the class list in the Layout - Document dialog is very nearly too large for the screen - I hope that 'Slides' was the last on the list, because most of that is off the screen and anything below that is lost... Sam. -- ___ [EMAIL PROTECTED] | It is not 'who' you are [EMAIL PROTECTED]| But who you are becoming. [EMAIL PROTECTED]| -- Goethe
Re: Possible bug-type thing
On Tue, Dec 12, 2000 at 01:33:41AM +, Sam Vere wrote: Currently using the version supplied with Mandrake 7.2. On my screen resolution of 800x600 the class list in the Layout - Document dialog is very nearly too large for the screen - I hope that 'Slides' was the last on the list, because most of that is off the screen and anything below that is lost... This problem has already been fixed in version 1.1.6 (which will be relased soon).
Re: Dead keys still not working with xforms 0.88
On Tue, Dec 12, 2000 at 01:21:32PM +0100, Lars Gullik Bjønnes wrote: | Until then I will just put it down as "not-a-bug". debug level="key" ;-) Workarea event: KEYBOARD XLookupBoth/ WorkArea: Key is slash' [47] WorkArea: Keysym is KP_Divide' [65455] Workarea Diff: 1698151594 KeySym is KP_Divide[65455] Key [91][KP_Divide] Workarea event: KEYBOARD XLookupBoth* WorkArea: Key is asterisk' [42] WorkArea: Keysym is KP_Multiply' [65450] Workarea Diff: 12662 KeySym is KP_Multiply[65450] Key [91][KP_Multiply] Workarea event: KEYBOARD XLookupBoth- WorkArea: Key is minus' [45] WorkArea: Keysym is KP_Subtract' [65453] Workarea Diff: 4067 KeySym is KP_Subtract[65453] Key [91][KP_Subtract] Workarea event: KEYBOARD XLookupBoth+ WorkArea: Key is plus' [43] WorkArea: Keysym is KP_Add' [65451] Workarea Diff: 2787 KeySym is KP_Add[65451] Key [91][KP_Add] Workarea event: KEYBOARD XLookupBoth1 WorkArea: Key is 1' [49] WorkArea: Keysym is KP_1' [65457] Workarea Diff: 19660 KeySym is KP_1[65457] Key [91][KP_1] Workarea event: KEYBOARD XLookupBoth. WorkArea: Key is period' [46] WorkArea: Keysym is KP_Decimal' [65454] Workarea Diff: 9265 KeySym is KP_Decimal[65454] Key [91][KP_Decimal] Running QuitLyX. TextCache::add 0x8410240 deleted TextCache: BufferView::buffer Deleting tmp dir /tmp/lyx_tmpdir9479id7rL Button: 0x83c4e50 Label: 0x83c4fd8 Form: 0x83c5160 Browser: 0x83c5370 CloseLyXLookup: destroying input context /debug The key that appears is the correct one for all cases, but LyX doesn't display it. I am using xforms 0.88, for lyx-1.1.6pre2, in redhat 7.0. Do you need further informations? -- José
Re: more 1.1.6pre2 deadkeys
On Sat, Dec 02, 2000 at 09:57:32AM -0600, Christopher Jones wrote: Anyway, I have my keymap bound american, and when I go to type the :u sequence for an umlaut the cursor jumps ahead, just like it is supposed to, but then the u which I follow with just sits there, and gets no umlaut. I get the same bug: when setting the keymap to american, and pressing the ':' key, the chr(14) char is inserted to the buffer (instead of waiting for the next char). Pressing the ' key inserts a chr(7) char to the buffer (and you see "foot" (a closed footnote) on screen). I think that between 1.1.5 and 1.1.6pre2 someone changed the keymap handling code (replacing char * by strings or something like that). This bug should be fixed for 1.1.6.
Re: Problems with viewing figures with dvi on 1.1.6pre
Dekel On Wed, Dec 06, 2000 at 09:56:14AM +1030, Ben Cazzolato wrote: Guys I'm having problems with the DVI viewer and figures with lyx1.1.6pre2. I think it has to do with the full path being used. The process initated by lyx when viewing DVI is xdvi.bin -name xdvi -paper a4 /home/bscazz/consult/britax/proposal.dvi Same goes for all my figures. Any ideas? The bug is really in xdvi: it requires the current directory to be '/home/bscazz/consult/britax/' in order to view the eps figures, namely if you run xdvi from another directory by using the full path, it will not show the figures. (The xdvi man page says that if the file name does not begin with a slash, then xdvi will look (for eps files) in the directory containing the DVI file, but it doesn't seem to work). I've attached a fix for this problem: before viewing any file, LyX changes the current directory to the directory of this file. PS: Maybe changing the directory should be done only for DVI viewing. Are there other cases of viewers that requires changing of the directory ? Well, viewing PS figures in the dvi file is no longer a problem. To fix it I turned on the temp directory flag, then turned it off. Yep, weird. The strange thing is now latex'ing doesn't work properly. If I delete my .dvi file and try export dvi it doesn't work. I get no dvi file. I suspect lyx thinks it already exists. Now if I delete the .tex.dep file it will export the dvi. The strange thing is none of these problems occured before 1.1.6pre2 (and now 1.1.6cvs). Ben
Re: Dead keys still not working with xforms 0.88
On Mon, Dec 11, 2000 at 11:35:25PM +0100, Lars Gullik Bjønnes wrote: > > something must have changed... do others also see this problem with > dead keys and XForms 0.88? > > Lgb Not directly related I know, but in pre2 (I have not tried the more recent cvs) I am unable to use the numerical pad. I use it to get / and * on a single strokeç I'm using xforms .88 and I hadn't this issue with previous versions, although this did happen for previous 1.1.6cvs. I guess that I should know better and use the key debug level, but I was curious if any one has (had) this particular problem. -- José
Re: Dead keys still not working with xforms 0.88
Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes: | On Mon, Dec 11, 2000 at 11:35:25PM +0100, Lars Gullik Bjønnes wrote: | > | > something must have changed... do others also see this problem with | > dead keys and XForms 0.88? | > | > Lgb | | Not directly related I know, but in pre2 (I have not tried the more recent | cvs) I am unable to use the numerical pad. I use it to get / and * on a single | strokeç | I'm using xforms .88 and I hadn't this issue with previous versions, | although this did happen for previous 1.1.6cvs. It seems that somehow the keybindings for the numerical pad is not used. Lgb
Re: Dead keys still not working with xforms 0.88
Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes: | On Mon, Dec 11, 2000 at 11:35:25PM +0100, Lars Gullik Bjønnes wrote: | > | > something must have changed... do others also see this problem with | > dead keys and XForms 0.88? | > | > Lgb | | Not directly related I know, but in pre2 (I have not tried the more recent | cvs) I am unable to use the numerical pad. I use it to get / and * on a single | strokeç | I'm using xforms .88 and I hadn't this issue with previous versions, | although this did happen for previous 1.1.6cvs. | | I guess that I should know better and use the key debug level, but I was | curious if any one has (had) this particular problem. I began looking at this... but I am not going too look any further until I get a good bug report. Until then I will just put it down as "not-a-bug". Lgb
Re: Spellchecker popup woes
> "Allan" == Allan Rae <[EMAIL PROTECTED]> writes: Allan> It does beg the question: Do we need/want document scope Allan> options? (Which such a direct link implies) I do not think it will be necessary for the spellchecker. At most, we will need options for each language. JMarc
Re: Problems with viewing figures with dvi on 1.1.6pre
On Wed, Dec 06, 2000 at 09:56:14AM +1030, Ben Cazzolato wrote: > Guys > > I'm having problems with the DVI viewer and figures with lyx1.1.6pre2. I think > it has to do with the full path being used. The process initated by lyx when > viewing DVI is > > xdvi.bin -name xdvi -paper a4 /home/bscazz/consult/britax/proposal.dvi > > Same goes for all my figures. Any ideas? The bug is really in xdvi: it requires the current directory to be '/home/bscazz/consult/britax/' in order to view the eps figures, namely if you run xdvi from another directory by using the full path, it will not show the figures. (The xdvi man page says that if the file name does not begin with a slash, then xdvi will look (for eps files) in the directory containing the DVI file, but it doesn't seem to work). I've attached a fix for this problem: before viewing any file, LyX changes the current directory to the directory of this file. PS: Maybe changing the directory should be done only for DVI viewing. Are there other cases of viewers that requires changing of the directory ? patch.gz
Re: Dead keys still not working with xforms 0.88
On Tue, Dec 12, 2000 at 10:19:55AM +0100, Lars Gullik Bjønnes wrote: > I began looking at this... but I am not going too look any further > until I get a good bug report. > > Until then I will just put it down as "not-a-bug". Ok, I got the point. Do you see this behaviour? > Lgb -- José
Re: Dead keys still not working with xforms 0.88
Jose Abilio Oliveira Matos <[EMAIL PROTECTED]> writes: | On Tue, Dec 12, 2000 at 10:19:55AM +0100, Lars Gullik Bjønnes wrote: | > I began looking at this... but I am not going too look any further | > until I get a good bug report. | > | > Until then I will just put it down as "not-a-bug". | | Ok, I got the point. Do you see this behaviour? Hard to say, since I am using a laptop with weird KP_ keys. But no, I don't belive so since I get the correct keysym. Lgb
Re: Key-binding documentation dilemma
On Mon, Dec 04, 2000 at 01:33:55PM +0100, Lars Gullik Bjønnes wrote: > Allan Rae <[EMAIL PROTECTED]> writes: > > | On Fri, 1 Dec 2000, Angus Leeming wrote: > | > | > Gentlemen, > | > > | > I've written the inset proposed by Jean-Marc. Currently, it's a little > | > cumbersome to use: [snip > I really do not want it done this way... I agree 100%! This is *not* appropriate for documentation... -- John Weiss "Not through coersion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Re: Key-binding documentation dilemma
On Fri, Dec 01, 2000 at 01:39:05PM -0500, Amir Karger wrote: > On Fri, Dec 01, 2000 at 05:27:05PM +0900, Miyata Shigeru wrote: > > Why don't you write a perl script to parse users' lyxrc, preference, ui and > > bind files, and to update UserGuide.lyx? > > But then, each user would need a local copy of that file. (I guess you would > put it in /tmp?) Seems kind of complicated. It will also consume disk space. No... not a good idea. Plus, it excludes one set of default bindings (e.g. Emacs) in favor of another (e.g. CUA). We need to document *all* bindings, and the place for that is in the Reference Manual. More to come shortly... -- John Weiss "Not through coersion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Re: Key-binding documentation dilemma
On Thu, Nov 30, 2000 at 12:22:12PM -0800, Mike Ressler wrote: > Hi, > > I'm working on updating the keyboard shortcuts in the docs (starting with > the User Guide). Given that I'm former editor-in-chief of the LyX Documentation Effort and remain its floating spiritual guide, I think it's time I weigh in on this... 1. Different manuals will need different approaches. It's already been mentioned that the Tutorial should pretty much run with the default bindings, whatever they are. This makes sense; a user reading the Tutorial ain't gonna know or care how to change his keybindings. For the UG and EG, a) Prefer the default bindings; b) However, when deemed necessary, also document the other major binding(s) *in* *addition* *to* the default (either parenthetically or in footnotes; c) Finally, and above all else, do whatever is most appropriate for the flow of the text. This, preservation of readability, takes priority over all else. 2. Full documentation of all bindings belongs in the Reference Manual. Someone else noted that we should document the bindings with the functions, as we currently do. This is by design, folks. If necessary, we can reorganize the RM a bit, junk unused chapters, and move bindings to prominence. An appendix in the UG would, therefore, be redundant. Just refer to the Reference Manual. 3. The RefMan needs a new chapter, one listing keybindings. a) Each major section would be for a particular flavor: (i) Menus and Generic Defaults (ii) CUA-like Default Bindings (iii) Emacs-like Default Bindings b) Within each major section, bindings would be grouped by function/purpose. c) Each group of bindings would be listed by keystroke and sorted lexically. d) Each keybinding would refer to the appropriate reference entry in the chapter documenting lyxfunc's. If no such reference exists, add one. e) For the sake of the printed version, every section/subsection/whatever will make use of "muticols" and be put in at least two columns per page. (Online readers can always use the TOC-menu to navigate.) f) If appropriate, we'll put pagebreaks into this chapter so that users can print out "quick-reference" sheets for the group(s) of bindings they use the most. So say I! -- John Weiss "Not through coersion. Not by force. But by compassion. By affection. And, a small fish." -His Holiness, the 14th Dalai Lama
Re: Key-binding documentation dilemma
John Weiss <[EMAIL PROTECTED]> writes: | On Fri, Dec 01, 2000 at 01:39:05PM -0500, Amir Karger wrote: | > On Fri, Dec 01, 2000 at 05:27:05PM +0900, Miyata Shigeru wrote: | > > Why don't you write a perl script to parse users' lyxrc, preference, ui and | > > bind files, and to update UserGuide.lyx? | > | > But then, each user would need a local copy of that file. (I guess you would | > put it in /tmp?) Seems kind of complicated. | | It will also consume disk space. No... not a good idea. | | Plus, it excludes one set of default bindings (e.g. Emacs) in favor of | another (e.g. CUA). We need to document *all* bindings, and the place | for that is in the Reference Manual. I must admit that I'd like an apendix a lot better. ... Lgb
Re: Key-binding documentation dilemma
> "John" == John Weiss <[EMAIL PROTECTED]> writes: John> On Mon, Dec 04, 2000 at 01:33:55PM +0100, Lars Gullik Bjønnes John> wrote: >> Allan Rae <[EMAIL PROTECTED]> writes: >> >> | On Fri, 1 Dec 2000, Angus Leeming wrote: | | > Gentlemen, | > | > >> I've written the inset proposed by Jean-Marc. Currently, it's a >> little | > cumbersome to use: >> I really do not want it done this way... John> I agree 100%! This is *not* appropriate for documentation... Why? JMarc
Re: Dead keys still not working with xforms 0.88
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> _or_ really since this is supposed to be handled by lyxlookup, Lars> something has changed there? No, I had reverted lyxlookup mostly to the state it was in 1.1.5 (I remove dependency on xforms headers, since it does not make sense). I just commited this. I'll try to look further. JMarc
Re: Key-binding documentation dilemma
On 12 Dec 2000, Lars Gullik Bjønnes wrote: > John Weiss <[EMAIL PROTECTED]> writes: > | Plus, it excludes one set of default bindings (e.g. Emacs) in favor of > | another (e.g. CUA). We need to document *all* bindings, and the place > | for that is in the Reference Manual. > > I must admit that I'd like an apendix a lot better. Give me a chance to get everything written up. When I'm finished, we can play the appendix vs no appendix game and see how things look. I'm actually beginning to agree more with John on this one, but I'd like to see them in action first. My worry about the Reference Manual is that the keybinding section is likely to be the ONLY section that isn't completely out of date. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Possible bug-type thing
Currently using the version supplied with Mandrake 7.2. On my screen resolution of 800x600 the class list in the Layout -> Document dialog is very nearly too large for the screen - I hope that 'Slides' was the last on the list, because most of that is off the screen and anything below that is lost... Sam. -- ___ [EMAIL PROTECTED] | It is not 'who' you are [EMAIL PROTECTED]| But who you are becoming. [EMAIL PROTECTED]| -- Goethe
Re: Possible bug-type thing
On Tue, Dec 12, 2000 at 01:33:41AM +, Sam Vere wrote: > Currently using the version supplied with Mandrake 7.2. On my screen > resolution of 800x600 the class list in the Layout -> Document dialog is > very nearly too large for the screen - I hope that 'Slides' was the last > on the list, because most of that is off the screen and anything below > that is lost... This problem has already been fixed in version 1.1.6 (which will be relased soon).
Re: Dead keys still not working with xforms 0.88
On Tue, Dec 12, 2000 at 01:21:32PM +0100, Lars Gullik Bjønnes wrote: > | > Until then I will just put it down as "not-a-bug". ;-) Workarea event: KEYBOARD XLookupBoth/ WorkArea: Key is slash' [47] WorkArea: Keysym is KP_Divide' [65455] Workarea Diff: 1698151594 KeySym is KP_Divide[65455] Key [91][KP_Divide] Workarea event: KEYBOARD XLookupBoth* WorkArea: Key is asterisk' [42] WorkArea: Keysym is KP_Multiply' [65450] Workarea Diff: 12662 KeySym is KP_Multiply[65450] Key [91][KP_Multiply] Workarea event: KEYBOARD XLookupBoth- WorkArea: Key is minus' [45] WorkArea: Keysym is KP_Subtract' [65453] Workarea Diff: 4067 KeySym is KP_Subtract[65453] Key [91][KP_Subtract] Workarea event: KEYBOARD XLookupBoth+ WorkArea: Key is plus' [43] WorkArea: Keysym is KP_Add' [65451] Workarea Diff: 2787 KeySym is KP_Add[65451] Key [91][KP_Add] Workarea event: KEYBOARD XLookupBoth1 WorkArea: Key is 1' [49] WorkArea: Keysym is KP_1' [65457] Workarea Diff: 19660 KeySym is KP_1[65457] Key [91][KP_1] Workarea event: KEYBOARD XLookupBoth. WorkArea: Key is period' [46] WorkArea: Keysym is KP_Decimal' [65454] Workarea Diff: 9265 KeySym is KP_Decimal[65454] Key [91][KP_Decimal] Running QuitLyX. TextCache::add 0x8410240 deleted TextCache: BufferView::buffer Deleting tmp dir /tmp/lyx_tmpdir9479id7rL Button: 0x83c4e50 Label: 0x83c4fd8 Form: 0x83c5160 Browser: 0x83c5370 CloseLyXLookup: destroying input context The key that appears is the correct one for all cases, but LyX doesn't display it. I am using xforms 0.88, for lyx-1.1.6pre2, in redhat 7.0. Do you need further informations? -- José
Re: more 1.1.6pre2 deadkeys
On Sat, Dec 02, 2000 at 09:57:32AM -0600, Christopher Jones wrote: > Anyway, I have my keymap bound american, and when I go to type the :u sequence > for an umlaut the cursor jumps ahead, just like it is supposed to, but then the > u which I follow with just sits there, and gets no umlaut. I get the same bug: when setting the keymap to american, and pressing the ':' key, the chr(14) char is inserted to the buffer (instead of waiting for the next char). Pressing the ' key inserts a chr(7) char to the buffer (and you see "foot" (a closed footnote) on screen). I think that between 1.1.5 and 1.1.6pre2 someone changed the keymap handling code (replacing char * by strings or something like that). This bug should be fixed for 1.1.6.
Re: Problems with viewing figures with dvi on 1.1.6pre
Dekel > On Wed, Dec 06, 2000 at 09:56:14AM +1030, Ben Cazzolato wrote: > > Guys > > > > I'm having problems with the DVI viewer and figures with lyx1.1.6pre2. I think > > it has to do with the full path being used. The process initated by lyx when > > viewing DVI is > > > > xdvi.bin -name xdvi -paper a4 /home/bscazz/consult/britax/proposal.dvi > > > > Same goes for all my figures. Any ideas? > > The bug is really in xdvi: it requires the current directory to be > '/home/bscazz/consult/britax/' in order to view the eps figures, namely > if you run xdvi from another directory by using the full path, it will not show > the figures. > (The xdvi man page says that if the file name does not begin with a slash, > then xdvi will look (for eps files) in the directory containing the DVI file, > but it doesn't seem to work). > > I've attached a fix for this problem: before viewing any file, LyX changes the > current directory to the directory of this file. > > PS: Maybe changing the directory should be done only for DVI viewing. > Are there other cases of viewers that requires changing of the directory ? Well, viewing PS figures in the dvi file is no longer a problem. To fix it I turned on the temp directory flag, then turned it off. Yep, weird. The strange thing is now latex'ing doesn't work properly. If I delete my .dvi file and try export dvi it doesn't work. I get no dvi file. I suspect lyx thinks it already exists. Now if I delete the .tex.dep file it will export the dvi. The strange thing is none of these problems occured before 1.1.6pre2 (and now 1.1.6cvs). Ben
