On 2023-03-10 15:31, Theo Buehler wrote:
While I have no opinion on whether this behavior makes sense, can or
should be changed, I'm quite confident that this is not a bug.
Well, since i got a solution that also solves another problem that i
had;
i can excuse the original issue and consider
On 2023/03/10 13:31, Theo Buehler wrote:
> > Other shells do not have this bug, such as bash, yash, mksh, ash, dash.
mksh does behave the same way as OpenBSD's ksh. I tested a source
build and the Debian package.
> On the other hand, ksh93 behaves the same way as ksh.
>
> Obviously zsh has a con
> Other shells do not have this bug, such as bash, yash, mksh, ash, dash.
On the other hand, ksh93 behaves the same way as ksh.
Obviously zsh has a configuration knob for this, conspicuously named
CD_POSIX:
https://zsh.sourceforge.io/Doc/Release/Options.html
Indeed, see point 5:
https://pubs.o
March 10, 2023 at 2:52 PM, "Theo Buehler" wrote:
> CDPATH Search path for the cd built-in command. It works the same
> way as PATH for those directories not beginning with ‘/’ or
> ‘.’ in cd commands. Note that if CDPATH is set and does not
> contain ‘.’ or an empty path, the current director
On 2023/03/10 11:16:31 +, s...@disroot.org wrote:
> I believe since the given directory (argument) is not an absolute path;
> it attempts to search in CDPATH before checking if the directory
> exists. This will cause any attempts to cd into a directory to fail.
>
> I also believe that the gi
> I also believe that the given directory to cd should be preferred over
> CDPATH; what i mean by this is if a directory exists within CDPATH but
> also exists within the current working directory; the latter should be
> preferred.
I haven't checked how other shells behave. This is the document
Hello, i am facing a bug on portable OpenBSD ksh, aka oksh; where cd
will attempt to search for the given directory (if not provided as an
absolute path) in CDPATH before checking it in the current working
directory. A way to reproduce is the following:
/tmp $ unset CDPATH
/tmp
