Re: Question about eqnarray environment (multiple = or <> symbols)

On May 4, 2009, at 5:27 PM, Jim Rockford wrote: Hello : this is probably more of a latex issue than Lyx, but I would like to do this quickly in Lyx, so... What I want is a neatly formatted set of relations like a < S < b c < T < d and so forth. I just need the analog of the usual "3

Re: Question about eqnarray environment (multiple = or symbols)

Jim Rockford wrote: Hello : this is probably more of a latex issue than Lyx, but I would like to do this quickly in Lyx, so... What I want is a neatly formatted set of relations like a S b c T d and so forth. I just need the analog of the usual 3 column equation array environment so that

Re: Question about eqnarray environment (multiple = or symbols)

Jim Rockford wrote: Hello : this is probably more of a latex issue than Lyx, but I would like to do this quickly in Lyx, so... What I want is a neatly formatted set of relations like a S b c T d and so forth. I just need the analog of the usual 3 column equation array environment so that

Re: Question about eqnarray environment (multiple = or <> symbols)

Jim Rockford wrote: Hello : this is probably more of a latex issue than Lyx, but I would like to do this quickly in Lyx, so... What I want is a neatly formatted set of relations like a < S < b c < T < d and so forth. I just need the analog of the usual "3 column" equation array environment

Re: question re citation

On 2009-04-27, Wolfgang Engelmann wrote: In a document (Lyx1.6.1) I get an error message TeX capacity exceeded cite{a reference}{319}{13.5.3}{section*.37} If you really absolutely need more capacity ... I tried to remove the citation from the text for a later inspection what was going

Re: question re citation

Am Tuesday 28 April 2009 10:26:30 schrieb Guenter Milde: Still, the aux-file is generated (from the document and the bibtex-extracted citations). It is annoying to have to restart the session for each removal. Is there a better way? Does closing and reopening the doc help? Or just try a

Re: question re citation

On 2009-04-27, Wolfgang Engelmann wrote: In a document (Lyx1.6.1) I get an error message TeX capacity exceeded cite{a reference}{319}{13.5.3}{section*.37} If you really absolutely need more capacity ... I tried to remove the citation from the text for a later inspection what was going

Re: question re citation

Am Tuesday 28 April 2009 10:26:30 schrieb Guenter Milde: Still, the aux-file is generated (from the document and the bibtex-extracted citations). It is annoying to have to restart the session for each removal. Is there a better way? Does closing and reopening the doc help? Or just try a

Re: question re citation

On 2009-04-27, Wolfgang Engelmann wrote: > In a document (Lyx1.6.1) I get an error message > TeX capacity exceeded > cite{a reference}{319}{13.5.3}{section*.37} > If you really absolutely need more capacity ... > I tried to remove the citation from the text for a later inspection what was >

Re: question re citation

Am Tuesday 28 April 2009 10:26:30 schrieb Guenter Milde: > > Still, the aux-file is generated (from the document and the > bibtex-extracted citations). > > > It is annoying to have to restart the session for each removal. Is there > > a better way? > > Does closing and reopening the doc help? Or

Re: Question on \setkomafont{}{}

On Sat, Apr 18, 2009 at 1:34 PM, Rich Shepard rshep...@appl-ecosys.comwrote: From the KOMA-script doc I see that I can use the \setkomafont{element}{command} directive to change the typeface for specific document elements. Rather than the san-serif font for the title and section heads, I

Re: Question on \setkomafont{}{} -- ANSWERED

On Sat, 18 Apr 2009, Bob Lounsbury wrote: Don't have access to LyX at the moment. Does \setkomafont{sectioning}{} work for unnumbered sections? Probably not, but I thought I'd ask. Bob, Wow! It certainly does! It did not occur to me to try that, but it sure does the job. Many thanks,

Re: Question on \setkomafont{}{}

Bob Lounsbury wrote: From the KOMA-script doc I see that I can use the \setkomafont{element}{command} directive to change the typeface for specific document elements. Rather than the san-serif font for the title and section heads, I prefer to use the default body text typeface of

Re: Question on \setkomafont{}{}

On Sat, 18 Apr 2009, cmira...@kde-france.org wrote: Try \renewcommand\sectfont{\rmfamily} Not very logical Charles, That's the old KOMA-script way. And, Bob's suggestion of using the sectioning alias to dispositioning (Table 3.3 in the manual) works like a charm. Thank you, Rich --

Re: Question on \setkomafont{}{}

On Sat, Apr 18, 2009 at 1:34 PM, Rich Shepard rshep...@appl-ecosys.comwrote: From the KOMA-script doc I see that I can use the \setkomafont{element}{command} directive to change the typeface for specific document elements. Rather than the san-serif font for the title and section heads, I

Re: Question on \setkomafont{}{} -- ANSWERED

On Sat, 18 Apr 2009, Bob Lounsbury wrote: Don't have access to LyX at the moment. Does \setkomafont{sectioning}{} work for unnumbered sections? Probably not, but I thought I'd ask. Bob, Wow! It certainly does! It did not occur to me to try that, but it sure does the job. Many thanks,

Re: Question on \setkomafont{}{}

Bob Lounsbury wrote: From the KOMA-script doc I see that I can use the \setkomafont{element}{command} directive to change the typeface for specific document elements. Rather than the san-serif font for the title and section heads, I prefer to use the default body text typeface of

Re: Question on \setkomafont{}{}

On Sat, 18 Apr 2009, cmira...@kde-france.org wrote: Try \renewcommand\sectfont{\rmfamily} Not very logical Charles, That's the old KOMA-script way. And, Bob's suggestion of using the sectioning alias to dispositioning (Table 3.3 in the manual) works like a charm. Thank you, Rich --

Re: Question on \setkomafont{}{}

On Sat, Apr 18, 2009 at 1:34 PM, Rich Shepard wrote: > From the KOMA-script doc I see that I can use the > \setkomafont{element}{command} directive to change the typeface for > specific > document elements. > > Rather than the san-serif font for the title and section

Re: Question on \setkomafont{}{} -- ANSWERED

On Sat, 18 Apr 2009, Bob Lounsbury wrote: Don't have access to LyX at the moment. Does \setkomafont{sectioning}{} work for unnumbered sections? Probably not, but I thought I'd ask. Bob, Wow! It certainly does! It did not occur to me to try that, but it sure does the job. Many thanks,

Re: Question on \setkomafont{}{}

Bob Lounsbury wrote: >> From the KOMA-script doc I see that I can use the >> \setkomafont{element}{command} directive to change the typeface for >> specific >> document elements. >> >> Rather than the san-serif font for the title and section heads, I prefer >> to use the default body text

Re: Question on \setkomafont{}{}

On Sat, 18 Apr 2009, cmira...@kde-france.org wrote: Try \renewcommand\sectfont{\rmfamily} Not very logical Charles, That's the old KOMA-script way. And, Bob's suggestion of using the sectioning alias to dispositioning (Table 3.3 in the manual) works like a charm. Thank you, Rich --

Re: Question about Full screen on Windows

Vassil Lunchev wrote: When Full screen is active and there is more than one screen of text, the last line is always at the bottom of the screen. I prefer it being somewhere in the middle of my screen. Is there a way to configure the view so that it displays the last line somewhere in the

Re: Question about Full screen on Windows

Vassil Lunchev wrote: When Full screen is active and there is more than one screen of text, the last line is always at the bottom of the screen. I prefer it being somewhere in the middle of my screen. Is there a way to configure the view so that it displays the last line somewhere in the

Re: Question about "Full screen" on Windows

Vassil Lunchev wrote: > When Full screen is active and there is more than one screen of text, the > last line is always at the bottom of the screen. I prefer it being > somewhere in the middle of my screen. Is there a way to configure the > "view" so that it displays the last line somewhere in

Re: Question on managing templates and features

Jay Austad wrote: Can LyX provide the functionality that I need? I installed it, but the version control menu is empty. How do I go about setting up LyX to work with SVN? I couldn't find documentation on that. The file you're editing has already be registered with version control. So you

Re: Question on managing templates and features

Jay Austad wrote: Can LyX provide the functionality that I need? I installed it, but the version control menu is empty. How do I go about setting up LyX to work with SVN? I couldn't find documentation on that. The file you're editing has already be registered with version control. So you

Re: Question on managing templates and features

Jay Austad wrote: Can LyX provide the functionality that I need? I installed it, but the version control menu is empty. How do I go about setting up LyX to work with SVN? I couldn't find documentation on that. The file you're editing has already be registered with version control. So you

Re: Question : how to write vietnamese documents with LyX-1.6.1

R. Josh III schrieb: Is it possible to write vietnamese (with viqr code for instance) with LyX-1.6.1 ? I don't know about viqr, but I created a Wiki page describing the basic steps: http://wiki.lyx.org/Windows/Vietnamese To use your french keyboard for vietnamese, you can create your own

Re: Question : how to write vietnamese documents with LyX-1.6.1

R. Josh III schrieb: Is it possible to write vietnamese (with viqr code for instance) with LyX-1.6.1 ? I don't know about viqr, but I created a Wiki page describing the basic steps: http://wiki.lyx.org/Windows/Vietnamese To use your french keyboard for vietnamese, you can create your own

Re: Question : how to write vietnamese documents with LyX-1.6.1

R. Josh III schrieb: Is it possible to write vietnamese (with viqr code for instance) with LyX-1.6.1 ? I don't know about "viqr", but I created a Wiki page describing the basic steps: http://wiki.lyx.org/Windows/Vietnamese To use your french keyboard for vietnamese, you can create your own

Re: question about breaking words in pdf files

Ana Rodriguez schrieb: Is there any way to make lyx not to break words in the pdf files at the end of the line? Yes, you can either use a non-breakable space between words as described in sec. 3.5.1 of the UserGuide or put a word into a special box as described in sec. 3.9.2 of the

Re: question about breaking words in pdf files

Ana Rodriguez schrieb: Is there any way to make lyx not to break words in the pdf files at the end of the line? Yes, you can either use a non-breakable space between words as described in sec. 3.5.1 of the UserGuide or put a word into a special box as described in sec. 3.9.2 of the

Re: question about breaking words in pdf files

Ana Rodriguez schrieb: Is there any way to make lyx not to break words in the pdf files at the end of the line? Yes, you can either use a non-breakable space between words as described in sec. 3.5.1 of the UserGuide or put a word into a special box as described in sec. 3.9.2 of the

Re: Question on whitespace at the end of raw TeX - inserts

Dieter Jurzitza wrote: Hi folks, first of all: thank you for all your replies. And yes, after hearing what you came up with I think ERT should remain ERT and inserting an automatic blank _within_ the ERT is not a good idea. But wait: what is LyX saying about itself, WYSIWYM? Hey, if I put a

Re: Question on whitespace at the end of raw TeX - inserts

Dear Helge, thank you for your reply. There were several of them - and I came to the end that I - to some extend - took it too simple. My personal wrap up is the fact that the current TeX-inserts in LyX are not encapsulated - i. e. they reach further than the closing insert bracket. So, maybe

Re: Question on whitespace at the end of raw TeX - inserts

Dieter Jurzitza wrote: Hi folks, first of all: thank you for all your replies. And yes, after hearing what you came up with I think ERT should remain ERT and inserting an automatic blank _within_ the ERT is not a good idea. But wait: what is LyX saying about itself, WYSIWYM? Hey, if I put a

Re: Question on whitespace at the end of raw TeX - inserts

Dear Helge, thank you for your reply. There were several of them - and I came to the end that I - to some extend - took it too simple. My personal wrap up is the fact that the current TeX-inserts in LyX are not encapsulated - i. e. they reach further than the closing insert bracket. So, maybe

Re: Question on whitespace at the end of raw TeX - inserts

Dieter Jurzitza wrote: Hi folks, first of all: thank you for all your replies. And yes, after hearing what you came up with I think ERT should remain ERT and inserting an automatic blank _within_ the ERT is not a good idea. But wait: what is LyX saying about itself, WYSIWYM? Hey, if I put a

Re: Question on whitespace at the end of raw TeX - inserts

Dear Helge, thank you for your reply. There were several of them - and I came to the end that I - to some extend - took it too simple. My personal wrap up is the fact that the current TeX-inserts in LyX are not encapsulated - i. e. they reach further than the closing insert "bracket". So,

Re: Question on cross-reference dialog window

Peter Baumgartner wrote: Hello, In my LyX installation 1.6.1 on Mac OSX I have a cross-reference window with an input field called Name which is always grayed out so that no input is possible. Maybe this should work for formatted references? But how to use it? This is only used with

Re: Question on cross-reference dialog window

Peter Baumgartner wrote: Hello, In my LyX installation 1.6.1 on Mac OSX I have a cross-reference window with an input field called Name which is always grayed out so that no input is possible. Maybe this should work for formatted references? But how to use it? This is only used with

Re: Question on cross-reference dialog window

Peter Baumgartner wrote: Hello, In my LyX installation 1.6.1 on Mac OSX I have a cross-reference window with an input field called "Name" which is always grayed out so that no input is possible. Maybe this should work for formatted references? But how to use it? This is only used with

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Hi Vincent, I wouldn't consider / being a good idea when it comes to file access, as is \ not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say __ as a replacement for \. __ is harmless in any regard, escaping is not

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted in success. So, at least

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Hi Vincent, I wouldn't consider / being a good idea when it comes to file access, as is \ not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say __ as a replacement for \. __ is harmless in any regard, escaping is not

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted in success. So, at least

Re: Question on section - properties in the menu bar

> Dieter Jurzitza schreef: >> Hi Vincent, >> I wouldn't consider "/" being a good idea when it comes to file access, as >> is "\" not a good idea. >> >> If I was asked I'd rather suggest to use something like a doubled >> underscore, say "__" as a replacement for "\". "__" is harmless in any >>

Re: Question on section - properties in the menu bar

> Dieter Jurzitza schreef: >> Dear listmembers, >> well, obviously my C-programming capabilities were sufficient, though. My >> first attempt of using "fprintf("%s\n", name1); ended with an "invalid >> machinecode" message - but patching the debugging-cout messagestring >> resulted in success.

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Hi Vincent, I wouldn't consider / being a good idea when it comes to file access, as is \ not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say __ as a replacement for \. __ is harmless in any regard, escaping is not

Re: Question on section - properties in the menu bar

On Jan 1, 2009, at 11:33 AM, Dieter Jurzitza wrote: When including figures in reports, I mostly (but not always) put them centered, in contrast, the remainder of the text remains aligned justified. And I am sure that I could potentially write a specific environment doing this, use

Re: Question on section - properties in the menu bar

Hi Vincent, this solution is perfectly fine with me - would you kindly consider to include my debugging - extension to GuiApplication.cpp as well? I never ever worked on a public source repository - and basically I think that I would not come up with too many contributions so some other nice

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Hi Vincent, I wouldn't consider / being a good idea when it comes to file access, as is \ not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say __ as a replacement for \. __ is harmless in any regard, escaping is not

Re: Question on section - properties in the menu bar

On Jan 1, 2009, at 11:33 AM, Dieter Jurzitza wrote: When including figures in reports, I mostly (but not always) put them centered, in contrast, the remainder of the text remains aligned justified. And I am sure that I could potentially write a specific environment doing this, use

Re: Question on section - properties in the menu bar

Hi Vincent, this solution is perfectly fine with me - would you kindly consider to include my debugging - extension to GuiApplication.cpp as well? I never ever worked on a public source repository - and basically I think that I would not come up with too many contributions so some other nice

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Hi Vincent, I wouldn't consider "/" being a good idea when it comes to file access, as is "\" not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say "__" as a replacement for "\". "__" is harmless in any regard, escaping

Re: Question on section - properties in the menu bar

On Jan 1, 2009, at 11:33 AM, Dieter Jurzitza wrote: When including figures in reports, I mostly (but not always) put them centered, in contrast, the remainder of the text remains aligned justified. And I am sure that I could potentially write a specific environment doing this, use

Re: Question on section - properties in the menu bar

Hi Vincent, this solution is perfectly fine with me - would you kindly consider to include my debugging - extension to GuiApplication.cpp as well? I never ever worked on a public source repository - and basically I think that I would not come up with too many contributions so some other nice

Re: Question on section - properties in the menu bar

Dear Steve, dear listmembers, your answer tells me that I haven't been precise enough. Imagine you have a section in your document you want to be centered rather than (i.e.) flushleft. To achieve this in LyX, you have to mark the section and then klick on the section menu, from where you can

Re: Question on section - properties in the menu bar

In 1.6.x you can right-click to do this. It is still not as quick as a button, but is quicker than digging through menus... On Jan 1, 2009, at 5:27 AM, Dieter Jurzitza dieter.jurzi...@t- online.de wrote: Dear Steve, dear listmembers, your answer tells me that I haven't been precise

Re: Question on section - properties in the menu bar

On Thursday 01 January 2009 07:27:29 am Dieter Jurzitza wrote: Dear Steve, dear listmembers, your answer tells me that I haven't been precise enough. Imagine you have a section in your document you want to be centered rather than (i.e.) flushleft. To achieve this in LyX, you have to mark the

Re: Question on section - properties in the menu bar

Well, lazy me, what I would like to see are three little symbols for flush-right, flush-left or center on the top-level menu bar that help me avoid diving into a submenu in order to achieve this. I don't have a red robe or a long white beard, so if you still want to have the four (you need

Re: Question on section - properties in the menu bar

Dear listmembers, in the meantime I created some icons for my purpose and have been putting them in the directory /usr/share/lyx/images. From the stdtoolbars.inc file I know (theoretically) that the naming convention for the files ought to be action_parameter.png following this strategy

Re: Question on section - properties in the menu bar

Dear listmembers, dear Vincent, dear Steve, well, I can see, christmas just passed by, so I am not t sad about Vincent for not having the red robe and the beard. But many thanks to Vincent, this really did the trick! And, Steve, you do not have to make me a TeXnician - I readily am (since

Re: Question on section - properties in the menu bar

Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted in success. So, at least for linux I can confirm that \ in

Re: Question on section - properties in the menu bar

On Thu, Jan 01, 2009 at 10:03:12PM +0100, Dieter Jurzitza wrote: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted in success. So, at least for

Re: Question on section - properties in the menu bar

Dear Andre, thanks for the pointer, I see, I see, I forgot to apply the stderr in fprintf ... I know, there are lots of people around having higher programming capabilities than I do ;-), but anyway, one should not mix up C and C++, so, it wasn't that bad to modify LYXERR output instead

Re: Question on section - properties in the menu bar

Vincent van Ravesteijn wrote: Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted

Re: Question on section - properties in the menu bar

rgheck schreef: Vincent van Ravesteijn wrote: Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout

Re: Question on section - properties in the menu bar

Hi Vincent, I wouldn't consider / being a good idea when it comes to file access, as is \ not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say __ as a replacement for \. __ is harmless in any regard, escaping is not complicated. As an alternative

Re: Question on section - properties in the menu bar

Dear Steve, dear listmembers, your answer tells me that I haven't been precise enough. Imagine you have a section in your document you want to be centered rather than (i.e.) flushleft. To achieve this in LyX, you have to mark the section and then klick on the section menu, from where you can

Re: Question on section - properties in the menu bar

In 1.6.x you can right-click to do this. It is still not as quick as a button, but is quicker than digging through menus... On Jan 1, 2009, at 5:27 AM, Dieter Jurzitza dieter.jurzi...@t- online.de wrote: Dear Steve, dear listmembers, your answer tells me that I haven't been precise

Re: Question on section - properties in the menu bar

On Thursday 01 January 2009 07:27:29 am Dieter Jurzitza wrote: Dear Steve, dear listmembers, your answer tells me that I haven't been precise enough. Imagine you have a section in your document you want to be centered rather than (i.e.) flushleft. To achieve this in LyX, you have to mark the

Re: Question on section - properties in the menu bar

Well, lazy me, what I would like to see are three little symbols for flush-right, flush-left or center on the top-level menu bar that help me avoid diving into a submenu in order to achieve this. I don't have a red robe or a long white beard, so if you still want to have the four (you need

Re: Question on section - properties in the menu bar

Dear listmembers, in the meantime I created some icons for my purpose and have been putting them in the directory /usr/share/lyx/images. From the stdtoolbars.inc file I know (theoretically) that the naming convention for the files ought to be action_parameter.png following this strategy

Re: Question on section - properties in the menu bar

Dear listmembers, dear Vincent, dear Steve, well, I can see, christmas just passed by, so I am not t sad about Vincent for not having the red robe and the beard. But many thanks to Vincent, this really did the trick! And, Steve, you do not have to make me a TeXnician - I readily am (since

Re: Question on section - properties in the menu bar

Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted in success. So, at least for linux I can confirm that \ in

Re: Question on section - properties in the menu bar

On Thu, Jan 01, 2009 at 10:03:12PM +0100, Dieter Jurzitza wrote: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted in success. So, at least for

Re: Question on section - properties in the menu bar

Dear Andre, thanks for the pointer, I see, I see, I forgot to apply the stderr in fprintf ... I know, there are lots of people around having higher programming capabilities than I do ;-), but anyway, one should not mix up C and C++, so, it wasn't that bad to modify LYXERR output instead

Re: Question on section - properties in the menu bar

Vincent van Ravesteijn wrote: Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout messagestring resulted

Re: Question on section - properties in the menu bar

rgheck schreef: Vincent van Ravesteijn wrote: Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using fprintf(%s\n, name1); ended with an invalid machinecode message - but patching the debugging-cout

Re: Question on section - properties in the menu bar

Hi Vincent, I wouldn't consider / being a good idea when it comes to file access, as is \ not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say __ as a replacement for \. __ is harmless in any regard, escaping is not complicated. As an alternative

Re: Question on section - properties in the menu bar

Dear Steve, dear listmembers, your answer tells me that I haven't been precise enough. Imagine you have a section in your document you want to be centered rather than (i.e.) flushleft. To achieve this in LyX, you have to mark the section and then klick on the section menu, from where you can

Re: Question on section - properties in the menu bar

In 1.6.x you can right-click to do this. It is still not as quick as a button, but is quicker than digging through menus... On Jan 1, 2009, at 5:27 AM, Dieter Jurzitza wrote: Dear Steve, dear listmembers, your answer tells me that I haven't been precise

Re: Question on section - properties in the menu bar

On Thursday 01 January 2009 07:27:29 am Dieter Jurzitza wrote: > Dear Steve, > dear listmembers, > your answer tells me that I haven't been precise enough. Imagine you have a > section in your document you want to be centered rather than (i.e.) > flushleft. To achieve this in LyX, you have to mark

Re: Question on section - properties in the menu bar

Well, lazy me, what I would like to see are three little symbols for flush-right, flush-left or center on the top-level menu bar that help me avoid diving into a submenu in order to achieve this. I don't have a "red robe or a long white beard", so if you still want to have the four (you

Re: Question on section - properties in the menu bar

Dear listmembers, in the meantime I created some icons for my purpose and have been putting them in the directory /usr/share/lyx/images. From the stdtoolbars.inc file I know (theoretically) that the naming convention for the files ought to be _.png following this strategy based on i.e.

Re: Question on section - properties in the menu bar

Dear listmembers, dear Vincent, dear Steve, well, I can see, christmas just passed by, so I am not t sad about Vincent for not having the red robe and the beard. But many thanks to Vincent, this really did the trick! And, Steve, you do not have to make me a TeXnician - I readily am (since

Re: Question on section - properties in the menu bar

Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using "fprintf("%s\n", name1); ended with an "invalid machinecode" message - but patching the debugging-cout messagestring resulted in success. So, at least for linux I can confirm that

Re: Question on section - properties in the menu bar

On Thu, Jan 01, 2009 at 10:03:12PM +0100, Dieter Jurzitza wrote: > Dear listmembers, > well, obviously my C-programming capabilities were sufficient, though. My > first attempt of using "fprintf("%s\n", name1); ended with an "invalid > machinecode" message - but patching the debugging-cout

Re: Question on section - properties in the menu bar

Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using "fprintf("%s\n", name1); ended with an "invalid machinecode" message - but patching the debugging-cout messagestring resulted in success. So, at least

Re: Question on section - properties in the menu bar

Dear Andre, thanks for the pointer, I see, I see, I forgot to apply the "stderr" in fprintf ... I know, there are lots of people around having higher programming capabilities than I do ;-), but anyway, one should not mix up C and C++, so, it wasn't that bad to modify LYXERR output instead

Re: Question on section - properties in the menu bar

Vincent van Ravesteijn wrote: Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using "fprintf("%s\n", name1); ended with an "invalid machinecode" message - but patching the debugging-cout messagestring

Re: Question on section - properties in the menu bar

rgheck schreef: Vincent van Ravesteijn wrote: Dieter Jurzitza schreef: Dear listmembers, well, obviously my C-programming capabilities were sufficient, though. My first attempt of using "fprintf("%s\n", name1); ended with an "invalid machinecode" message - but patching the debugging-cout

Re: Question on section - properties in the menu bar

Hi Vincent, I wouldn't consider "/" being a good idea when it comes to file access, as is "\" not a good idea. If I was asked I'd rather suggest to use something like a doubled underscore, say "__" as a replacement for "\". "__" is harmless in any regard, escaping is not complicated. As an

Re: Question on section - properties in the menu bar

On Wednesday 31 December 2008 10:03:52 am Dieter Jurzitza wrote: Dear listmembers, from other text processing systems (b ) I am acustomed to the possibility to directly access the section attributes (centered, right adjusted, left adjusted) via small icons in the menu bar. I know this

Re: Question on section - properties in the menu bar

On Wednesday 31 December 2008 10:03:52 am Dieter Jurzitza wrote: Dear listmembers, from other text processing systems (b ) I am acustomed to the possibility to directly access the section attributes (centered, right adjusted, left adjusted) via small icons in the menu bar. I know this

Re: Question on section - properties in the menu bar

On Wednesday 31 December 2008 10:03:52 am Dieter Jurzitza wrote: > Dear listmembers, > from other text processing systems (b ) I am acustomed to the > possibility to directly access the section attributes (centered, right > adjusted, left adjusted) via small icons in the menu bar. > I know

<    3   4   5   6   7   8   9   10   11   12   >