- Original Message -
From: "Alexander Gahr" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 19, 2005 11:03 AM
Subject: Add Function Aspell (was Aspell personal dictionnaires OsX 10.4.2)
Hm tried this before but gave it another try.
I installed lyx
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
- Original Message -
From: "Alexander Gahr" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, October 19, 2005 11:03 AM
Subject: Add Function Aspell (was Aspell personal dictionnaires OsX 10.4.2)
Hm tried this before but gave it another try.
I installed lyx
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
Suppose I have some text that has a lot of quoted speech in it, but it's
supplied using standard (") straight single and double quotes.
Is there some pre-processing tool that will try to convert them to
proper curly quotes suitable for LaTeX (``) and ('')?
I know it can't be done perfectly and
On Thu, 20 Oct 2005, Paul wrote:
Is there a command-line tool that does this using some heuristics to cover
most areas that could be problematic?
Paul
sed. tr, too, but sed would work. Something like s/"[A-Z,a-z]?/``?/g. I
didn't look
at my sed book, but that reads, "substitute two single
Hi everybody,
I've just installed Lyx and even though things went fairly smooth,
I'm struggling with a bunch of minor issues.
(Using the latest Lyx version, Mac OS 10.4.2, Powerbook with a german
keyboard. Gerben Wierda's TeX, ghostscript8, Freetype2, libiconf,
libwmf, ImaheMagick,
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
Paul wrote:
> Suppose I have some text that has a lot of quoted speech in it, but it's
> supplied using standard (") straight single and double quotes.
>
> Is there some pre-processing tool that will try to convert them to
> proper curly quotes suitable for LaTeX (``) and ('')?
>
> I know it
In <[EMAIL PROTECTED]>, Rich Shepard <[EMAIL PROTECTED]> typed:
> On Thu, 20 Oct 2005, Paul wrote:
>
> > Is there a command-line tool that does this using some heuristics to cover
> > most areas that could be problematic?
>
> Paul
>
>sed. tr, too, but sed would work. Something like
Mike Meyer wrote:
>>> Is there a command-line tool that does this using some heuristics to
>>> cover most areas that could be problematic?
>> sed. tr, too, but sed would work. Something like s/"[A-Z,a-z]?/``?/g.
>> I didn't look at my sed book, but that reads, "substitute two single
>> backqotes
I realized that export using the pdflatex do not
produce the same pdf output that the dvipdfm. The
difference lay between the size of up and bottom
margins and the size of the files. Why, PDF (pdflatex)
-- build an output with about (e.g. 29kb) and PDF
(dvipdfm) -- build an output with about
On Oct 19, 2005, at 8:01 PM, [EMAIL PROTECTED] wrote:
Hi everybody,
I've just installed Lyx and even though things went fairly smooth,
I'm struggling with a bunch of minor issues.
(Using the latest Lyx version, Mac OS 10.4.2, Powerbook with a
german keyboard. Gerben Wierda's TeX,
Paul wrote:
> Suppose I have some text that has a lot of quoted speech in it, but it's
> supplied using standard (") straight single and double quotes.
>
> Is there some pre-processing tool that will try to convert them to
> proper curly quotes suitable for LaTeX (``) and ('')?
Here's some
101 - 120 of 120 matches
Mail list logo