On Tue, Dec 4, 2012 at 8:21 PM, Nico Williams wrote:
> It'd also be nice to be able to define a filter that must be applied
> before rendering. Such a filter might convert metadata into LyX
> directives, thus pre-rendering said metadata.
>
Did you look into the possibility of adding a new file fo
Never mind. I really had to define LabelStrings for all my insets,
and then View->Open All Insets was enough. And apparently they are
inserted open anyways. I've closed the ticket I opened for this.
On Tue, Dec 4, 2012 at 12:56 PM, Jean-Marc Lasgouttes
wrote:
> Le 04/12/2012 19:53, Jürgen Spitzmüller a écrit :
>> You are talking about "conglomerate"-style flex insets, right?
>> Currently, they are always inserted "collapsed" and you need to
>> manually uncollapse them. We could introduce a la
It'd be nice to have a custom inset type just for metadata, that is,
one that doesn't get rendered.
It'd also be nice to be able to define a filter that must be applied
before rendering. Such a filter might convert metadata into LyX
directives, thus pre-rendering said metadata.
I'll file a reque
2012/12/4 Jean-Marc Lasgouttes :
> Or we could always insert them opened.
I would not object.
Jürgen
> JMarc
>
Le 04/12/2012 19:53, Jürgen Spitzmüller a écrit :
2012/12/4 Nico Williams :
Now, I notice that there's a LabelString parameter for custom insets,
but I don't see how to have that label string appear in the UI. Oh,
well, I notice that there's right click menu item for showing the
label -- I just
2012/12/4 Nico Williams :
> Now, I notice that there's a LabelString parameter for custom insets,
> but I don't see how to have that label string appear in the UI. Oh,
> well, I notice that there's right click menu item for showing the
> label -- I just want the labels for my custom insets display
I'm using custom insets to represent various metadata. The problem I
run into is that there's no way in the LyX display to see what each
inset is. If I click inside such an inset the layout is shown as
plain -- nothing in the UI shows the inset type.
In some cases I'm resorting to using param=va
Le 04/12/2012 19:42, Nico Williams a écrit :
Ideally the syntax should be something like: lyx --merge --out=doc3
doc1 doc2, and the result should be a merged document with change
tracking so that the user can do all semantic merging. In this mode
LyX should not open a window nor require user int
Ideally the syntax should be something like: lyx --merge --out=doc3
doc1 doc2, and the result should be a merged document with change
tracking so that the user can do all semantic merging. In this mode
LyX should not open a window nor require user interaction, as the idea
is to use this as a merge
Le 04/12/2012 19:32, Liviu Andronic a écrit :
On Tue, Dec 4, 2012 at 7:30 PM, Jean-Marc Lasgouttes wrote:
Unfortunately, it seems that there is no lfun to do that. The only one is
vc-compare, which compares documents already in version control.
Is it worth filing a feature request on bug trac
On Tue, Dec 4, 2012 at 7:30 PM, Jean-Marc Lasgouttes wrote:
> Unfortunately, it seems that there is no lfun to do that. The only one is
> vc-compare, which compares documents already in version control.
>
Is it worth filing a feature request on bug tracker?
Liviu
Le 04/12/2012 18:10, Nico Williams a écrit :
What would the exact command-line invocation be?
Unfortunately, it seems that there is no lfun to do that. The only one
is vc-compare, which compares documents already in version control.
JMarc
On 12/04/2012 11:09 AM, Jürgen Spitzmüller wrote:
> Christoph Burschka wrote:
>> The two modules require one of Theorems or Theorems (AMS), and conflict
>> only with each other. Still I wasn't able to enable either of them in
>> the document. Is this a bug?
>
> All I can say is that this is also t
What would the exact command-line invocation be?
Nico
--
On 2012-12-04, Leslaw Bieniasz wrote:
> Hi,
> I have checked my MikTeX files, and I see that the isomath package is
> probably already there (there are directories \source, \doc]latex,
> \tex\latex, tmp\packages, doc\latex\isomath, all in c:\Program
> Files\MikTeX 2.0 ). I also have the access to
On 2012-11-25 16:53, David L. Johnson wrote:
> My students would testify that many of my notes are far, far more than
> 8-12 months old when I open and "revise" them for the current term,
> and this has never happened to me [except on very, very old files
> whose format is no longer supported direc
Christoph Burschka wrote:
> The two modules require one of Theorems or Theorems (AMS), and conflict
> only with each other. Still I wasn't able to enable either of them in
> the document. Is this a bug?
All I can say is that this is also the case in LyX 2.0.5 and that
BufferParams::moduleCanBeAdd
Hi,
I have checked my MikTeX files, and I see that the isomath package is probably
already there (there are directories \source, \doc]latex, \tex\latex,
tmp\packages, doc\latex\isomath, all in c:\Program Files\MikTeX 2.0 ).
I also have the access to the \mathbf fonts from the level of LyX.
Howev
Le 04/12/2012 09:22, Liviu Andronic a écrit :
On Tue, Dec 4, 2012 at 9:06 AM, Jean-Marc Lasgouttes wrote:
Have you looked into Document > Track Changes?
The problem is probably to see how to invoke that from command line.
Good question. Theoretically is it possible to diff two LyX documents
On Tue, Dec 4, 2012 at 9:06 AM, Jean-Marc Lasgouttes wrote:
>> Have you looked into Document > Track Changes?
>
> The problem is probably to see how to invoke that from command line.
>
Good question. Theoretically is it possible to diff two LyX documents
using the --execute CLI argument?
Liviu
Le 04/12/2012 08:41, Liviu Andronic a écrit :
On Mon, Dec 3, 2012 at 6:44 PM, Nico Williams wrote:
I'd like to use LyX + git (or some such VCS) to cooperatively edit
documents. This requires a diff/merge tool that is LyX-aware and can
result in LyX documents that contain diffs that users can m
22 matches
Mail list logo
