On 24.11.08, rgheck wrote:
> G. Milde wrote:
>> The attached module enables resuming an enumeration with the new
>> Enumerate-Resume style. See the example file for usage details.
> Question (in case you already know): What happens if the user chooses
> this environment without a previous Enumer
G. Milde wrote:
The attached module enables resuming an enumeration with the new
Enumerate-Resume style. See the example file for usage details.
I'll test this later, but I have to say, this is a very nice solution to
this problem, rather than having to mess with something in the code itself
The attached module enables resuming an enumeration with the new
Enumerate-Resume style. See the example file for usage details.
It also allows customising base lists with optional arguments
(Still to be found under Einfügen>Kurztitel.)
> Why not use a different Style for a "resuming enumeration"
On 21.11.08, Jean-Marc Lasgouttes wrote:
> Guenter Milde <[EMAIL PROTECTED]> writes:
> > I wonder whether it would be better to put the "intelligence" into lyx:
> >
> > let lyx compute the start number of a resumed enumeration and use this to
> > set the label and the correct `enum*' counter.
> I
Vincent van Ravesteijn wrote:
Currently I added the resume AND suspend bools to the first paragraph
of an environment. In principle, all paragraphs within an environment
should have these parameters set. Now, cutting an enumeration (that is
resumed later) in half would result in the first one b
Guenter Milde <[EMAIL PROTECTED]> writes:
> I wonder whether it would be better to put the "intelligence" into lyx:
>
> let lyx compute the start number of a resumed enumeration and use this to
> set the label and the correct `enum*' counter.
I would not do that, since we are not sure enough that
Vincent van Ravesteijn wrote:
rgheck schreef:
Just some random thoughts looking quickly. Suppose resumeEnumeration
is on, and then I change the layout to, say, LyX list. What happens?
I guess, in the abstract, I have general worries about how this will
behave under such changes.
Yes, these
Guenter Milde wrote:
Anyway, I could imagine the "resume last" option to be part of a
selection list:
Enumeration counter [*] start new
[ ] continue previous
[ ] start with []
With the * indicating the (backwards/LaTeX compatible) default settin
Vincent van Ravesteijn schrieb:
>> The biggest problem I have with this is that, since you add the suspend
>> flag automatically, the mechanism is very fragile.
...
> Another possibility is to remove the suspend variable completely, making
> it more robust. But then, we should search for a res
Vincent van Ravesteijn <[EMAIL PROTECTED]> writes:
> Another possibility is to remove the suspend variable completely,
> making it more robust. But then, we should search for a resuming
> enumeration in the document everytime we generate the latex code,
> which won't be fun working on a large docum
rgheck schreef:
Just some random thoughts looking quickly. Suppose resumeEnumeration
is on, and then I change the layout to, say, LyX list. What happens? I
guess, in the abstract, I have general worries about how this will
behave under such changes.
Yes, these are valid worries. See below.
Jü
Vincent van Ravesteijn <[EMAIL PROTECTED]> writes:
> Is anybody willing to review and/or try this patch ?
The biggest problem I have with this is that, since you add the suspend
flag automatically, the mechanism is very fragile. What if you copy the
second enumeration in front of the other? What i
rgheck wrote:
> It is supposed to be UI policy that things on context menus have to
> exist elsewhere, too. So we'd have to figure out where to put this.
Yes. Furthermore, this is a file format change.
Jürgen
Vincent van Ravesteijn wrote:
Dear All,
Lately, I see often questions about the interrupted enumeration
problem at the User's list. Therefore I implemented a context menu
item that will make it possible to let an enumeration resume a
previous one.
Is anybody willing to review and/or try thi
14 matches
Mail list logo
