zsh-workers
 help / color / mirror / code / Atom feed
From: Marlon Richert <marlon.richert@gmail.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [BUG] zf_ln complains about the wrong argument
Date: Sun, 22 Aug 2021 22:27:42 +0300	[thread overview]
Message-ID: <CAHLkEDuh13eY-dW6Y0URAapqFrfRGDfzC1Kg+-6dxG==VXeCOQ@mail.gmail.com> (raw)
In-Reply-To: <CAHYJk3Ts=+iLAH+OmPWeng4gNj9kZEjvvR2QqP5MnzrUwSP1sw@mail.gmail.com>

On Sun, Aug 22, 2021 at 6:35 PM Mikael Magnusson <mikachu@gmail.com> wrote:
>
> On 8/22/21, Marlon Richert <marlon.richert@gmail.com> wrote:
> > When the second argument to zf_ln is an empty string, zf_ln mistakenly
> > reports that the first argument is a non-existing file or dir:
> >
> > % zmodload zsh/files
> > % touch foo
> > % zf_ln foo ''
> > zf_ln: foo: no such file or directory
>
> As do zf_mv, gnu ln, and gnu mv.

Well, two wrongs don't make a right, don't you think? Just because Gnu
prints confusing error messages, doesn't mean Zsh can't do better.

Plus, BSD ln does manage to complain about the right file:

% ln foo ''
ln: : No such file or directory

Also, I discovered this happens, too, when trying to create a symlink
in a dir that doesn't exist:

% zf_ln foo bar/baz
zf_ln: foo: no such file or directory

BSD ln again gives a better error message (although still not 100% accurate):

% ln foo bar/baz
ln: bar/baz: No such file or directory


  reply	other threads:[~2021-08-22 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22 13:45 Marlon Richert
2021-08-22 15:35 ` Mikael Magnusson
2021-08-22 19:27   ` Marlon Richert [this message]
2021-08-22 20:24 ` Peter Stephenson
2021-08-22 21:05   ` Daniel Shahaf
2021-08-23  8:33     ` Peter Stephenson
2021-08-24 13:04       ` Daniel Shahaf

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='CAHLkEDuh13eY-dW6Y0URAapqFrfRGDfzC1Kg+-6dxG==VXeCOQ@mail.gmail.com' \
    --to=marlon.richert@gmail.com \
    --cc=mikachu@gmail.com \
    --cc=zsh-workers@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).