From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: User interface confusion; p0.30 invokes VM?
Date: 19 Sep 1998 14:02:22 +0200 [thread overview]
Message-ID: <m3r9x81fap.fsf@sparky.gnus.org> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Wed, 16 Sep 1998 10:43:09 -0400"
"Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov> writes:
> A similar function is already in Emacs' executable.el. See the function
> `executable-find'. I don't think it's autoloaded though.
I've now modified `mailcap-command-p' to use suffixes under crippled
pseudo-OSs.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1998-09-19 12:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-13 13:48 Karl Kleinpaste
1998-09-13 16:04 ` William M. Perry
2002-10-20 23:17 ` Lars Magne Ingebrigtsen
1998-09-13 18:48 ` Hallvard B Furuseth
1998-09-14 5:38 ` Lars Magne Ingebrigtsen
1998-09-16 13:22 ` Hrvoje Niksic
1998-09-16 14:43 ` Edward J. Sabol
1998-09-19 12:02 ` Lars Magne Ingebrigtsen [this message]
1998-09-13 19:13 ` Karl Kleinpaste
1998-09-13 20:05 ` William M. Perry
1998-09-13 20:15 ` Karl Kleinpaste
1998-09-13 16:35 ` Chris Halverson
1998-09-14 6:31 ` SL Baur
1998-09-14 5:44 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r9x81fap.fsf@sparky.gnus.org \
--to=larsi@gnus.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.
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 NNTP newsgroup(s).