dash.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joshua Nelson <jynelson@email.sc.edu>
To: dash@vger.kernel.org
Cc: cdaniels@fastmail.com
Subject: [BUG] $PATH not fully searched
Date: Wed, 10 Jan 2018 13:36:18 -0500	[thread overview]
Message-ID: <1997619.aMy8rkrhBo@debian-thinkpad> (raw)

[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]

To the maintainers of the `dash` shell:

I've come across an error with the PATH variable in `dash`. Instead of fully 
searching PATH for commands, dash will respond 'command not found' if `command 
-p <executable>` fails.  The same command works fine in Bash.

The following example was performed in a live cd of Debian 9.1 Stretch (run in 
a virtual machine), with dash version 0.5.8-2.4:

```bash
user@debian:~$ PATH="~/my_bin:$PATH" dash
$ echo $PATH
~/my_bin:/usr/local/bin:/usr/bin:/usr/local/games:/usr/games
$ ls -l ~/my_bin/list
-rwxr--r-- 1 user user 18 Jan 10 17:42 /home/user/my_bin/list
$ list
dash: 3: list: not found
$ exit
user@debian:~$ PATH="$PATH:~/my_bin" list
Desktop Documents Downloads Music my_bin Pictures Public Templates Videos
```

I believe but am not certain that this is related to the following patch:
https://www.mail-archive.com/dash@vger.kernel.org/msg01329.html

Thank you for your time,
Joshua Nelson

jynelson@email.sc.edu
B.S. Computer Science
College of Engineering and Computing | South Carolina Honors College
This message was sent with a PGP[1] signature.

--------
[1] https://www.openpgp.org/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-01-10 18:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 18:36 Joshua Nelson [this message]
2018-01-10 22:18 ` [BUG] $PATH not fully searched Jilles Tjoelker
2018-01-10 23:44   ` Joshua Nelson

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=1997619.aMy8rkrhBo@debian-thinkpad \
    --to=jynelson@email.sc.edu \
    --cc=cdaniels@fastmail.com \
    --cc=dash@vger.kernel.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.
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).