Richard Heck <[EMAIL PROTECTED]> writes:
> For this reason, name() seems to be used for pretty various things,
> and all of that would need sorting out. So, if it's OK, I'll put
> some FIXMEs in the right places for now, and come back to it once
> I've finished sorting out the InsetCommand stuff.
Jean-Marc Lasgouttes wrote:
Richard Heck <[EMAIL PROTECTED]> writes:
But of course I can change all the inset names to uppercase, if you'd
prefer. Let me know which. One or the other should be done.
I prefer lowercase personally. I think the capitalized version is
intended to look goo
Richard Heck <[EMAIL PROTECTED]> writes:
> But of course I can change all the inset names to uppercase, if you'd
> prefer. Let me know which. One or the other should be done.
I prefer lowercase personally. I think the capitalized version is
intended to look goo in the GUI.
> Note that, since th
Jean-Marc Lasgouttes wrote:
Richard Heck <[EMAIL PROTECTED]> writes:
The attached patch accomplishes the first part of the plan discussed
here earlier, under InsetCommand[Params], the goal being to
disentangle the type of an inset from the (LaTeX) command it
represents. This patch reworks how
Richard Heck <[EMAIL PROTECTED]> writes:
> The attached patch accomplishes the first part of the plan discussed
> here earlier, under InsetCommand[Params], the goal being to
> disentangle the type of an inset from the (LaTeX) command it
> represents. This patch reworks how InsetCommands are repres
The attached patch accomplishes the first part of the plan discussed
here earlier, under InsetCommand[Params], the goal being to disentangle
the type of an inset from the (LaTeX) command it represents. This patch
reworks how InsetCommands are represented in LyX files, laying the
foundation fo