Hi,
i think a file_not_found_handle() or a modified command_not_found_handle(),
that does not need an unsuccessful PATH search to be triggered, would be
useful and consistent.
i found this old (Dec, 2009) discussion :
http://gnu-bash.2382.n7.nabble.com/command-not-found-handle-not-called-if-comma
Hi Ken,
same reason for me: some object-oriented shell (
http://oobash.sourceforge.net/)
"But given that the first entry on a command line pretty much has to be
a command, I'm not sure it makes sense to invoke file_not_found_handle()"
I think you are right.
But then we go in circles...:
http://
mey
> On 8/14/13 7:44 AM, Andreas Gregor Frank wrote:
> > Hi,
> >
> > i think a file_not_found_handle() or a modified
> command_not_found_handle(),
> > that does not need an unsuccessful PATH search to be triggered, would be
> > useful and consistent.
>
ethod...
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
> On 8/19/13 6:57 AM, Andreas Gregor Frank wrote:
> > Hi Chet,
> >
> > I have no
Hello Greg,
this is a feature request for no_such_file_or_directory_
handle(). I do not want to talk about missing quotes in anyone's code
example!
And the question if it makes sense to implement a
command_not_found_handle() in this or that way has nothing to do with this
request, too.
How someone
Hi Eduardo,
thank you very much for this constructive and honest answer.
Not what i hoped to see, but this is only a request.
For me only a nice to have...so fine
bye
Andreas
2013/8/21 Eduardo A. Bustamante López
> On Wed, Aug 21, 2013 at 08:39:53PM +0200, Andreas Gregor Frank wr