Hi Chet,
sorry, i thought you talk about the bash code.
I didn't want to show my own usecase but now i have to ;-):
I have a File class and can construct a File "object" for example:
File anObjectName /etc/passwd
and then i can do
e.g. anObjectName.getInode (this already works with
command_not_found_handle() )
But if i do a:
File /etc/passwd /etc/passwd
and then
/etc/passwd.getInode (i think it would be nice if the normal files in a
filesystem could be treated like objects)
then there is nothing that triggers the command_not_found_handle() to split
"object" and method...
So at the moment slashes are forbidden in object names in my fun project.
Now you know why your bash example for ckexec() isn't a solution for me.
bye
Andreas
2013/8/19 Chet Ramey <chet.ra...@case.edu>
> On 8/19/13 6:57 AM, Andreas Gregor Frank wrote:
> > Hi Chet,
> >
> > I have no idea if there is "enough" demand, but i think there will be
> some
> > ideas to use this feature...
> > I still think it is a question of consistency to be able to handle a "No
> > such file or directory event", if i can do this with a "command not found
> > event" (independent of the command_not_found_handle history).
> >
> > You say you can easily test whether or not if the file in the pathname
> exists.
>
> That is not what I said. I said that you, the script writer, can check
> whether or not a filename containing a slash is executable before
> attempting to execute it. Maybe a function something like this (untested):
>
> ckexec()
> {
> case "$1" in
> */*) ;;
> *) "$@" ; return $? ;;
> esac
>
> if [ -x "$1" ]; then
> "$@"
> else
> other-prog "$@"
> fi
> }
>
>
> Chet
> --
> ``The lyf so short, the craft so long to lerne.'' - Chaucer
> ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, ITS, CWRU c...@case.edu
> http://cnswww.cns.cwru.edu/~chet/
>
