Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n

Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n

[Peter Stephenson]

Andrej Borsenkow wrote:
> The problem is, of course, =cmd won't be the same as /path/to/cmd.exe. But
> it the same with my patch as well.

That might be worth a special case, since the assumption is usually that
=cmd returns a file.

However, `=' doesn't always return a file in any case, since it expands
aliases.  That tends to annoy me since it means the behaviour is not well
defined.  What's more, it seems to try the command path first, then expand
aliases, which is not the usual search order; and it never searches for
functions.  So this seems to me more confusing than useful.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

RE: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n

[Andrej Borsenkow]

>
> On Thu, 12 Jul 2001, Michael Schaap wrote:
>
> > At 11:21 12-7-2001, Peter Stephenson wrote:
> > >Andrej Borsenkow wrote:
> > > > The problem is, of course, =cmd won't be the same as
> /path/to/cmd.exe. But
> > > > it the same with my patch as well.
> > >
> > >That might be worth a special case, since the assumption is
> usually that
> > >=cmd returns a file.
> >
> > But it does, in this case!
> >
>
> No.
>
> cp =cmd .
>
> copies cmd *not* cmd.exe. And this does make difference.
>

Sorry, now when I could finally test it it is O.K. mv results in error
message (something about inability to chmod) but still creates foo.exe.

-andrej

Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n

[Andrej Borsenkow]

On Thu, 12 Jul 2001, Michael Schaap wrote:

> At 11:21 12-7-2001, Peter Stephenson wrote:
> >Andrej Borsenkow wrote:
> > > The problem is, of course, =cmd won't be the same as /path/to/cmd.exe. But
> > > it the same with my patch as well.
> >
> >That might be worth a special case, since the assumption is usually that
> >=cmd returns a file.
>
> But it does, in this case!
>

No.

cp =cmd .

copies cmd *not* cmd.exe. And this does make difference.

> As far as Cygwin is concerned, both "/bin/ls" and "/bin/ls.exe" are files -
> the same file.  You can do whatever you want with either of the names.  The
> only difference is that a readdir on /bin only returns "ls.exe" and not "ls".
>

Only w.r.t. to stat() and only if /bin/ls does not exist.

-andrej

Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n

[Michael Schaap]

At 11:21 12-7-2001, Peter Stephenson wrote:
>Andrej Borsenkow wrote:
> > The problem is, of course, =cmd won't be the same as /path/to/cmd.exe. But
> > it the same with my patch as well.
>
>That might be worth a special case, since the assumption is usually that
>=cmd returns a file.

But it does, in this case!

As far as Cygwin is concerned, both "/bin/ls" and "/bin/ls.exe" are files - 
the same file.  You can do whatever you want with either of the names.  The 
only difference is that a readdir on /bin only returns "ls.exe" and not "ls".

  - Michael

Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n

[Sven Wischnowsky]

Peter Stephenson wrote:

> "Bart Schaefer" wrote:
> > On Jul 11,  1:30pm, Andrew Markebo wrote:
> > } aes@NOCTURN:Jul04<130> cvs --help-options
> > } zsh: correct 'cvs' to '_cvs' [nyae]? n
> >
> > Aside to zsh-workers:  Regardless of the above, this really shouldn't
> > happen.  I'd hate to suggest special-casing a leading underscore in the
> > correction code.  Other possibilities?
> 
> Well, the *real* fix is to make the correction code use the completion
> system to generate corrections and do it with shell functions.  But I
> suspect that's a huge amount of work, since the completion system is
> heavily tied into zle.

I've been thinking about this ever since we added correction to the
completion system...  There's another problem, namely: where to make it
try correction.  After each word, but what exactly is a word here.  And
what about things like `../$foo/bar' -- it might be that it's the `$foo'
that really should be `Foo' or whatever.

Very complicated that.


Bye
  Sven


-- 
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de

Re: ehh... zsh: correct 'cvs' to '_cvs' [nyae]? n

[Peter Stephenson]

"Bart Schaefer" wrote:
> On Jul 11,  1:30pm, Andrew Markebo wrote:
> } aes@NOCTURN:Jul04<130> cvs --help-options
> } zsh: correct 'cvs' to '_cvs' [nyae]? n
>
> Aside to zsh-workers:  Regardless of the above, this really shouldn't
> happen.  I'd hate to suggest special-casing a leading underscore in the
> correction code.  Other possibilities?

Well, the *real* fix is to make the correction code use the completion
system to generate corrections and do it with shell functions.  But I
suspect that's a huge amount of work, since the completion system is
heavily tied into zle.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************