Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 07:47:50PM +, Kornel Benko wrote: > Hm, I don't think it depends on TL. Using system fonts is slow here. > In fact, installing "fonts-farsiweb" and "ttf-freefarsi" improved the > compilation dramatically. > > 1/1 Test #4880: INVERTED.TODO_export/examples/fa/splash_pdf

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 14:01:25, schrieb Scott Kostyshak > On Mon, Jan 15, 2018 at 06:42:31PM +, Kornel Benko wrote: > > Am Montag, 15. Januar 2018 um 13:03:26, schrieb Scott Kostyshak > > > > > On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > > > > > > > There are te

Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 06:42:31PM +, Kornel Benko wrote: > Am Montag, 15. Januar 2018 um 13:03:26, schrieb Scott Kostyshak > > > On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > > > > > There are tests running about 10 minutes (like export farsi files). > > > > Does fa/splas

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 13:03:26, schrieb Scott Kostyshak > On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > > > There are tests running about 10 minutes (like export farsi files). > > Does fa/splash.lyx take about 10 minutes for you? Actually, no PDF > export for Farsi is

Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 01:34:45PM +, Pavel Sanda wrote: > Jean-Marc Lasgouttes wrote: > > BTW, what is the difference between buffer-export and buffer-export-as ? > > I believe the second opens the dialog for you. Yes, and also buffer-export takes a second (optional) argument, which is the

Re: Test wish for a new lfunc

On Mon, Jan 15, 2018 at 01:21:57PM +, Kornel Benko wrote: > There are tests running about 10 minutes (like export farsi files). Does fa/splash.lyx take about 10 minutes for you? Actually, no PDF export for Farsi is uninverted for me. Does the export take 10 minutes to fail for you? I get the

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 15:04:55, schrieb Jean-Marc Lasgouttes > Le 15/01/2018 à 14:21, Kornel Benko a écrit : > > This is not desirable due to parallel run of tests which use the same lyxrc. > > There are tests running about 10 minutes (like export farsi files). > > And possible waiting fo

Re: Test wish for a new lfunc

Le 15/01/2018 à 14:21, Kornel Benko a écrit : This is not desirable due to parallel run of tests which use the same lyxrc. There are tests running about 10 minutes (like export farsi files). And possible waiting for 10 minutes for a test which should complete in 10 seconds is definitely not desi

Re: Test wish for a new lfunc

Jean-Marc Lasgouttes wrote: > Ah, yes there is this async thing. I thought that we wanted to disable it > when running in batch mode or in command-sequence, right? I do not know batch-mode well, but I do not think you can use it for useful command sequences, you need gui for that (e.g. even buffe

Re: Test wish for a new lfunc

Le 15/01/2018 à 14:10, Pavel Sanda a écrit : Jean-Marc Lasgouttes wrote: What about making os::timeout_min() be configurable by LyXRC (maybe in seconds instead of minutes if you prefer)? Then you could set the rc variable to some value before doing the export. But you still need some wait func

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 14:10:10, schrieb Pavel Sanda > Jean-Marc Lasgouttes wrote: > > What about making os::timeout_min() be configurable by LyXRC (maybe in > > seconds instead of minutes if you prefer)? Then you could set the rc > > variable to some value before doing the export. This

Re: Test wish for a new lfunc

Jean-Marc Lasgouttes wrote: > What about making os::timeout_min() be configurable by LyXRC (maybe in > seconds instead of minutes if you prefer)? Then you could set the rc > variable to some value before doing the export. But you still need some wait function, which hangs until export(cancel) is

Re: Test wish for a new lfunc

Le 15/01/2018 à 13:02, Kornel Benko a écrit : Am Montag, 15. Januar 2018 um 12:55:00, schrieb Pavel Sanda Kornel Benko wrote: Could we please get a new function, say export-wait maxtime to wait for an export to finish for at maximal max-time seconds? If time exceeds max-time, then use

Re: Test wish for a new lfunc

Am Montag, 15. Januar 2018 um 12:55:00, schrieb Pavel Sanda > Kornel Benko wrote: > > Could we please get a new function, say > > export-wait maxtime > > to wait for an export to finish for at maximal max-time seconds? > > If time exceeds max-time, then use 'export-cancel'. > > if no backgroun

Re: Test wish for a new lfunc

Kornel Benko wrote: > Could we please get a new function, say > export-wait maxtime > to wait for an export to finish for at maximal max-time seconds? > If time exceeds max-time, then use 'export-cancel'. > if no background export in work, then it should be noop. I'd say export-wait [maxtime

Test wish for a new lfunc

Could we please get a new function, say export-wait maxtime to wait for an export to finish for at maximal max-time seconds? If time exceeds max-time, then use 'export-cancel'. if no background export in work, then it should be noop. Kornel signature.asc Description: This is a dig

Re: key bindings wish

Neal Becker writes: > True, but I'd still like a more introspective way to learn things, like > emacs has. What kind of introspective way? Through a lyxfunc? JMarc

Re: key bindings wish

Jean-Marc LASGOUTTES wrote: > Neal Becker writes: >> This morning I wanted to verify that C-sp was protected space. Couldn't >> find a way to get this info. > > You can see it in the insert->formatting menu. > > Moreover, the toolbar also shows the shortcuts. > > JMarc True, but I'd still lik

Re: key bindings wish

Pavel Sanda wrote: > but many are listed at all. are not p

Re: key bindings wish

Jean-Marc LASGOUTTES wrote: > Pavel Sanda writes: > > the document which should do the job is in Help->Shortcuts. > > however nobody maintains it (hint!) so its generally outdated. > > Doesn't it use the InsetInfo machinery? It should be reasonably up to > date. those which are written are up to

Re: key bindings wish

Neal Becker writes: > This morning I wanted to verify that C-sp was protected space. Couldn't > find a way to get this info. You can see it in the insert->formatting menu. Moreover, the toolbar also shows the shortcuts. JMarc

Re: key bindings wish

Pavel Sanda writes: > the document which should do the job is in Help->Shortcuts. > however nobody maintains it (hint!) so its generally outdated. Doesn't it use the InsetInfo machinery? It should be reasonably up to date. JMarc

Re: key bindings wish

On 09/03/2010 09:09 AM, Pavel Sanda wrote: Neal Becker wrote: One thing I enjoy with emacs is it has an introspection system to help me learn key bindings. I could as 'where is' the key binding, or simply list all the bindings. This morning I wanted to verify that C-sp was protected space.

Re: key bindings wish

Neal Becker wrote: > One thing I enjoy with emacs is it has an introspection system to help me > learn key bindings. > > I could as 'where is' the key binding, or simply list all the bindings. > > This morning I wanted to verify that C-sp was protected space. Couldn't > find a way to get this

key bindings wish

One thing I enjoy with emacs is it has an introspection system to help me learn key bindings. I could as 'where is' the key binding, or simply list all the bindings. This morning I wanted to verify that C-sp was protected space. Couldn't find a way to get this info.

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Sidharth Kshatriya wrote: > > I find the source code very lightly commented unfortunately. Even if every > > class had a 3-4 lines describing what it did, it would have been great. It > > would be wonderful if some more human commenting of each class were part of > > the goals of the 2.0 version.

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Thanks for your reply Richard. After reading your and Vincent's comments, I felt my questions relating to the DocIterator were well answered. Sure, I look forward to you suggesting enhancement features to implement. Thanks, Sidharth On Sun, Jun 13, 2010 at 11:16 PM, Richard Heck wrote: > On

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

On 06/13/2010 01:22 PM, Sidharth Kshatriya wrote: On Sun, Jun 13, 2010 at 9:58 PM, Vincent van Ravesteijn >wrote: Are you interested in implementing a certain feature ? If it's not too difficult, we can guide you and explain you the things you'll find on your roa

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

On Sun, Jun 13, 2010 at 9:58 PM, Vincent van Ravesteijn wrote: > Are you interested in implementing a certain feature ? If it's not too > difficult, we can guide you and explain you the things you'll find on your > road. It's indeed useful if you document it immediately. I myself have tried > to d

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

On 06/13/2010 11:13 AM, Sidharth Kshatriya wrote: I want to understand * What is the use of the inset_ member in the DocIterator class? Each CursorSlice has a link to its corresponding inset so what is the use of inset_ in the DocIterator class? I don't know this code terribly well, but I thi

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Op 13-6-2010 17:13, Sidharth Kshatriya schreef: I want to understand * What is the use of the inset_ member in the DocIterator class? Each CursorSlice has a link to its corresponding inset so what is the use of inset_ in the DocIterator class? I don't have a good answer, but if you create a D

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Thanks for you reply Amir. How familiar are you with the source code? Would be great to get your help on this. My skype id is sid.kshatriya and I'd be happy to speak to you and others in bringing out a document on LyX internals. There are so many free resources on Linux kernel programming and it

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Basically I want to understand how the diagram of http://wiki.lyx.org/Devel/Diagrams corresponds to the implementation. I have figured out that each CursorSlice relates to one node in the stack of parents upto the root InsetText but can't understand the role of inset_ in DocIterator. On Sun, Jun

Re: Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Hi, I'm pretty much at the same position as you are right now and if you want to join forces on the documentations I can offer my help with it. Though as I said, I'm also a newbie to the code (but not LyX, I've been using it for some time). Thanks, - Amir Rachum On Sun, Jun 13, 2010 at 6:13 PM,

Wish to understand DocIterator class + Willing to Volunteer to document LyX internals

Dear All, I'm a newbie to LyX and I'm currently trying to understand the source code. I'm very impressed by the WYSIWYM concept and I would like to be able to contribute to LyX one day. I find the source code very lightly commented unfortunately. Even if every class had a 3-4 lines describing wha

Re: wish: parallel build

"Mikhail T." writes: > Well, there is still lyx-1.5.7/src/frontends/qt4/ui/Makefile, which > means, the fix was, probably, never merged into 1.5.x (although back > then it was still a maintained branch). > Any hope for a fix now? Thanks! Yours, No, this will not happen now: the 1.5 branch is dead

Re: wish: parallel build

Jean-Marc Lasgouttes написав(ла): "Mikhail T." writes: That's a race condition... Any hope of seeing this fixed -- I'm fairly certain, 1.6.x has the same issue and that the fix will be applicable to 1.5.x as well. Thanks! Yours, I think this has been fixed with the following changeset

Re: wish: parallel build

"Mikhail T." writes: > That's a race condition... Any hope of seeing this fixed -- I'm fairly > certain, 1.6.x has the same issue and that the fix will be applicable > to 1.5.x as well. Thanks! Yours, I think this has been fixed with the following changeset, which removed ui/Makefile.am. I am not

Re: wish: parallel build

Mikhail T. wrote: Jean-Marc Lasgouttes wrote: LyX 1.5 and 1.6 can be built with -jx without problem. I do not know what is wrong with 1.4.5.1, but there is little (!) chance to see it fixed... JMarc I just had a report about failure of parallel build of LyX-1.5.7 -- the frontends/qt4/*.h fi

Re: wish: parallel build

Jean-Marc Lasgouttes wrote: LyX 1.5 and 1.6 can be built with -jx without problem. I do not know what is wrong with 1.4.5.1, but there is little (!) chance to see it fixed... JMarc I just had a report about failure of parallel build of LyX-1.5.7 -- the frontends/qt4/*.h files were being crea

I wish Track Change was implemented with Inset...

Because I would just have to implement Inset::addToToc() in order to have a full list of change accessible through the outline pane... food for thought :-) Abdel.

Re: wish: parallel build

Mikhail Teterin <[EMAIL PROTECTED]> writes: > Hello! > > I tried to do a parallel build of lyx-1.4.5.1 with > > gmake -j4 > > but it failed due to some race condition. With more and more computers having > multiple processors, it would be extremely useful to have all dependencies > properl

wish: parallel build

Hello! I tried to do a parallel build of lyx-1.4.5.1 with gmake -j4 but it failed due to some race condition. With more and more computers having multiple processors, it would be extremely useful to have all dependencies properly listed in the makefile so that make could perform such b

Re: UI wish/bug list

On Fri, Aug 03, 2007 at 04:39:51PM +0100, Stephen Cornell wrote: > If you want to warn the user that the document is not the clean version on > disk, perhaps a warning popup `The file is already open '. The user is > now out of danger... Well, not a dialog box - we don't want to force the user

Re: UI wish/bug list [Two math issues]

On 4 Aug 2007, at 20:14, Andre Poenitz wrote: On Fri, Aug 03, 2007 at 10:52:46PM +0300, Martin Vermeer wrote: On Fri, Aug 03, 2007 at 02:04:06PM -0400, Richard Heck wrote: Andre Poenitz wrote: On Fri, Aug 03, 2007 at 11:19:58AM -0400, Richard Heck wrote: This causes a lot of frustration t

Re: UI wish/bug list [Two math issues]

On Fri, Aug 03, 2007 at 10:52:46PM +0300, Martin Vermeer wrote: > On Fri, Aug 03, 2007 at 02:04:06PM -0400, Richard Heck wrote: > > Andre Poenitz wrote: > > > On Fri, Aug 03, 2007 at 11:19:58AM -0400, Richard Heck wrote: > > > > > >>> This causes a lot of frustration to me, because often I only

Re: UI wish/bug list [Two math issues]

On Sat, Aug 04, 2007 at 12:19:18AM -0400, Richard Heck wrote: > FYI: > http://bugzilla.lyx.org/show_bug.cgi?id=2543 I don't think this is the same bug. The bug that gets me worked up is, that after writing a one line formula, trying to append a second line by ctrl-enter will spread out pieces o

Re: UI wish/bug list [Two math issues]

FYI: http://bugzilla.lyx.org/show_bug.cgi?id=2543 Richard Heck wrote: Martin Vermeer wrote: On Fri, Aug 03, 2007 at 02:04:06PM -0400, Richard Heck wrote: Andre Poenitz wrote: On Fri, Aug 03, 2007 at 11:19:58AM -0400, Richard Heck wrote: This causes a lot of frustration to me,

Re: UI wish/bug list [Two math issues]

Martin Vermeer wrote: On Fri, Aug 03, 2007 at 02:04:06PM -0400, Richard Heck wrote: Andre Poenitz wrote: On Fri, Aug 03, 2007 at 11:19:58AM -0400, Richard Heck wrote: This causes a lot of frustration to me, because often I only decide that an equation has to be multi-line wh

Re: UI wish/bug list [Two math issues]

On Fri, Aug 03, 2007 at 02:04:06PM -0400, Richard Heck wrote: > Andre Poenitz wrote: > > On Fri, Aug 03, 2007 at 11:19:58AM -0400, Richard Heck wrote: > > > >>> This causes a lot of frustration to me, because often I only decide > >>> that an equation has to be multi-line when I'm already half-

Re: UI wish/bug list [Two math issues]

Andre Poenitz wrote: On Fri, Aug 03, 2007 at 11:19:58AM -0400, Richard Heck wrote: This causes a lot of frustration to me, because often I only decide that an equation has to be multi-line when I'm already half-way through typing it. When this happens, I have to type CMD-return, then CMD-z to

Re: UI wish/bug list [Two math issues]

On Fri, Aug 03, 2007 at 11:19:58AM -0400, Richard Heck wrote: > >This causes a lot of frustration to me, because often I only decide > >that an equation has to be multi-line when I'm already half-way > >through typing it. When this happens, I have to type CMD-return, then > >CMD-z to undo the creat

Re: UI wish/bug list [Two math issues]

On 3 Aug 2007, at 16:19, Richard Heck wrote: Stephen Cornell wrote: Position the cursor in a single-line equation. Press CMD-return Expected behaviour: create a new line, with all material before the cursor on the present line to remain on the current line, and all material after the curs

Re: UI wish/bug list

On Fri, Aug 03, 2007 at 04:39:51PM +0100, Stephen Cornell wrote: > If you want to warn the user that the document is not the clean > version on disk, perhaps a warning popup `The file is already open > '. The user is now out of danger... Worst of both worlds I think. I'm happy with either a

Re: UI wish/bug list

On 3 Aug 2007, at 16:14, Richard Heck wrote: I think it could be confusing to switch to a document that wasn't the same as the one on disk that you thought you were opening. I just checked: even emacs just switches to the already-edited version without comment. One of the guiding princip

Re: UI wish/bug list

John Levon wrote: On Fri, Aug 03, 2007 at 11:14:56AM -0400, Richard Heck wrote: John Levon wrote: On Fri, Aug 03, 2007 at 03:24:54PM +0100, Stephen Cornell wrote: I checked to see how other programs behave in this context, and Word, Pages, and NeoOffice simply switched to th

Re: UI wish/bug list

On Fri, Aug 03, 2007 at 11:14:56AM -0400, Richard Heck wrote: > John Levon wrote: > >On Fri, Aug 03, 2007 at 03:24:54PM +0100, Stephen Cornell wrote: > > > >>I checked to see how other programs behave in this context, and Word, > >>Pages, and NeoOffice simply switched to the already-open (and

Re: UI wish/bug list

John Levon <[EMAIL PROTECTED]> writes: > On Fri, Aug 03, 2007 at 03:24:54PM +0100, Stephen Cornell wrote: > >> `The document blah.lyx is already being edited. Do you want to >> discard your changes and re-read from disk? >> > > With the logic mentioned previously, I think this makes sense, but

Re: UI wish/bug list [Two math issues]

Stephen Cornell wrote: (2) Creating multi-line equations breaks the equation in a brain-dead place Position the cursor in a single-line equation. Press CMD-return Expected behaviour: create a new line, with all material before the cursor on the present line to remain on the current line, and a

Re: UI wish/bug list

John Levon wrote: On Fri, Aug 03, 2007 at 03:24:54PM +0100, Stephen Cornell wrote: I checked to see how other programs behave in this context, and Word, Pages, and NeoOffice simply switched to the already-open (and possibly edited) document without comment. Maybe that's the correct beha

Re: UI wish/bug list

On Fri, Aug 03, 2007 at 03:24:54PM +0100, Stephen Cornell wrote: > `The document blah.lyx is already being edited. Do you want to > discard your changes and re-read from disk? > With the logic mentioned previously, I think this makes sense, but Continue editing should be "Cancel" I think. >

Re: UI wish/bug list

On 3 Aug 2007, at 15:25, Richard Heck wrote: What if we did this: First, switch to the already open document; if the user wanted to open it, then she wants to switch to it, at least. Then check if it's dirty. If not, do nothing. If so, pop up a dialog that says something like, "The file [d

Re: UI wish/bug list

John Levon wrote: On Fri, Aug 03, 2007 at 02:57:43PM +0100, Stephen Cornell wrote: When trying to open a file which is already open in LyX, the user is confronted with `The document blah.lyx is already loaded. Do you want to revert to the saved version? .' `Switch' and `revert' are too a

Re: UI wish/bug list

John Levon wrote: On Fri, Aug 03, 2007 at 02:57:43PM +0100, Stephen Cornell wrote: When trying to open a file which is already open in LyX, the user is confronted with `The document blah.lyx is already loaded. Do you want to revert to the saved version? .' `Switch' and `revert' are to

Re: UI wish/bug list

On 3 Aug 2007, at 15:08, John Levon wrote: On Fri, Aug 03, 2007 at 02:57:43PM +0100, Stephen Cornell wrote: `The document blah.lyx is already open in LyX. Do you want to read the version saved on disk? document> .' Two problems: 1 - wording is too long for push buttons 2 - new descriptio

Re: UI wish/bug list

On Fri, Aug 03, 2007 at 02:57:43PM +0100, Stephen Cornell wrote: > When trying to open a file which is already open in LyX, the user is > confronted with `The document blah.lyx is already loaded. Do you > want to revert to the saved version? .' > > `Switch' and `revert' are too ambiguous -

UI wish/bug list

LyX is one of my favourite pieces of software, and for several years has made the business of documenting my research a relatively painless and even pleasurable experience. However, in spite of my immense gratitude to the LyX team, there are still a couple of aspects that cause me frustrat

[wish] Vowels (nikud) in Hebrew (and Arabic?)

Dov Feldstern wrote: I can tell you that isComposeChar_arabic and isComposeChar_hebrew are definitely wrong. They still assume the old encodings. Fixing them is easy, but tedious: You have to translate each explicit codepoint in src/encoding.C from the old encoding to ucs4. The old encodings a

Re: Wish: add newline after \begin{centering} and before \end{centering}

Juergen Spitzmueller <[EMAIL PROTECTED]> writes: > Gregor Gorjanc wrote: > > Gosh. I am surprised on license need for something so small. > > This is just our way to get you into the boat ;) > > Which 1.4.X will have this feature? > > The next one (1.4.4). Thank you again! Gregor

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc wrote: > Gosh. I am surprised on license need for something so small. This is just our way to get you into the boat :-) > Which 1.4.X will have this feature? The next one (1.4.4). Jürgen

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Sun, Dec 03, 2006 at 11:52:48PM +0100, Herbert Voss wrote: > Enrico Forestieri schrieb: > > On Sun, Dec 03, 2006 at 09:31:45PM +0100, Herbert Voss wrote: > > > >> no, do it without a caption ... There is no _correct_ way. > >> A command shouldn't be used as environemtn. That's correct. > >> In

Re: Wish: add newline after \begin{centering} and before \end{centering}

Enrico Forestieri schrieb: On Sun, Dec 03, 2006 at 09:31:45PM +0100, Herbert Voss wrote: no, do it without a caption ... There is no _correct_ way. A command shouldn't be used as environemtn. That's correct. Independant from that it works sometimes ... However, it is clearly documented in the

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Sun, Dec 03, 2006 at 09:31:45PM +0100, Herbert Voss wrote: > no, do it without a caption ... There is no _correct_ way. > A command shouldn't be used as environemtn. That's correct. > Independant from that it works sometimes ... However, it is clearly documented in the LaTeX book by Lamport th

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes schrieb: "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes: Herbert> Enrico Forestieri schrieb: Herbert, the two constructs are not equivalent. Herbert> I know, what I want to show is that it is not a good idea to Herbert> use a _command_ as an environment. The real

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes: Herbert> Enrico Forestieri schrieb: >> Herbert, the two constructs are not equivalent. Herbert> I know, what I want to show is that it is not a good idea to Herbert> use a _command_ as an environment. The real problem is that this comma

Re: Wish: add newline after \begin{centering} and before \end{centering}

Enrico Forestieri schrieb: Herbert, the two constructs are not equivalent. I know, what I want to show is that it is not a good idea to use a _command_ as an environment. This one: \begin{figure} \begin{centering} foo \end{centering} \caption{bar} \end{figure} corresponds to: \begin{figur

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes: Juergen> Jean-Marc Lasgouttes wrote: Adding a newline has no side Juergen> effects in this specific case AFAICS (and we already do that Juergen> for trivlist alignment), so I think this change could go in. >> Yes (in 1.4.X too)

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Sun, Dec 03, 2006 at 08:04:40PM +0100, Herbert Voss wrote: > Jean-Marc Lasgouttes schrieb: > > > I guess Herbert is balking at the use of centering as an environment. > > In my view, using > > \begin{centering}...\end{centering} > > is equivalent to the more traditional > > {\centering ..

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes schrieb: I guess Herbert is balking at the use of centering as an environment. In my view, using \begin{centering}...\end{centering} is equivalent to the more traditional {\centering ...} except that at least the first one is a proper markup. I agree nevertheless that

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc <[EMAIL PROTECTED]> writes: > Juergen Spitzmueller wrote: > > Juergen Spitzmueller wrote: > >>> Yes (in 1.4.X too) Which 1.4.X will have this feature? Thanks. Gregor

Re: Wish: add newline after \begin{centering} and before \end{centering}

Juergen Spitzmueller wrote: > Juergen Spitzmueller wrote: >>> Yes (in 1.4.X too) >> I'll do that. > > However, after testing Gregor's patch, I noticed that it adds some unneeded > blank lines after \end tags (where a linebreak occurs anyway). So I'll apply > the attached patch instead. Thank yo

Re: Wish: add newline after \begin{centering} and before \end{centering}

Juergen Spitzmueller wrote: > > Yes (in 1.4.X too) > > I'll do that. However, after testing Gregor's patch, I noticed that it adds some unneeded blank lines after \end tags (where a linebreak occurs anyway). So I'll apply the attached patch instead. Before I do this: Gregor, can you please post

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes wrote: > Juergen> Adding a newline has no side effects in this specific case > Juergen> AFAICS (and we already do that for trivlist alignment), so I > Juergen> think this change could go in. > > Yes (in 1.4.X too) I'll do that. Jürgen

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes: Juergen> Jean-Marc Lasgouttes wrote: >> I think it makes sense, but it needs careful checking. In >> particular, extra \n can create unwanted extra paragraphs in some >> cases. Juergen> Adding a newline has no side effects in thi

Re: Wish: add newline after \begin{centering} and before \end{centering}

Jean-Marc Lasgouttes wrote: > I think it makes sense, but it needs careful checking. In particular, > extra \n can create unwanted extra paragraphs in some cases. Adding a newline has no side effects in this specific case AFAICS (and we already do that for trivlist alignment), so I think this cha

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 05:05:55PM +0100, Jean-Marc Lasgouttes wrote: > Gregor> Sorry for ranting again. Can someone please "evaluate" my > Gregor> proposal. Should I file bug report, or, ... > > I think it makes sense, but it needs careful checking. In particular, > extra \n can create unwanted e

Re: Wish: add newline after \begin{centering} and before \end{centering}

>> I suppose you do not know the difference between >>> centering and > >> center >>>> First, I want to point out that this is the code output by LyX, >>> not > Gregor's doing. And I do not think that his particular >>> problem is > ab

Re: Wish: add newline after \begin{centering} and before \end{centering}

ce between >> centering and > >> center >> > >> > First, I want to point out that this is the code output by LyX, >> not > Gregor's doing. And I do not think that his particular >> problem is > about center vs centering. >> >> Any c

Re: Wish: add newline after \begin{centering} and before \end{centering}

his is the code output by LyX, not > > Gregor's doing. And I do not think that his particular problem is > > about center vs centering. > > Any comments on my wish and proposed patch? Sorry for ranting again. Can someone please "evaluate" my proposal. Should I file bug report, or, ... Thank you! Gregor

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 02:48:39PM +0100, Jean-Marc Lasgouttes wrote: > > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes: > > Enrico> Now, when \csname is used to define a command for the first > Enrico> time, this command is made equivalent to \relax until it is > Enrico> redefined.

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes: Enrico> Now, when \csname is used to define a command for the first Enrico> time, this command is made equivalent to \relax until it is Enrico> redefined. Ahh, I did not know that \csname...\endcsname could define the macro if it di

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 12:46:51PM +0100, Jean-Marc Lasgouttes wrote: > What I don't quite understand is that \endcentering does not exist (at > least I did not find its definition). This due to the way \begin and \end are defined: \def\begin#1{% [EMAIL PROTECTED] [EMAIL PROTECTED]@[EMAIL

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes: Enrico> On Fri, Dec 01, 2006 at 09:27:17AM +0100, Jean-Marc Lasgouttes Enrico> wrote: >> I guess Herbert is balking at the use of centering as an >> environment. In my view, using \begin{centering}...\end{centering} >> is equivalent t

Re: Wish: add newline after \begin{centering} and before \end{centering}

On Fri, Dec 01, 2006 at 09:27:17AM +0100, Jean-Marc Lasgouttes wrote: > I guess Herbert is balking at the use of centering as an environment. > In my view, using > \begin{centering}...\end{centering} > is equivalent to the more traditional > {\centering ...} > except that at least the first o

Re: Wish: add newline after \begin{centering} and before \end{centering}

d I do not think that his particular problem is > about center vs centering. Any comments on my wish and proposed patch? Gregor

Re: Wish: add newline after \begin{centering} and before \end{centering}

> "Gregor" == Gregor Gorjanc <[EMAIL PROTECTED]> writes: Gregor> Herbert Voss <[EMAIL PROTECTED]> writes: >> > That is the output if I center scrap (modified to allow that) >> environment: >> > >> > \begin{figure} > \begin{centering}<>= > >> boxplot(Sepal.Length~Species,data=iris) > \par\end

Re: Wish: add newline after \begin{centering} and before \end{centering}

Herbert Voss <[EMAIL PROTECTED]> writes: > > That is the output if I center scrap (modified to allow that) environment: > > > > \begin{figure} > > \begin{centering}<>= > > boxplot(Sepal.Length~Species,data=iris) > > \par\end{centering} > > > > > > \caption{bla bla} > > \end{figure} > > stupid

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc schrieb: > Gregor Gorjanc <[EMAIL PROTECTED]> writes: > >> Herbert Voss ...> writes: >>> you mean center, not centering ... >>> \centering is a macro and center an environment. >>> >> Whatever. LyX sometimes outputs centering otherwise center. > > That is the output if I center sc

Re: Wish: add newline after \begin{centering} and before \end{centering}

Gregor Gorjanc <[EMAIL PROTECTED]> writes: > > Herbert Voss ...> writes: > > you mean center, not centering ... > > \centering is a macro and center an environment. > > > > Whatever. LyX sometimes outputs centering otherwise center. That is the output if I center scrap (modified to allow that

Re: Wish: add newline after \begin{centering} and before \end{centering}

Herbert Voss <[EMAIL PROTECTED]> writes: > you mean center, not centering ... > \centering is a macro and center an environment. > Whatever. LyX sometimes outputs centering otherwise center. Gregor

  1   2   3   >