From: "Štěpán Němec" <stepnem@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36828@debbugs.gnu.org, ofv@wanadoo.es
Subject: bug#36828: 27.0.50; Uninstalled emacs shows installed documentation
Date: Mon, 29 Jul 2019 18:08:33 +0200 [thread overview]
Message-ID: <871ry8rfge.fsf@gmail.com> (raw)
In-Reply-To: <83mugwkh8u.fsf@gnu.org>
On Mon, 29 Jul 2019 18:11:45 +0300
Eli Zaretskii wrote:
> I think you are missing the perspective of someone who considers the
> current behavior to be TRT.
Certainly. So much that I can't even imagine why anybody would consider
that TRT (although I do try, and will appreciate if you try to explain).
> IOW, why should we assume that the version of NEWS in the source tree
> is necessarily more up-to-date/useful than the one in the installation
> directory. It could be, but then it could not be.
Hm, it seems the misunderstanding is mutual.
Whether some version is more up-to-date or useful (whatever that means)
is besides the point. What I meant by "most relevant for the running
executable" and "obvious" above was simply what seems to me a case of
the principle of least surprise: if I run /usr/bin/emacs, I expect it to
use the same PREFIX for other things, i.e. /usr/share/emacs.... If I run
/usr/local/bin/emacs, I expect it to use /usr/local/share/emacs.... And
if I run src/emacs, I expect it to use the source tree.
Does that really seem less reasonable than your "TRT"?
I can imagine the current behaviour being hard to change, but that still
wouldn't make it the right thing IMO.
--
Štěpán
next prev parent reply other threads:[~2019-07-29 16:08 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 15:07 bug#36828: 27.0.50; Uninstalled emacs shows installed documentation Óscar Fuentes
2019-07-28 15:30 ` Eli Zaretskii
2019-07-28 15:56 ` Óscar Fuentes
2019-07-28 16:50 ` Eli Zaretskii
2019-07-29 0:36 ` Óscar Fuentes
2019-07-29 12:13 ` Štěpán Němec
2019-07-29 14:25 ` Óscar Fuentes
2019-07-29 14:41 ` Štěpán Němec
2019-07-29 14:38 ` Eli Zaretskii
2019-07-29 14:47 ` Štěpán Němec
2019-07-29 15:11 ` Eli Zaretskii
2019-07-29 15:20 ` Eli Zaretskii
2019-07-29 16:08 ` Štěpán Němec [this message]
2019-07-29 16:57 ` Eli Zaretskii
2019-07-29 17:44 ` Štěpán Němec
2019-07-29 18:13 ` Eli Zaretskii
2019-07-29 18:33 ` Štěpán Němec
2019-07-29 18:48 ` Eli Zaretskii
2019-07-29 19:20 ` Štěpán Němec
2019-07-29 19:31 ` Eli Zaretskii
2019-07-29 18:42 ` Óscar Fuentes
2019-07-29 19:26 ` Eli Zaretskii
2019-07-29 21:09 ` Óscar Fuentes
2019-07-30 15:08 ` Eli Zaretskii
2019-08-07 14:25 ` Eli Zaretskii
2019-08-07 15:00 ` Óscar Fuentes
2019-08-07 15:03 ` Eli Zaretskii
2019-10-26 3:16 ` Óscar Fuentes
2019-10-26 8:51 ` Eli Zaretskii
2019-10-26 11:55 ` Óscar Fuentes
2019-10-26 12:29 ` Eli Zaretskii
2019-10-26 13:27 ` Óscar Fuentes
2019-10-26 13:45 ` Eli Zaretskii
2019-10-26 20:05 ` Óscar Fuentes
2019-10-26 20:21 ` Eli Zaretskii
2019-10-26 20:40 ` Óscar Fuentes
2019-10-27 5:13 ` Eli Zaretskii
2019-10-27 23:50 ` Óscar Fuentes
2019-10-28 15:58 ` Eli Zaretskii
2019-10-28 19:40 ` Óscar Fuentes
2019-10-28 20:03 ` Eli Zaretskii
2019-10-28 20:21 ` Óscar Fuentes
2019-10-28 20:38 ` Eli Zaretskii
2019-10-28 21:45 ` Óscar Fuentes
2019-10-29 11:56 ` Eli Zaretskii
2019-11-02 17:08 ` Óscar Fuentes
2019-10-29 3:09 ` Richard Stallman
2019-10-26 3:33 ` Óscar Fuentes
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=871ry8rfge.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=36828@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ofv@wanadoo.es \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.