On 2011-09-08, Richard Heck wrote:
On 09/08/2011 01:57 PM, Julien Rioux wrote:
On 08/09/2011 7:34 PM, Tommaso Cucinotta wrote:
Hi,
would it be possible to add to LyX the possibility to specify an
explicit output file-name when exporting from the command-line to a
different format ?
Am 08.09.2011 um 22:01 schrieb Richard Heck:
On 09/08/2011 01:57 PM, Julien Rioux wrote:
On 08/09/2011 7:34 PM, Tommaso Cucinotta wrote:
Hi,
would it be possible to add to LyX the possibility to specify an
explicit output file-name when exporting from the command-line to a
different
On 05. sep. 2011 08:49, Jean-Pierre Chrétien wrote:
[...]
After investigation, this error is due to the fact that the word
'Flottants' is in French in the index inset within title of section
4.6.3. The exported latex construct
\subsection{More
On 29. aug. 2011 13:24, Pavel Sanda wrote:
Helge Hafting wrote:
I just noticed that LyX 2.0 (and 2.0.1svn) fail to open files that contain
xfig graphics.
did it work in 1.6? can you create new bug and attach example file with
.fig file?
The bug mysteriously disappeared. I guess it had
Helge Hafting wrote:
We see that selectlanguage inside an index entry cause trouble.
Therefore, LyX should not emit language change commands inside index
entries. This is probably not necessary either - an index entry will
not be hyphenated so language support is not needed there.
Unless you
Il 09/09/2011 08:10, Guenter Milde ha scritto:
Presumably what is needed here is a buffer-export-as LFUN.
or I don't know if one can add an optional argument to the same
buffer-export LFUN, i.e.:
Alt-x buffer-export ps
Alt-x buffer-export ps /tmp/foo.ps
... as implemented in the
Il 09/09/2011 08:29, Stephan Witt ha scritto:
Am 08.09.2011 um 22:01 schrieb Richard Heck:
On 09/08/2011 01:57 PM, Julien Rioux wrote:
new switch, say, -E, which takes two arguments, and have that act as
shorthand for:
-x buffer-export-as pdf /path/to/export.lyx
What about spaces in path
I tried building with cmake yesterday. A few observations.
Compiling from scratch went faster than autoconf.
From INSTALL.cmake I though that
-DLYX_PACKAGE_SUFFIX=-devel
would be the equivalent of
--with-version-suffix=-devel
under autoconf. But my LyX built by cmake uses ~/.lyx2.1/ as the
Le 09/09/2011 12:50, Tommaso Cucinotta a écrit :
in the patch I sent a few minutes ago, we have this working:
-x buffer-export latex /path/to/file name with space.tex
Would it be ok for people used to paths with spaces (guess mostly Win
users) ?
Perosnally, I'd prefer to avoid this syntax of
Le 09/09/2011 14:24, Julien Rioux a écrit :
under autoconf. But my LyX built by cmake uses ~/.lyx2.1/ as the user
directory instead of ~/.lyx-devel/ as I expected. This might be a wrong
configuration on my part.
I would have expected that also.
Nevertheless, it would be good to have it
I am going to try scons today and report back.
Scons is going to be dropped some time from now. So you might want to
spend your time in a more useful way.
Vincent
On 09/08/2011 09:10 PM, Lisa Andrews wrote:
I understand that it is not possible to insert a footnote inside a footnote.
However, I notice that it is possible to insert a footnote inside a
footnote if it is inside a branch.
The pdf output does not show the contents of such nested footnotes,
but
Hi,
I've been building LyX RPMs from the SVN source for a while now, but I don't
know how to compile things so that installing the RPM automatically produces
a LyX desktop shortcut for Gnome, the way the officially supported RPM
package does. What precise additional steps do I need to perform?
On 09/09/2011 2:34 PM, Vincent van Ravesteijn wrote:
I am going to try scons today and report back.
Scons is going to be dropped some time from now. So you might want to
spend your time in a more useful way.
Vincent
I see. Good to know, thanks. The build failed but anyway there's not
On 09/09/2011 09:28 AM, Jacob Barandes wrote:
Hi,
I've been building LyX RPMs from the SVN source for a while now, but I
don't know how to compile things so that installing the RPM
automatically produces a LyX desktop shortcut for Gnome, the way the
officially supported RPM package does.
Le 09/09/2011 15:31, Richard Heck a écrit :
On 09/09/2011 09:28 AM, Jacob Barandes wrote:
I've been building LyX RPMs from the SVN source for a while now, but I
don't know how to compile things so that installing the RPM
automatically produces a LyX desktop shortcut for Gnome, the way the
Am 09.09.2011 um 15:45 schrieb Jean-Marc Lasgouttes:
Le 09/09/2011 15:31, Richard Heck a écrit :
On 09/09/2011 09:28 AM, Jacob Barandes wrote:
I've been building LyX RPMs from the SVN source for a while now, but I
don't know how to compile things so that installing the RPM
automatically
Le 09/09/2011 15:51, Stephan Witt a écrit :
This problem is tracked at http://www.lyx.org/trac/ticket/2820
and the outcome is that we do not really know how this stuff works :)
Really? I'm building our own software RPMs with desktop icon setup.
I can have a look later... if nobody steps up.
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Le 09/09/2011 12:50, Tommaso Cucinotta a écrit :
in the patch I sent a few minutes ago, we have this working:
-x buffer-export latex /path/to/file name with space.tex
Would it be ok for people used to paths with spaces (guess mostly Win
Il 09/09/2011 19:45, Tommaso Cucinotta ha scritto:
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Perosnally, I'd prefer to avoid this syntax of 'everything until the
end of line', and stick with the good old
-x buffer-export latex \/path/to/file name with space.tex\
which LyX should
On 09/09/2011 02:57 PM, Tommaso Cucinotta wrote:
Il 09/09/2011 19:45, Tommaso Cucinotta ha scritto:
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Perosnally, I'd prefer to avoid this syntax of 'everything until the
end of line', and stick with the good old
-x buffer-export latex
Am 09.09.2011 um 19:45 schrieb Tommaso Cucinotta:
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Le 09/09/2011 12:50, Tommaso Cucinotta a écrit :
in the patch I sent a few minutes ago, we have this working:
-x buffer-export latex /path/to/file name with space.tex
Would it be ok
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
This is a better syntax, isn't it? It's still possible. When you call
Am 09.09.2011 um 21:50 schrieb Stephan Witt:
There's not only this problem.
There is no way to stop e. g. LFUN_FILE_OPEN from substituting the variable
in /tmp/path/to/the$variable/filename.lyx ...
So one cannot have a dollar sign in file names. And since it's used
internally too it
On 09/09/2011 9:51 PM, Julien Rioux wrote:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
This is a better syntax, isn't it? It's
On 09/09/2011 10:24 PM, Julien Rioux wrote:
On 09/09/2011 9:51 PM, Julien Rioux wrote:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
Il 09/09/2011 22:32, Julien Rioux ha scritto:
On 09/09/2011 10:24 PM, Julien Rioux wrote:
On 09/09/2011 9:51 PM, Julien Rioux wrote:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e
Il 09/09/2011 21:51, Julien Rioux ha scritto:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
This is a better syntax, isn't it?
On 09/09/2011 02:57 PM, Tommaso Cucinotta wrote:
Il 09/09/2011 19:45, Tommaso Cucinotta ha scritto:
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Perosnally, I'd prefer to avoid this syntax of 'everything until the
end of line', and stick with the good old
-x buffer-export latex
Il 09/09/2011 22:58, Richard Heck ha scritto:
I have a worry here about what happens to associated files. E.g., if you
export a master document, where do the exported children go, and with
what names? This makes me wonder whether all we should really allow the
user to provide is a directory, and
Il 09/09/2011 23:55, Tommaso Cucinotta ha scritto:
Thinking aloud:
-) a destination folder might be inferred from the destination
file-name, i.e., its immediately containing folder.
And this is done in the attached patch.
Example of usage:
I have master.lyx including c/child.lyx (by relative
Recently, I found out the easiest way (imo) of accessing mailing lists
for LyX, by using news server (nntp) news.gmane.org and subscribing to
gmane.editors.lyx.* groups. Sending an reading messages can be
conveniently done, for example through Thunderbird.
I think it would be helpful for the
Guenter Milde wrote:
So the attached patch would be what you request. Shall I put this in?
Looks fine to me:
I've committed to trunk. What about branch?
Jürgen
On 2011-09-08, Richard Heck wrote:
> On 09/08/2011 01:57 PM, Julien Rioux wrote:
>> On 08/09/2011 7:34 PM, Tommaso Cucinotta wrote:
>>> Hi,
>>> would it be possible to add to LyX the possibility to specify an
>>> explicit output file-name when exporting from the command-line to a
>>> different
Am 08.09.2011 um 22:01 schrieb Richard Heck:
> On 09/08/2011 01:57 PM, Julien Rioux wrote:
>> On 08/09/2011 7:34 PM, Tommaso Cucinotta wrote:
>>> Hi,
>>>
>>> would it be possible to add to LyX the possibility to specify an
>>> explicit output file-name when exporting from the command-line to a
On 05. sep. 2011 08:49, Jean-Pierre Chrétien wrote:
[...]
After investigation, this error is due to the fact that the word
'Flottants' is in French in the index inset within title of section
4.6.3. The exported latex construct
\subsection{More
On 29. aug. 2011 13:24, Pavel Sanda wrote:
Helge Hafting wrote:
I just noticed that LyX 2.0 (and 2.0.1svn) fail to open files that contain
xfig graphics.
did it work in 1.6? can you create new bug and attach example file with
.fig file?
The bug mysteriously disappeared. I guess it had
Helge Hafting wrote:
> We see that "selectlanguage" inside an index entry cause trouble.
> Therefore, LyX should not emit language change commands inside index
> entries. This is probably not necessary either - an index entry will
> not be hyphenated so language support is not needed there.
Il 09/09/2011 08:10, Guenter Milde ha scritto:
Presumably what is needed here is a "buffer-export-as" LFUN.
or I don't know if one can add an optional argument to the same
buffer-export LFUN, i.e.:
Alt-x buffer-export ps
Alt-x buffer-export ps /tmp/foo.ps
... as implemented in the
Il 09/09/2011 08:29, Stephan Witt ha scritto:
Am 08.09.2011 um 22:01 schrieb Richard Heck:
On 09/08/2011 01:57 PM, Julien Rioux wrote:
new switch, say, -E, which takes two arguments, and have that act as
shorthand for:
-x "buffer-export-as pdf /path/to/export.lyx"
What about spaces in
I tried building with cmake yesterday. A few observations.
Compiling from scratch went faster than autoconf.
From INSTALL.cmake I though that
-DLYX_PACKAGE_SUFFIX=-devel
would be the equivalent of
--with-version-suffix=-devel
under autoconf. But my LyX built by cmake uses ~/.lyx2.1/ as the
Le 09/09/2011 12:50, Tommaso Cucinotta a écrit :
in the patch I sent a few minutes ago, we have this working:
-x "buffer-export latex /path/to/file name with space.tex"
Would it be ok for people used to paths with spaces (guess mostly Win
users) ?
Perosnally, I'd prefer to avoid this syntax
Le 09/09/2011 14:24, Julien Rioux a écrit :
under autoconf. But my LyX built by cmake uses ~/.lyx2.1/ as the user
directory instead of ~/.lyx-devel/ as I expected. This might be a wrong
configuration on my part.
I would have expected that also.
Nevertheless, it would be good to have it
I am going to try scons today and report back.
Scons is going to be dropped some time from now. So you might want to
spend your time in a more useful way.
Vincent
On 09/08/2011 09:10 PM, Lisa Andrews wrote:
I understand that it is not possible to insert a footnote inside a footnote.
However, I notice that it is possible to insert a footnote inside a
footnote if it is inside a branch.
The pdf output does not show the contents of such nested footnotes,
but
Hi,
I've been building LyX RPMs from the SVN source for a while now, but I don't
know how to compile things so that installing the RPM automatically produces
a LyX desktop shortcut for Gnome, the way the officially supported RPM
package does. What precise additional steps do I need to perform?
On 09/09/2011 2:34 PM, Vincent van Ravesteijn wrote:
I am going to try scons today and report back.
Scons is going to be dropped some time from now. So you might want to
spend your time in a more useful way.
Vincent
I see. Good to know, thanks. The build failed but anyway there's not
On 09/09/2011 09:28 AM, Jacob Barandes wrote:
Hi,
I've been building LyX RPMs from the SVN source for a while now, but I
don't know how to compile things so that installing the RPM
automatically produces a LyX desktop shortcut for Gnome, the way the
officially supported RPM package does.
Le 09/09/2011 15:31, Richard Heck a écrit :
On 09/09/2011 09:28 AM, Jacob Barandes wrote:
I've been building LyX RPMs from the SVN source for a while now, but I
don't know how to compile things so that installing the RPM
automatically produces a LyX desktop shortcut for Gnome, the way the
Am 09.09.2011 um 15:45 schrieb Jean-Marc Lasgouttes:
> Le 09/09/2011 15:31, Richard Heck a écrit :
>> On 09/09/2011 09:28 AM, Jacob Barandes wrote:
>>> I've been building LyX RPMs from the SVN source for a while now, but I
>>> don't know how to compile things so that installing the RPM
>>>
Le 09/09/2011 15:51, Stephan Witt a écrit :
This problem is tracked at http://www.lyx.org/trac/ticket/2820
and the outcome is that we do not really know how this stuff works :)
Really? I'm building our own software RPMs with desktop icon setup.
I can have a look later... if nobody steps up.
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Le 09/09/2011 12:50, Tommaso Cucinotta a écrit :
in the patch I sent a few minutes ago, we have this working:
-x "buffer-export latex /path/to/file name with space.tex"
Would it be ok for people used to paths with spaces (guess mostly Win
Il 09/09/2011 19:45, Tommaso Cucinotta ha scritto:
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Perosnally, I'd prefer to avoid this syntax of 'everything until the
end of line', and stick with the good old
-x "buffer-export latex \"/path/to/file name with space.tex\""
which LyX
On 09/09/2011 02:57 PM, Tommaso Cucinotta wrote:
Il 09/09/2011 19:45, Tommaso Cucinotta ha scritto:
Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
Perosnally, I'd prefer to avoid this syntax of 'everything until the
end of line', and stick with the good old
-x "buffer-export latex
Am 09.09.2011 um 19:45 schrieb Tommaso Cucinotta:
> Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
>> Le 09/09/2011 12:50, Tommaso Cucinotta a écrit :
>>> in the patch I sent a few minutes ago, we have this working:
>>>
>>> -x "buffer-export latex /path/to/file name with space.tex"
>>>
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
This is a better syntax, isn't it? It's still possible. When you call
Am 09.09.2011 um 21:50 schrieb Stephan Witt:
>
> There's not only this problem.
>
> There is no way to stop e. g. LFUN_FILE_OPEN from substituting the "variable"
> in /tmp/path/to/the$variable/filename.lyx ...
> So one cannot have a dollar sign in file names. And since it's used
> internally
On 09/09/2011 9:51 PM, Julien Rioux wrote:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
This is a better syntax, isn't it? It's
On 09/09/2011 10:24 PM, Julien Rioux wrote:
On 09/09/2011 9:51 PM, Julien Rioux wrote:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
Il 09/09/2011 22:32, Julien Rioux ha scritto:
On 09/09/2011 10:24 PM, Julien Rioux wrote:
On 09/09/2011 9:51 PM, Julien Rioux wrote:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e
Il 09/09/2011 21:51, Julien Rioux ha scritto:
On 09/09/2011 8:57 PM, Tommaso Cucinotta wrote:
I also checked the front-end part by Guenter, and I have to say we had
that potential issue
that
lyx -o path -e latex
would work, but
lyx -e latex -o path
This is a better syntax, isn't it?
On 09/09/2011 02:57 PM, Tommaso Cucinotta wrote:
> Il 09/09/2011 19:45, Tommaso Cucinotta ha scritto:
>> Il 09/09/2011 14:31, Jean-Marc Lasgouttes ha scritto:
>>>
>>> Perosnally, I'd prefer to avoid this syntax of 'everything until the
>>> end of line', and stick with the good old
>>> -x
Il 09/09/2011 22:58, Richard Heck ha scritto:
I have a worry here about what happens to associated files. E.g., if you
export a master document, where do the exported children go, and with
what names? This makes me wonder whether all we should really allow the
user to provide is a directory, and
Il 09/09/2011 23:55, Tommaso Cucinotta ha scritto:
Thinking aloud:
-) a destination folder might be inferred from the destination
file-name, i.e., its immediately containing folder.
And this is done in the attached patch.
Example of usage:
I have master.lyx including c/child.lyx (by relative
Recently, I found out the easiest way (imo) of accessing mailing lists
for LyX, by using news server (nntp) news.gmane.org and subscribing to
gmane.editors.lyx.* groups. Sending an reading messages can be
conveniently done, for example through Thunderbird.
I think it would be helpful for the
Guenter Milde wrote:
> > So the attached patch would be what you request. Shall I put this in?
>
> Looks fine to me:
I've committed to trunk. What about branch?
Jürgen
66 matches
Mail list logo
