From: John Wiegley <johnw@gnu.org>
Subject: Re: eshell - win32 - executable files
Date: Mon, 20 Jan 2003 13:17:48 -0700 [thread overview]
Message-ID: <87r8b7tw2b.fsf@alice.dynodns.net> (raw)
In-Reply-To: 3E2A29FC.8000107@XXnetscape.net
>>>>> On Sun Jan 19, matt writes:
> Still no luck. Does this work for you?
Hmm, once, when I used to use Windows machines, I was doing something
close to exactly this. You definitely want to configure
`eshell-binary-suffixes'. You can test it by using the "which"
command, followed by the name of your script.
Oh, wait, you must ALSO set `eshell-force-execution' to t. :)
John
next prev parent reply other threads:[~2003-01-20 20:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-18 22:01 eshell - win32 - executable files matt
2003-01-19 6:02 ` John Wiegley
2003-01-19 7:04 ` matt
2003-01-19 7:12 ` John Wiegley
2003-01-19 7:30 ` matt
2003-01-20 20:17 ` John Wiegley [this message]
2003-01-19 9:14 ` Sören Vogel
2003-01-19 9:23 ` matt
2003-01-19 10:12 ` Sören Vogel
2003-01-19 10:34 ` matt
2003-01-20 11:59 ` Ehud Karni
[not found] ` <mailman.581.1043065581.21513.help-gnu-emacs@gnu.org>
2003-01-20 20:23 ` Matt
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=87r8b7tw2b.fsf@alice.dynodns.net \
--to=johnw@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.
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).