Bug#880992: debian-policy should not recommend running editor using absolute path
- To: Jonathan Nieder <jrnieder@gmail.com>
- Cc: 880992@bugs.debian.org
- Subject: Bug#880992: debian-policy should not recommend running editor using absolute path
- From: Russ Allbery <rra@debian.org>
- Date: Mon, 25 Dec 2017 18:54:13 -0800
- Message-id: <[🔎] 87fu7yqjvu.fsf@hope.eyrie.org>
- Reply-to: Russ Allbery <rra@debian.org>, 880992@bugs.debian.org
- In-reply-to: <20171106184209.jq5ryvl6h4uv6ad6@aiede.mtv.corp.google.com> (Jonathan Nieder's message of "Mon, 6 Nov 2017 10:42:09 -0800")
- References: <20171106184209.jq5ryvl6h4uv6ad6@aiede.mtv.corp.google.com> <20171106184209.jq5ryvl6h4uv6ad6@aiede.mtv.corp.google.com>
Control: tags -1 patch
Jonathan Nieder <jrnieder@gmail.com> writes:
> If read strictly, this says that I must use "/usr/bin/editor" instead of
> invoking "editor" from the $PATH. (I'm not sure I agree with that
> interpretation, but it came up in https://bugs.debian.org/682347.)
> Running "editor" from the $PATH instead of using that full path should
> be perfectly acceptable and IMHO is a better behavior, since it allows
> the user to put a custom editor in /usr/local/bin or $HOME/bin.
> Could this say something like
> not set, the commands "editor" and "pager" should be used,
> respectively. These commands can be invoked explicitly (e.g.
> as /usr/bin/editor), or through a $PATH search (e.g. as
> editor).
> ?
This wording seems fine to me. Seconded. (I volunteer to turn this into
a Git change if it gets enough seconds.)
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: