On Mon, Jul 18, 2011 at 7:17 AM, Enrico Forestieri wrote:
> On Sun, Jul 17, 2011 at 06:49:43PM +0800, John McCabe-Dansted wrote:
>
>> It seems that this code should only be called if the math inset has
>> actually been modified, but that it is being called constantly, even
>> on cursor movement ou
On Sun, Jul 17, 2011 at 06:49:43PM +0800, John McCabe-Dansted wrote:
> It seems that this code should only be called if the math inset has
> actually been modified, but that it is being called constantly, even
> on cursor movement outside the math inset.
Does the attached patch help? However, I d
On Fri, Jul 15, 2011 at 9:17 PM, Pavel Sanda wrote:
> Diego Queiroz wrote:
> > Do we need to figure a "label"? What are we talking about? Are we talking
> > about the bullet? the number? or really a label?
>
> it can be bullet (or others characters when deeper structure is used) or
> the number.
-Opprinnelig melding-
Fra: lyx-devel@lists.lyx.org på vegne av Uwe Stöhr
Sendt: to 7/14/2011 4:47
Til: sa...@lyx.org
Kopi: LyX-Devel
Emne: Re: Towards RC4/final release
[...]
>I added this module after a discussion. We came to the conclusion that a
>module is perhaps not the
>best UI
Uwe Stöhr wrote:
> So give me some more hours please.
no problem, just was not sure if its not overlooked... p
John McCabe-Dansted wrote:
> I have finally exercised my commit privileges by committing r39333. I
> spent an hours checking everything is OK, but this is my first commit
> ever to a shared VCS... so expect a rain of fire.
everything seems fine.
> Also, is this OK for branch? Should I commit ther
Uwe Stöhr wrote:
> The author of the change is "cmd". Who is that? Can we please use usernames
> where it is clear who is it?
care to read devel list? :)
just one message previous to yours.
John was given commit access together with Julien, but had no oportunity
to commit yet.
pavel
Am 17.07.2011 12:10, schrieb Pavel Sanda:
btw is it intended that new 8.4 paragraph in additional manual is completely in
german? p
Yes, I merged it from the German version to the English one and are translating it right now. I btw.
also update sec.8.3 with your lettrine support feature.
S
The author of the change is "cmd". Who is that? Can we please use usernames
where it is clear who is it?
regards Uwe
I seem to remember that I had recently changed a label in a document
with several children and the references in other children have
automatically been updated correctly.
However, even if updating across children works at all times, there
would be pitfalls in co-authored docuements. For insta
I have finally exercised my commit privileges by committing r39333. I
spent an hours checking everything is OK, but this is my first commit
ever to a shared VCS... so expect a rain of fire.
Also, is this OK for branch? Should I commit there as well?
If so, to do that I just check out branch, reap
Is it more convenient if I include the patch that caused the
regression in my email, if it is small, as below?
It seems that this code should only be called if the math inset has
actually been modified, but that it is being called constantly, even
on cursor movement outside the math inset.
--
On Tue, May 24, 2011 at 12:34 PM, John McCabe-Dansted wrote:
> To reproduce:
> 1) Open a complex lyx file with many math insets, macros etc. (e.g.
> http://www.csse.uwa.edu.au/~john/drafts/Thesis_Background.lyx, or just
> create a new document and fill the screen with "$x$ x", where $x$
> represe
Pavel Sanda wrote:
> i have some vague feeling that its even
> possible to have document which has set master although master is not aware
> of it? then this automatic bussiness would spoil references.
Yes. And also with xr.sty, things will become difficult to maintain.
Jürgen
Uwe Stöhr wrote:
> Am 16.07.2011 18:32, schrieb Richard Heck:
>
>> I'm not sure this is really a good idea. I
>> worry that there are too many cases where a label would be changed
>> incorrectly, or not changed.
>
> For example? I also thought about this but no case comes into my mind where
> this
Richard Heck wrote:
> What I meant was: I want to make a
> minor modification to what I just committed, not to the log message. So,
> e.g., I notice a typo in the doxy for my new routine, so I fix that. Then I
untested, but something like
git add corrected_file; git commit --amend
should help.
16 matches
Mail list logo