Subject: Re: bug#30723: eshell: built-in ln does not handle . correctly

From: Lars Ingebrigtsen <[email-masked]>
Date: Wed, 09 Dec 2020 19:31:02 +0100

Yegor Timoshenko <[email-masked]> writes:

> In M-x eshell:
>
>   $ ln -s . foo
>   ln: .: omitting directory
>   $ *ln -s . bar
>   $ ls
>   foo: No such file or directory
>   bar:

(This bug report unfortunately got no response at the time.)

If you have

(setq eshell-warn-dot-directories nil)

then "ln -s . foo" works fine, so I think this is expected behaviour?
And so I'm closing this bug report, but if somebody things that this is
something that should work specially in the "ln" command, feel free to
reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no