From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Karl Berry: Re: Nick Dokos: texi2dvi egrep regexp
Date: Sat, 09 Oct 2010 18:59:52 +0200 [thread overview]
Message-ID: <87fwwfuws7.fsf@Rainer.invalid> (raw)
In-Reply-To: 3B502F70-93E5-485E-B4B9-4850A06B7925@gmail.com
Carsten Dominik <carsten.dominik@gmail.com> writes:
> I am looking for a way out which will allow pdf compilation of Org
> work out of the box, and still allow texi2dvi to be used where possible.
All is well as long as GNU grep is not at version 2.6 or later, so maybe
check for that first. Even for later versions it likely only breaks
when the sort order is set to sort lower case letters before upper case
ones _and_ grep produces an error code on that rather than silently
reversing the range expression as it apparently did until version 2.5.
> 1. I could set the environment variable LC_ALL
> for the duration of the texi2dvi command to some value
> like C? That should fix the egrep call, but could
> it have adverse effects on the pdflatex and bibtex runs or
> any other stuff used in texi2dvi?
That would most likely wreak serious havoc with path / file names that
contain UTF-8 characters if they are not just passed through. But one
could use LC_COLLATE=C (or LC_COLLATE=POSIX) in the environment that
calls texi2dvi and that should fix it. Maybe someone with one of the
newer grep versions could try it and report if this indeed helps.
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
prev parent reply other threads:[~2010-10-09 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 18:51 Karl Berry: Re: Nick Dokos: texi2dvi egrep regexp Nick Dokos
2010-10-09 4:06 ` suvayu ali
2010-10-09 10:27 ` Eric S Fraga
2010-10-09 15:27 ` Carsten Dominik
2010-10-09 16:28 ` Matthew Leifer
2010-10-09 16:42 ` Nick Dokos
2010-10-09 17:25 ` Thomas S. Dye
2010-10-10 7:05 ` Carsten Dominik
2010-10-10 16:37 ` Thomas S. Dye
2010-10-10 18:04 ` Eric S Fraga
2010-10-09 16:59 ` Achim Gratz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fwwfuws7.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).