Il 19/09/2011 08:04, Pavel Sanda ha scritto:
Tommaso Cucinotta wrote:
Done, thanks. Is a command-line guide included also within the on-line docs
(UserGuide.lyx) ?
don't we have the new nifty advsearch feature of skimming through manuals
only? :)
Isn't asking on the list faster than using tha
Tommaso Cucinotta wrote:
> Done, thanks. Is a command-line guide included also within the on-line docs
> (UserGuide.lyx) ?
don't we have the new nifty advsearch feature of skimming through manuals
only? :)
pavel
Il 19/09/2011 02:38, Julien Rioux ha scritto:
On 19/09/2011 1:52 AM, Tommaso Cucinotta wrote:
Done, thanks. Is a command-line guide included also within the on-line
docs (UserGuide.lyx) ?
While you're at it could you please have a look at
http://www.lyx.org/trac/ticket/4312
Done (list of bac
On 19/09/2011 1:52 AM, Tommaso Cucinotta wrote:
Done, thanks. Is a command-line guide included also within the on-line
docs (UserGuide.lyx) ?
While you're at it could you please have a look at
http://www.lyx.org/trac/ticket/4312
--
Julien
Il 18/09/2011 23:48, Pavel Sanda ha scritto:
atters.\n"
+ "\t-E [--export-to] fmt filename\n"
+ " where fmt is the export format of choice (see
--export),\n"
+ " and filename is the destination
filename.\n"
Tommaso Cucinotta wrote:
> @@ -1054,6 +1057,9 @@
> " Look on Tools->Preferences->File
> formats->Format\n"
> " to get an idea which parameters should be
> passed.\n"
> " Note that the order of -e an
On 15/09/2011 9:52 PM, Tommaso Cucinotta wrote:
If what you'd like is an additional option/argument for specifying the
output folder for additional contents such as images, included files,
bibliography, etc., then we could add that later on.
That's an interesting idea in itself.
What I was get
Il 15/09/2011 15:13, Julien Rioux ha scritto:
Let's say I have a document, where all my figures are in ../images and
I want to export latex to out/latex and xhtml to out/xhtml and have my
images in out/images:
out/images <-- image files
out/latex <-- latex source
out/xhtml <-- xhtml source
Ho
On 15/09/2011 12:33 AM, Tommaso Cucinotta wrote:
I guess we have to live with this. What happens with the current code,
actually? Do we output e.g. .eps files to parent directories?
Yes, I just tried:
a.fig
nested/source.lyx (including a.fig)
and, after the export, we get:
nested/s
Il 13/09/2011 14:43, Richard Heck ha scritto:
Anyway, some thoughts.
This will be very nice to have.
It's in: r39678.
There may be some additional work needed in order to deal with all the
possible cases (relative paths, absolute paths), but it seems to me that
it's mostly there. I tried ex
Il 15/09/2011 00:47, Julien Rioux ha scritto:
So that's how LFUN's with more than one argument are handled then, as
one string. No need to change the patch, I see your stance.
Ok, let me check whether further clean-ups are needed, and commit.
On a related note, check out the point 3) at the bo
So that's how LFUN's with more than one argument are handled then, as
one string. No need to change the patch, I see your stance.
Cheers,
Julien
Il 14/09/2011 00:20, Julien Rioux ha scritto:
On 13/09/2011 1:52 AM, Tommaso Cucinotta wrote:
-bool doExport(std::string const& format, bool put_in_tempdir,
+bool doExport(std::string const& target, bool put_in_tempdir,
bool includeall = false) const;
Can we keep form
Il 13/09/2011 14:43, Richard Heck ha scritto:
I guess I'd prefer to a separate LFUN_BUFFER_EXPORT_TO routine here,
rather than this sort of trick with the arguments. There might one day
be other differences one wants. I think that would also make it easier
later to add the possibility to the fr
On 13/09/2011 7:55 PM, Tommaso Cucinotta wrote:
I tried to not interfere with the original logic when no output folder
was set. One difference that I would see between the 2 cases (and which
might motivate keeping some distinction between the 2 cases) is due to
already existing image files. Say t
On 13/09/2011 1:52 AM, Tommaso Cucinotta wrote:
The attached improved patch correctly exports EmbeddedObjects.lyx:
$ ./src/lyx -E latex /tmp/out/objects.tex lib/doc/EmbeddedObjects.lyx
$ find /tmp/out/
/tmp/out/
/tmp/out/DummyDocument2.tex
/tmp/out/clipart
/tmp/out/clipart/CommentNoteImageQt4.ep
Il 13/09/2011 14:43, Richard Heck ha scritto:
On 09/12/2011 07:52 PM, Tommaso Cucinotta wrote:
-bool Buffer::doExport(string const& format, bool put_in_tempdir,
- bool includeall, string& result_file) const
+bool Buffer::doExport(string const& target, bool put_in_tempdir,
+
On 09/12/2011 07:52 PM, Tommaso Cucinotta wrote:
> Il 11/09/2011 19:24, Tommaso Cucinotta ha scritto:
>> Il 10/09/2011 01:39, Tommaso Cucinotta ha scritto:
>>> However, graphics files are not copied, so the exported latex cannot
>>> compile unless you copy the additionally needed external files.
>>
Il 11/09/2011 19:24, Tommaso Cucinotta ha scritto:
Il 10/09/2011 01:39, Tommaso Cucinotta ha scritto:
However, graphics files are not copied, so the exported latex cannot
compile unless you copy the additionally needed external files.
Independently on whether the output folder is explicitly pr
Il 10/09/2011 01:39, Tommaso Cucinotta ha scritto:
However, graphics files are not copied, so the exported latex cannot
compile unless you copy the additionally needed external files.
Independently on whether the output folder is explicitly provider or
automatically inferred from an output fil
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
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
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-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? I
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
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
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 still
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 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
parse_export
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 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 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 sho
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
u
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 o
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
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 att
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 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 for
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 ?
>>
>> Something along the line of:
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 ?
Something along the line of:
lyx -e latex -o /path/to/output.tex /path/to/input.lyx
While
40 matches
Mail list logo
