Le 13/07/2012 00:24, Pavel Sanda a écrit :
Richard Heck wrote:
This leads to the harmless message above, but more importantly, it means
that the undo stack is lost every time a file is saved-as. This looks like
a regression to me.
Richard, would it seem right to add a parameter to
Le 12/07/2012 18:14, Richard Heck a écrit :
Richard, would it seem right to add a parameter to Buffer::reload
asking to preserve the undo stack in this case?
You would probably know better than I do. Are there pointers on the undo
stack that will be invalidated once we reload?
The undo stack
On 2012-07-12, Ronen Abravanel wrote:
as the Hebrew support of LaTeX is not developed for the last several
years, I decided to try and export Hebrew document to PDF using XeTeX,
Are there problems that did not get solved for years, or is there no
development because it just works?
where the
On 07/13/2012 03:47 AM, Jean-Marc Lasgouttes wrote:
Le 13/07/2012 00:24, Pavel Sanda a écrit :
Richard Heck wrote:
This leads to the harmless message above, but more importantly, it
means
that the undo stack is lost every time a file is saved-as. This
looks like
a regression to me.
Richard,
1. you are right. one can do that, and it would be a nice workaround. But I
prefer lyx will produce clean TeX file.
2. Attached some examples:
the text in the *xetex and *pdf files are identical. in the pdf, you can
see that the braces are rendered backword, and also if you will open the
.tex
Jean-Marc Lasgouttes wrote:
You mean to preserve undo stack for each reload of file or just for save-as
scenario? We also reload automatically after commit/checkout VCS operation
which can change read-only status.
This is why I propose to add a parameter to reload telling whether undo
should
From: Jean-Marc Lasgouttes [lasgout...@lyx.org]
Sent: Thursday, July 12, 2012 5:20 AM
I think theargument flag is not flexible enough to be useful.
ok.
In the meantime, it would not hurt to fix one by one the examples you
gave (in getStatus). Returning meaningful error messages when getStatus
Scott Kostyshak wrote:
In the meantime, it would not hurt to fix one by one the examples you
gave (in getStatus). Returning meaningful error messages when getStatus
disables a function would make sense too.
ok, I will look into this later if no ones else does.
Be sure no one else will do ;)
From: Pavel Sanda [sa...@lyx.org]
Sent: Friday, July 13, 2012 4:43 PM
Scott Kostyshak wrote:
In the meantime, it would not hurt to fix one by one the examples you
gave (in getStatus). Returning meaningful error messages when getStatus
disables a function would make sense too.
ok, I will look
Am 13.07.2012 03:33, schrieb Maaneli D:
First, although the graph shows up on the PDF, I'm not sure how to format it
such that I can center the graph, or move it in different places.
In the file you sent me, you inserted the image in the figure caption. Move it out of the caption
and it
Le 13/07/2012 00:24, Pavel Sanda a écrit :
Richard Heck wrote:
This leads to the harmless message above, but more importantly, it means
that the undo stack is lost every time a file is saved-as. This looks like
a regression to me.
Richard, would it seem right to add a parameter to
Le 12/07/2012 18:14, Richard Heck a écrit :
Richard, would it seem right to add a parameter to Buffer::reload
asking to preserve the undo stack in this case?
You would probably know better than I do. Are there pointers on the undo
stack that will be invalidated once we reload?
The undo stack
On 2012-07-12, Ronen Abravanel wrote:
> as the Hebrew support of LaTeX is not developed for the last several
> years, I decided to try and export Hebrew document to PDF using XeTeX,
Are there problems that did not get solved for years, or is there no
development because it "just works"?
> where
On 07/13/2012 03:47 AM, Jean-Marc Lasgouttes wrote:
Le 13/07/2012 00:24, Pavel Sanda a écrit :
Richard Heck wrote:
This leads to the harmless message above, but more importantly, it
means
that the undo stack is lost every time a file is saved-as. This
looks like
a regression to me.
Richard,
1. you are right. one can do that, and it would be a nice workaround. But I
prefer lyx will produce clean TeX file.
2. Attached some examples:
the text in the *xetex and *pdf files are identical. in the pdf, you can
see that the braces are rendered backword, and also if you will open the
.tex
Jean-Marc Lasgouttes wrote:
>> You mean to preserve undo stack for each reload of file or just for save-as
>> scenario? We also reload automatically after commit/checkout VCS operation
>> which can change read-only status.
>
> This is why I propose to add a parameter to reload telling whether undo
From: Jean-Marc Lasgouttes [lasgout...@lyx.org]
Sent: Thursday, July 12, 2012 5:20 AM
>I think theargument flag is not flexible enough to be useful.
ok.
>In the meantime, it would not hurt to fix one by one the examples you
>gave (in getStatus). Returning meaningful error messages when
Scott Kostyshak wrote:
> >In the meantime, it would not hurt to fix one by one the examples you
> >gave (in getStatus). Returning meaningful error messages when getStatus
> >disables a function would make sense too.
>
> ok, I will look into this later if no ones else does.
Be sure no one else
From: Pavel Sanda [sa...@lyx.org]
Sent: Friday, July 13, 2012 4:43 PM
Scott Kostyshak wrote:
>> >In the meantime, it would not hurt to fix one by one the examples you
>> >gave (in getStatus). Returning meaningful error messages when getStatus
>> >disables a function would make sense too.
>>
>>
Am 13.07.2012 03:33, schrieb Maaneli D:
First, although the graph shows up on the PDF, I'm not sure how to format it
such that I can center the graph, or move it in different places.
In the file you sent me, you inserted the image in the figure caption. Move it out of the caption
and it
20 matches
Mail list logo