From: Tim X <timx@nospam.dev.null>
Subject: Re: .doc files in emacs
Date: Sun, 17 Dec 2006 11:34:18 +1100 [thread overview]
Message-ID: <87bqm3cqd1.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.1969.1166264692.2155.help-gnu-emacs@gnu.org
Eli Zaretskii <eliz@gnu.org> writes:
> Subject: Re: .doc files in emacs
>
>> From: Tim X <timx@nospam.dev.null>
>> Date: Sat, 16 Dec 2006 12:02:28 +1100
>>
>> Let me know i you want a copy. However, note that it is pretty much my
>> first elisp utility I've let out into the wild - I think the elisp is
>> OK, but not great and probably could be greatly improved by a more
>> experienced elisper.
>
> Well, one advice I can give, based on brief reading of the code, is to
> keep in txutils-convert-alist only the program names, without the
> leading directories (e.g., "pdftotext" instead of "/usr/bin/pdftotext"),
> and use executable-find to find the program.
>
> This way, you will DTRT by default for more users on more platforms,
> and the only users that will need to customize txutils-convert-alist
> are those who install the utilities outside of their PATH.
>
Thanks Eli. I wasn't aware of executable-find. I will check it out.
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2006-12-17 0:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 20:31 .doc files in emacs Gary Wessle
2006-12-15 20:46 ` Leo
2006-12-16 1:02 ` Tim X
2006-12-16 10:24 ` Eli Zaretskii
[not found] ` <mailman.1969.1166264692.2155.help-gnu-emacs@gnu.org>
2006-12-17 0:34 ` Tim X [this message]
2006-12-16 2:21 ` Joe Fineman
2006-12-16 2:51 ` Lennart Borgman
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bqm3cqd1.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
/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.
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).