_/ On Wed 19 Oct 2005 19:42:31 BST, [Paul] wrote : \_
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted some
On 10/20/05, Angus Leeming [EMAIL PROTECTED] wrote:
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list
via gmane). For example, I press L in kmail when I want to answer to the
list.
I ignored all
_/ On Wed 19 Oct 2005 19:42:31 BST, [Paul] wrote : \_
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted some
On 10/20/05, Angus Leeming [EMAIL PROTECTED] wrote:
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list
via gmane). For example, I press L in kmail when I want to answer to the
list.
I ignored all
_/ On Wed 19 Oct 2005 19:42:31 BST, [Paul] wrote : \_
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted some
On 10/20/05, Angus Leeming <[EMAIL PROTECTED]> wrote:
> >> I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
> >> then get a decent email program (or news client, if you read the list
> >> via gmane). For example, I press L in kmail when I want to answer to the
> >> list.
> >
Geoffrey Lloyd wrote:
Yes it should but you must note that Export-Pdflatex is different to
Export-latex followed by running pdflatex on the file.
In the second case the only Export that Lyx is performing is Lyx-tex.
This will not convert any graphics file formats.
This is true for 1.3.x,
On Wednesday 19 October 2005 06:04, Roy Schestowitz wrote:
That said, I can't understand why people steer away from encapsulated
PostScript, which in most cases ought to be used as it preserves and
incorporates vectors rather than pixels. If used properly, it is also far
smaller in terms of
: Wednesday, October 19, 2005 8:56 AM
To: lyx-users@lists.lyx.org
Subject: Re: Lyx command line question
Geoffrey Lloyd wrote:
Yes it should but you must note that Export-Pdflatex is
different to
Export-latex followed by running pdflatex on the file.
In the second case the only Export
In [EMAIL PROTECTED], Sanders, Maarten (M.J.L.) [EMAIL PROTECTED] typed:
2) run, before you run pdflatex, something like
for FILE in `find . -name '*\.gif'`; do convert $FILE `echo $FILE | sed
's/\(.*\.\)gif/\1png/'`; done
basename is safer:
for file in $(find . -name *.gif)
do
convert
Mike Meyer wrote:
2) run, before you run pdflatex, something like
for FILE in `find . -name '*\.gif'`; do convert $FILE `echo $FILE |
sed 's/\(.*\.\)gif/\1png/'`; done
basename is safer:
for file in $(find . -name *.gif)
do
convert $file $(basename $file .gif).png
done
Hi, Mike.
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted some different
habits. The main question to ask is would the group or the
On 10/19/05, Paul [EMAIL PROTECTED] wrote:
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted some different
habits.
Paul Smith wrote:
On 10/19/05, Paul [EMAIL PROTECTED] wrote:
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted
In [EMAIL PROTECTED], Paul [EMAIL PROTECTED] typed:
Maybe it's just my mail client, but this list seems to default for a
reply to the sender instead of to the list, unlike all the other lists
I've ever been on. I accidently sent a reply intended for the list to
the sender and didn't realise
Paul [EMAIL PROTECTED] writes:
| PS: Please always reply to the list
|
| I second that. I noticed a tendency to reply off-list. This leaves
| gaps in the mailing list archives and puts off a subset of list
| subscribers. css-discuss, on the contrary, adopted some different
| habits. The
Angus Leeming [EMAIL PROTECTED] writes:
| find foo -name '*.gif' | while read file
| do
| pngfile=`basename $file .gif`.png
| convert $file pngfile
| done
Hmm... I thought thiw was usually written as a for-loop.
for file in `find foo -name \*.gif` ; do
pngfile=`basename $file
Todd Denniston wrote:
I agree, Paul. The reply address should be occupied by the list's address.
I could agree ... if I had not seen the problems it can cause.
example: the MUSCLE list (smart cards)
http://lists.drizzle.com/mailman/listinfo/muscle
First: to me this breaks the rule of
Paul Smith [EMAIL PROTECTED] writes:
| On 10/19/05, Paul [EMAIL PROTECTED] wrote:
| PS: Please always reply to the list
|
| I second that. I noticed a tendency to reply off-list. This leaves
| gaps in the mailing list archives and puts off a subset of list
| subscribers. css-discuss, on
On Wed, Oct 19, 2005 at 08:32:06PM +0100, Paul wrote:
My experience of lists is that 99% of the time I want to reply to the
whole list, so it makes sense to me to have that as the default.
If someone really decides to make the change, please set the rewriter to put
both the originator and
Lars Gullik Bjønnes wrote:
Angus Leeming writes:
| find foo -name '*.gif' | while read file
| do
| pngfile=`basename $file .gif`.png
| convert $file pngfile
| done
Hmm... I thought thiw was usually written as a for-loop.
for file in `find foo -name \*.gif` ; do
Am Mittwoch, 19. Oktober 2005 20:51 schrieb Paul Smith:
I agree, Paul. The reply address should be occupied by the list's
address.
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list via
gmane). For
On 10/19/05, Georg Baum [EMAIL PROTECTED] wrote:
I agree, Paul. The reply address should be occupied by the list's
address.
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list via
gmane). For example,
[drifting off-topic]
In [EMAIL PROTECTED], Angus Leeming [EMAIL PROTECTED] typed:
The problem is that for splits the returned list of files using
whitespace...
Perhaps the bigger problem is that you can overrun the internal array size
used by for to store the list of returned list of
Angus Leeming [EMAIL PROTECTED] writes:
| The problem is that for splits the returned list of files using
| whitespace...
find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
then (ha!)
| (and you forgot a '$')
|
| Right :) (And restricted the search to the foo directory rather
Paul Smith wrote:
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list
via gmane). For example, I press L in kmail when I want to answer to the
list.
I ignored all those details (discussed at the site
Lars Gullik Bjønnes wrote:
| The problem is that for splits the returned list of files using
| whitespace...
find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
then (ha!)
Thanks. I've just learnt something.
Don't you have to quote the args passed to convert? Bet you still
In [EMAIL PROTECTED], Angus Leeming [EMAIL PROTECTED] typed:
Lars Gullik Bjønnes wrote:
| The problem is that for splits the returned list of files using
| whitespace...
find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
then (ha!)
Thanks. I've just learnt something.
Geoffrey Lloyd wrote:
Yes it should but you must note that Export-Pdflatex is different to
Export-latex followed by running pdflatex on the file.
In the second case the only Export that Lyx is performing is Lyx-tex.
This will not convert any graphics file formats.
This is true for 1.3.x,
On Wednesday 19 October 2005 06:04, Roy Schestowitz wrote:
That said, I can't understand why people steer away from encapsulated
PostScript, which in most cases ought to be used as it preserves and
incorporates vectors rather than pixels. If used properly, it is also far
smaller in terms of
: Wednesday, October 19, 2005 8:56 AM
To: lyx-users@lists.lyx.org
Subject: Re: Lyx command line question
Geoffrey Lloyd wrote:
Yes it should but you must note that Export-Pdflatex is
different to
Export-latex followed by running pdflatex on the file.
In the second case the only Export
In [EMAIL PROTECTED], Sanders, Maarten (M.J.L.) [EMAIL PROTECTED] typed:
2) run, before you run pdflatex, something like
for FILE in `find . -name '*\.gif'`; do convert $FILE `echo $FILE | sed
's/\(.*\.\)gif/\1png/'`; done
basename is safer:
for file in $(find . -name *.gif)
do
convert
Mike Meyer wrote:
2) run, before you run pdflatex, something like
for FILE in `find . -name '*\.gif'`; do convert $FILE `echo $FILE |
sed 's/\(.*\.\)gif/\1png/'`; done
basename is safer:
for file in $(find . -name *.gif)
do
convert $file $(basename $file .gif).png
done
Hi, Mike.
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted some different
habits. The main question to ask is would the group or the
On 10/19/05, Paul [EMAIL PROTECTED] wrote:
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted some different
habits.
Paul Smith wrote:
On 10/19/05, Paul [EMAIL PROTECTED] wrote:
PS: Please always reply to the list
I second that. I noticed a tendency to reply off-list. This leaves
gaps in the mailing list archives and puts off a subset of list
subscribers. css-discuss, on the contrary, adopted
In [EMAIL PROTECTED], Paul [EMAIL PROTECTED] typed:
Maybe it's just my mail client, but this list seems to default for a
reply to the sender instead of to the list, unlike all the other lists
I've ever been on. I accidently sent a reply intended for the list to
the sender and didn't realise
Paul [EMAIL PROTECTED] writes:
| PS: Please always reply to the list
|
| I second that. I noticed a tendency to reply off-list. This leaves
| gaps in the mailing list archives and puts off a subset of list
| subscribers. css-discuss, on the contrary, adopted some different
| habits. The
Angus Leeming [EMAIL PROTECTED] writes:
| find foo -name '*.gif' | while read file
| do
| pngfile=`basename $file .gif`.png
| convert $file pngfile
| done
Hmm... I thought thiw was usually written as a for-loop.
for file in `find foo -name \*.gif` ; do
pngfile=`basename $file
Todd Denniston wrote:
I agree, Paul. The reply address should be occupied by the list's address.
I could agree ... if I had not seen the problems it can cause.
example: the MUSCLE list (smart cards)
http://lists.drizzle.com/mailman/listinfo/muscle
First: to me this breaks the rule of
Paul Smith [EMAIL PROTECTED] writes:
| On 10/19/05, Paul [EMAIL PROTECTED] wrote:
| PS: Please always reply to the list
|
| I second that. I noticed a tendency to reply off-list. This leaves
| gaps in the mailing list archives and puts off a subset of list
| subscribers. css-discuss, on
On Wed, Oct 19, 2005 at 08:32:06PM +0100, Paul wrote:
My experience of lists is that 99% of the time I want to reply to the
whole list, so it makes sense to me to have that as the default.
If someone really decides to make the change, please set the rewriter to put
both the originator and
Lars Gullik Bjønnes wrote:
Angus Leeming writes:
| find foo -name '*.gif' | while read file
| do
| pngfile=`basename $file .gif`.png
| convert $file pngfile
| done
Hmm... I thought thiw was usually written as a for-loop.
for file in `find foo -name \*.gif` ; do
Am Mittwoch, 19. Oktober 2005 20:51 schrieb Paul Smith:
I agree, Paul. The reply address should be occupied by the list's
address.
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list via
gmane). For
On 10/19/05, Georg Baum [EMAIL PROTECTED] wrote:
I agree, Paul. The reply address should be occupied by the list's
address.
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list via
gmane). For example,
[drifting off-topic]
In [EMAIL PROTECTED], Angus Leeming [EMAIL PROTECTED] typed:
The problem is that for splits the returned list of files using
whitespace...
Perhaps the bigger problem is that you can overrun the internal array size
used by for to store the list of returned list of
Angus Leeming [EMAIL PROTECTED] writes:
| The problem is that for splits the returned list of files using
| whitespace...
find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
then (ha!)
| (and you forgot a '$')
|
| Right :) (And restricted the search to the foo directory rather
Paul Smith wrote:
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list
via gmane). For example, I press L in kmail when I want to answer to the
list.
I ignored all those details (discussed at the site
Lars Gullik Bjønnes wrote:
| The problem is that for splits the returned list of files using
| whitespace...
find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
then (ha!)
Thanks. I've just learnt something.
Don't you have to quote the args passed to convert? Bet you still
In [EMAIL PROTECTED], Angus Leeming [EMAIL PROTECTED] typed:
Lars Gullik Bjønnes wrote:
| The problem is that for splits the returned list of files using
| whitespace...
find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
then (ha!)
Thanks. I've just learnt something.
Geoffrey Lloyd wrote:
> Yes it should but you must note that Export->Pdflatex is different to
> Export->latex followed by running pdflatex on the file.
>
> In the second case the only Export that Lyx is performing is Lyx->tex.
> This will not convert any graphics file formats.
This is true for
On Wednesday 19 October 2005 06:04, Roy Schestowitz wrote:
> That said, I can't understand why people steer away from encapsulated
> PostScript, which in most cases ought to be used as it preserves and
> incorporates vectors rather than pixels. If used properly, it is also far
> smaller in terms
> Sent: Wednesday, October 19, 2005 8:56 AM
> To: lyx-users@lists.lyx.org
> Subject: Re: Lyx command line question
>
>
> Geoffrey Lloyd wrote:
>
> > Yes it should but you must note that Export->Pdflatex is
> different to
> > Export->latex followed by running p
In <[EMAIL PROTECTED]>, Sanders, Maarten (M.J.L.) <[EMAIL PROTECTED]> typed:
> 2) run, before you run pdflatex, something like
> for FILE in `find . -name '*\.gif'`; do convert $FILE `echo $FILE | sed
> 's/\(.*\.\)gif/\1png/'`; done
basename is safer:
for file in $(find . -name *.gif)
do
Mike Meyer wrote:
>> 2) run, before you run pdflatex, something like
>> for FILE in `find . -name '*\.gif'`; do convert $FILE `echo $FILE |
>> sed 's/\(.*\.\)gif/\1png/'`; done
>
> basename is safer:
>
> for file in $(find . -name *.gif)
> do
> convert $file $(basename $file .gif).png
> done
>>> PS: Please always reply to the list
>
> I second that. I noticed a tendency to reply off-list. This leaves
> gaps in the mailing list archives and puts off a subset of list
> subscribers. css-discuss, on the contrary, adopted some different
> habits. The main question to ask is "would the
On 10/19/05, Paul <[EMAIL PROTECTED]> wrote:
> >>> PS: Please always reply to the list
> >
> > I second that. I noticed a tendency to reply off-list. This leaves
> > gaps in the mailing list archives and puts off a subset of list
> > subscribers. css-discuss, on the contrary, adopted some
Paul Smith wrote:
>
> On 10/19/05, Paul <[EMAIL PROTECTED]> wrote:
> > >>> PS: Please always reply to the list
> > >
> > > I second that. I noticed a tendency to reply off-list. This leaves
> > > gaps in the mailing list archives and puts off a subset of list
> > > subscribers. css-discuss, on
In <[EMAIL PROTECTED]>, Paul <[EMAIL PROTECTED]> typed:
> Maybe it's just my mail client, but this list seems to default for a
> reply to the sender instead of to the list, unlike all the other lists
> I've ever been on. I accidently sent a reply intended for the list to
> the sender and didn't
Paul <[EMAIL PROTECTED]> writes:
| >>> PS: Please always reply to the list
| >
| > I second that. I noticed a tendency to reply off-list. This leaves
| > gaps in the mailing list archives and puts off a subset of list
| > subscribers. css-discuss, on the contrary, adopted some different
| >
Angus Leeming <[EMAIL PROTECTED]> writes:
| find foo -name '*.gif' | while read file
| do
| pngfile=`basename "$file" .gif`.png
| convert "$file" "pngfile"
| done
Hmm... I thought thiw was usually written as a for-loop.
for file in `find foo -name \*.gif` ; do
pngfile=`basename
Todd Denniston wrote:
>>I agree, Paul. The reply address should be occupied by the list's address.
>
> I could agree ... if I had not seen the problems it can cause.
> example: the MUSCLE list (smart cards)
> http://lists.drizzle.com/mailman/listinfo/muscle
>
> First: to me this breaks the rule
Paul Smith <[EMAIL PROTECTED]> writes:
| On 10/19/05, Paul <[EMAIL PROTECTED]> wrote:
| > >>> PS: Please always reply to the list
| > >
| > > I second that. I noticed a tendency to reply off-list. This leaves
| > > gaps in the mailing list archives and puts off a subset of list
| > > subscribers.
On Wed, Oct 19, 2005 at 08:32:06PM +0100, Paul wrote:
> My experience of lists is that 99% of the time I want to reply to the
> whole list, so it makes sense to me to have that as the default.
>
> > If someone really decides to make the change, please set the rewriter to put
> > both the
Lars Gullik Bjønnes wrote:
> Angus Leeming writes:
> | find foo -name '*.gif' | while read file
> | do
> | pngfile=`basename "$file" .gif`.png
> | convert "$file" "pngfile"
> | done
> Hmm... I thought thiw was usually written as a for-loop.
> for file in `find foo -name \*.gif` ; do
>
Am Mittwoch, 19. Oktober 2005 20:51 schrieb Paul Smith:
> I agree, Paul. The reply address should be occupied by the list's
address.
I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
then get a decent email program (or news client, if you read the list via
gmane). For
On 10/19/05, Georg Baum <[EMAIL PROTECTED]> wrote:
> > I agree, Paul. The reply address should be occupied by the list's
> address.
>
> I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
> then get a decent email program (or news client, if you read the list via
> gmane). For
[drifting off-topic]
In <[EMAIL PROTECTED]>, Angus Leeming <[EMAIL PROTECTED]> typed:
> The problem is that "for" splits the returned list of files using
> whitespace...
>
> Perhaps the bigger problem is that you can overrun the internal array size
> used by "for" to store the list of
Angus Leeming <[EMAIL PROTECTED]> writes:
| The problem is that "for" splits the returned list of files using
| whitespace...
find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
then (ha!)
| > (and you forgot a '$')
|
| Right :) (And restricted the search to the foo directory
Paul Smith wrote:
>> I don't agree. Read http://www.unicom.com/pw/reply-to-harmful.html, and
>> then get a decent email program (or news client, if you read the list
>> via gmane). For example, I press L in kmail when I want to answer to the
>> list.
>
> I ignored all those details (discussed at
Lars Gullik Bjønnes wrote:
> | The problem is that "for" splits the returned list of files using
> | whitespace...
>
> find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
> then (ha!)
Thanks. I've just learnt something.
Don't you have to quote the args passed to convert? Bet you
In <[EMAIL PROTECTED]>, Angus Leeming <[EMAIL PROTECTED]> typed:
> Lars Gullik Bjønnes wrote:
> > | The problem is that "for" splits the returned list of files using
> > | whitespace...
> >
> > find foo -name \*.gif -print -exec convert {} `basename {}`.png \;
> > then (ha!)
>
> Thanks. I've
I try to use lyx from the command line.
In lyx 1.4pre2 preview pdflatex goes fine.
On the commandline I get:
$ lyx --export latex myfile.lyx
... lot of messages but OK
$ pdflatex myfile.tex
... goes fine except for an gif image. I can enter the latex question
about an image not being
Sanders, Maarten (M.J.L.) wrote:
I try to use lyx from the command line.
In lyx 1.4pre2 preview pdflatex goes fine.
On the commandline I get:
$ lyx --export latex myfile.lyx
... lot of messages but OK
$ pdflatex myfile.tex
... goes fine except for an gif image. I can enter the
Sanders, Maarten (M.J.L.) wrote:
I try to use lyx from the command line.
In lyx 1.4pre2 preview pdflatex goes fine.
On the commandline I get:
$ lyx --export latex myfile.lyx
... lot of messages but OK
$ pdflatex myfile.tex
... goes fine except for an gif image. I can enter the
Am Dienstag, 18. Oktober 2005 16:09 schrieb Sanders, Maarten (M.J.L.):
Georg/Angus,
From within the GUI things work fine. It is just the conversion on the
commandline that does not do the part where the gif file is converted to
some format pdflatex understands. Convert is present on my
- Original Message -
From: Georg Baum [EMAIL PROTECTED]
To: Sanders, Maarten (M.J.L.) [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: Angus Leeming [EMAIL PROTECTED]
Sent: Tuesday, October 18, 2005 3:40 PM
Subject: Re: Lyx command line question
Am Dienstag, 18. Oktober 2005 16:09 schrieb
: Lyx command line question
Am Dienstag, 18. Oktober 2005 16:09 schrieb Sanders, Maarten (M.J.L.):
Georg/Angus,
From within the GUI things work fine. It is just the conversion on the
commandline that does not do the part where the gif file is converted to
some format pdflatex understands. Convert
I try to use lyx from the command line.
In lyx 1.4pre2 preview pdflatex goes fine.
On the commandline I get:
$ lyx --export latex myfile.lyx
... lot of messages but OK
$ pdflatex myfile.tex
... goes fine except for an gif image. I can enter the latex question
about an image not being
Sanders, Maarten (M.J.L.) wrote:
I try to use lyx from the command line.
In lyx 1.4pre2 preview pdflatex goes fine.
On the commandline I get:
$ lyx --export latex myfile.lyx
... lot of messages but OK
$ pdflatex myfile.tex
... goes fine except for an gif image. I can enter the
Sanders, Maarten (M.J.L.) wrote:
I try to use lyx from the command line.
In lyx 1.4pre2 preview pdflatex goes fine.
On the commandline I get:
$ lyx --export latex myfile.lyx
... lot of messages but OK
$ pdflatex myfile.tex
... goes fine except for an gif image. I can enter the
Am Dienstag, 18. Oktober 2005 16:09 schrieb Sanders, Maarten (M.J.L.):
Georg/Angus,
From within the GUI things work fine. It is just the conversion on the
commandline that does not do the part where the gif file is converted to
some format pdflatex understands. Convert is present on my
- Original Message -
From: Georg Baum [EMAIL PROTECTED]
To: Sanders, Maarten (M.J.L.) [EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: Angus Leeming [EMAIL PROTECTED]
Sent: Tuesday, October 18, 2005 3:40 PM
Subject: Re: Lyx command line question
Am Dienstag, 18. Oktober 2005 16:09 schrieb
: Lyx command line question
Am Dienstag, 18. Oktober 2005 16:09 schrieb Sanders, Maarten (M.J.L.):
Georg/Angus,
From within the GUI things work fine. It is just the conversion on the
commandline that does not do the part where the gif file is converted to
some format pdflatex understands. Convert
I try to use lyx from the command line.
In lyx 1.4pre2 preview pdflatex goes fine.
On the commandline I get:
$ lyx --export latex myfile.lyx
... lot of messages but OK
$ pdflatex myfile.tex
... goes fine except for an gif image. I can the latex question
about an image not being found and
Sanders, Maarten (M.J.L.) wrote:
> I try to use lyx from the command line.
>
> In lyx 1.4pre2 preview pdflatex goes fine.
>
> On the commandline I get:
>
> $ lyx --export latex myfile.lyx
> ... lot of messages but OK
> $ pdflatex myfile.tex
> ... goes fine except for an gif image. I can
Sanders, Maarten (M.J.L.) wrote:
> I try to use lyx from the command line.
>
> In lyx 1.4pre2 preview pdflatex goes fine.
>
> On the commandline I get:
>
> $ lyx --export latex myfile.lyx
> ... lot of messages but OK
> $ pdflatex myfile.tex
> ... goes fine except for an gif image. I can
Am Dienstag, 18. Oktober 2005 16:09 schrieb Sanders, Maarten (M.J.L.):
> Georg/Angus,
>
> From within the GUI things work fine. It is just the conversion on the
> commandline that does not do the part where the gif file is converted to
> some format pdflatex understands. Convert is present on my
- Original Message -
From: "Georg Baum" <[EMAIL PROTECTED]>
To: "Sanders, Maarten (M.J.L.)" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Cc: "Angus Leeming" <[EMAIL PROTECTED]>
Sent: Tuesday, October 18, 2005 3:40 PM
Subject: Re: Lyx
PROTECTED]>
Sent: Tuesday, October 18, 2005 3:40 PM
Subject: Re: Lyx command line question
Am Dienstag, 18. Oktober 2005 16:09 schrieb Sanders, Maarten (M.J.L.):
Georg/Angus,
From within the GUI things work fine. It is just the conversion on the
commandline that does not do the part w
90 matches
Mail list logo
