On Sat, Mar 14, 2020 at 09:46:22AM +0100, Jürgen Spitzmüller wrote:
> Am Freitag, den 13.03.2020, 16:45 +0100 schrieb Jürgen Spitzmüller:
> > A major problem with this is that it breaks
> >
> > 1. children stand-alone compiling if they have references to siblings
> > or their master
> >
> > 2. mu
> On Mar 14, 2020, at 08:39, Jürgen Spitzmüller wrote:
>
> Am Samstag, den 14.03.2020, 08:25 -0600 schrieb Joel Kulesza:
>> One thing that's been on my mind for a while is coloring the broken
>> elements differently than default; however, it was not clear to me
>> how to achieve that in a stra
Am Samstag, den 14.03.2020, 08:25 -0600 schrieb Joel Kulesza:
> One thing that's been on my mind for a while is coloring the broken
> elements differently than default; however, it was not clear to me
> how to achieve that in a straightforward way.
I've done this as well. See
https://www.lyx.org/t
On Sat, Mar 14, 2020 at 8:19 AM Jürgen Spitzmüller wrote:
> Am Samstag, den 14.03.2020, 14:29 +0100 schrieb Daniel:
> > > How about a dedicated outliner entry "Broken citations and
> > > references"?
> > > This would be easiest to implement, and it would give you both a
> > > quick
> > > report a
Am Samstag, den 14.03.2020, 14:29 +0100 schrieb Daniel:
> > How about a dedicated outliner entry "Broken citations and
> > references"?
> > This would be easiest to implement, and it would give you both a
> > quick
> > report and the possibility to navigate to the broken insets
> > quickly.
> >
>
Am Samstag, den 14.03.2020, 14:29 +0100 schrieb Daniel:
> Yes, I think that would be helpful. In particular if some broken
> references would be classified as such that currently aren't. For
> example, visible references to hidden labels
> (https://www.lyx.org/trac/ticket/11782).
This seems to
On 2020-03-14 11:20, Jürgen Spitzmüller wrote:
Am Samstag, den 14.03.2020, 10:04 +0100 schrieb Daniel:
Great. (Just for reference: This was part of the suggestions of the
rest
of my post.) I think that would be helpful.
I know. I just cut it for readability.
However, depending on how large t
Am Samstag, den 14.03.2020, 10:04 +0100 schrieb Daniel:
> Great. (Just for reference: This was part of the suggestions of the
> rest
> of my post.) I think that would be helpful.
I know. I just cut it for readability.
> However, depending on how large the document and how many sub-
> documents
On 2020-03-14 09:32, Jürgen Spitzmüller wrote:
Am Samstag, den 14.03.2020, 09:13 +0100 schrieb Daniel:
For me, incorrect references are basically the only point where
using
LyX/LaTeX is worse than a WYSIWYG word processor because in the
letter
you are able to more easily spot them in context. Br
Am Freitag, den 13.03.2020, 16:45 +0100 schrieb Jürgen Spitzmüller:
> A major problem with this is that it breaks
>
> 1. children stand-alone compiling if they have references to siblings
> or their master
>
> 2. multi-part documents compiled with "includeonly" and "maintain
> counters and refere
Am Samstag, den 14.03.2020, 09:13 +0100 schrieb Daniel:
> For me, incorrect references are basically the only point where
> using
> LyX/LaTeX is worse than a WYSIWYG word processor because in the
> letter
> you are able to more easily spot them in context. Broken and wrongly
> formatted referenc
On 2020-03-13 17:31, Jürgen Spitzmüller wrote:
Am Freitag, den 13.03.2020, 17:11 +0100 schrieb Daniel:
I am not sure what you mean by "defunc'ed", but doesn't the patch
"let
users see the results anyway"?
Yes, but if you have clicked this each time you want to update your
preview for only a fe
Am Freitag, den 13.03.2020, 17:11 +0100 schrieb Daniel:
> I am not sure what you mean by "defunc'ed", but doesn't the patch
> "let
> users see the results anyway"?
Yes, but if you have clicked this each time you want to update your
preview for only a few times, you'll see that this is not a worka
On 2020-03-13 16:45, Jürgen Spitzmüller wrote:
Am Freitag, den 07.06.2019, 17:05 +0200 schrieb Pavel Sanda:
commit bf99ece7366ad479458b3cecb067341a3320286a
Author: Pavel Sanda
Date: Fri Jun 7 16:47:04 2019 +0200
Start reporting missing citations and broken references in LaTeX
build.
Am Freitag, den 07.06.2019, 17:05 +0200 schrieb Pavel Sanda:
> commit bf99ece7366ad479458b3cecb067341a3320286a
> Author: Pavel Sanda
> Date: Fri Jun 7 16:47:04 2019 +0200
>
> Start reporting missing citations and broken references in LaTeX
> build.
>
> Now we report these in the sa
On Mon, Sep 09, 2019 at 03:45:54PM -0700, Pavel Sanda wrote:
> On Sun, Sep 08, 2019 at 12:56:44PM -0400, Scott Kostyshak wrote:
> > 1. Would it be more efficient to use "prefixIs()" instead of
> > "contains()"? Are you concerned that for some older versions there is
> > white space at the beginning
On Sun, Sep 08, 2019 at 12:56:44PM -0400, Scott Kostyshak wrote:
> 1. Would it be more efficient to use "prefixIs()" instead of
> "contains()"? Are you concerned that for some older versions there is
> white space at the beginning of the line? Since this is a new feature,
I'm not sure what exact l
On Fri, Jun 07, 2019 at 05:05:20PM +0200, Pavel Sanda wrote:
> commit bf99ece7366ad479458b3cecb067341a3320286a
> Author: Pavel Sanda
> Date: Fri Jun 7 16:47:04 2019 +0200
>
> Start reporting missing citations and broken references in LaTeX build.
>
> Now we report these in the same
18 matches
Mail list logo
