From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: trapped in bash
Date: Sun, 18 Dec 2016 20:29:33 -0800 [thread overview]
Message-ID: <9da2ae82-ac3f-6ee3-5452-5a008cf129e7@eastlink.ca> (raw)
In-Reply-To: <161218183056.ZM5304@torch.brasslantern.com>
On 18/12/16 06:30 PM, Bart Schaefer wrote:
> On Dec 19, 12:32am, Daniel Shahaf wrote:
> }
> } I suppose you could write a command_not_found_handler() function that
> } tried to reverse engineer _why_ the command wasn't found - with the
> } obvious limitations, e.g., race conditions between the library's
> } execution and the handler's.
>
> I don't think there can be a race here because the handler won't be
> invoked if the execve() hasn't already failed.
>
> Something like this:
>
> command_not_found_handler () {
> local attempt="$1"
> if [[ "$1" != /* && ( -o pathdirs || "$1
> " != */* ) ]]
> then
> emulate zsh -c 'attempt=$^path/$1(N[1])'
> fi
> if [[ -f $attempt ]]
> then
> local hashbang
> read -u 0 -k 2 hashbang < "$attempt"
> case "$hashbang" in
> ('#!') print -u2 -- $1\: bad '#!' interpreter ;;
> (*) print -u2 failed to load $1 ;;
> esac
> else
> print -u2 -- $1\: no such file in \$PATH
> fi
> return 127
> }
>
>
Not for me to say, but it seems to me that the simple fact that a file
exists or does not exist is simple enough to determine in the tradition
of 'whence' or something like that. *Then* we run into issues about
executing it *after* the thing has (obviously) been found. Sometimes a
command can't be found because it can't be found, that is, the file
simply does not exist. Or is that too simple? Anyway I sure like the idea.
next prev parent reply other threads:[~2016-12-19 4:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 15:33 Ray Andrews
2016-12-16 21:51 ` Aaron Schrab
2016-12-16 22:39 ` Ray Andrews
2016-12-16 23:05 ` Bart Schaefer
2016-12-17 20:27 ` Ray Andrews
2016-12-17 20:43 ` Bart Schaefer
2016-12-17 22:40 ` Ray Andrews
[not found] ` <5855BEF2.6090208__18199.534857604$1482015164$gmane$org@eastlink.ca>
2016-12-18 15:06 ` Daniel Shahaf
2016-12-18 15:54 ` Ray Andrews
2016-12-19 0:32 ` Daniel Shahaf
2016-12-19 2:30 ` Bart Schaefer
2016-12-19 4:29 ` Ray Andrews [this message]
2016-12-19 5:48 ` Bart Schaefer
2016-12-19 16:26 ` Ray Andrews
[not found] ` <ab7aeb33-d091-6602-8baa-cce92300d289__26556.3400615521$1482166729$gmane$org@eastlink.ca>
2016-12-19 17:47 ` Daniel Shahaf
2016-12-17 23:16 ` Jim
2016-12-17 23:38 ` Ray Andrews
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=9da2ae82-ac3f-6ee3-5452-5a008cf129e7@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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).