From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?=C5=A0t=C4=9Bp=C3=A1n_?= =?UTF-8?Q?N=C4=9Bmec?= Newsgroups: gmane.emacs.bugs Subject: bug#36828: 27.0.50; Uninstalled emacs shows installed documentation Date: Mon, 29 Jul 2019 19:44:25 +0200 Message-ID: <87wog0pwg6.fsf@gmail.com> References: <87lfwitcyf.fsf@telefonica.net> <83blxekwhz.fsf@gnu.org> <87ef2ataoj.fsf@telefonica.net> <837e82kssb.fsf@gnu.org> <87a7cxu16y.fsf@telefonica.net> <87h875qbrv.fsf@gmail.com> <83r268kiss.fsf@gnu.org> <875znkrj6y.fsf@gmail.com> <83mugwkh8u.fsf@gnu.org> <871ry8rfge.fsf@gmail.com> <83k1c0kcbw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="87159"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) Cc: 36828@debbugs.gnu.org, ofv@wanadoo.es To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jul 29 19:45:13 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hs9hv-000MVU-7e for geb-bug-gnu-emacs@m.gmane.org; Mon, 29 Jul 2019 19:45:11 +0200 Original-Received: from localhost ([::1]:55382 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hs9hu-0001mF-0T for geb-bug-gnu-emacs@m.gmane.org; Mon, 29 Jul 2019 13:45:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44744) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hs9ho-0001m7-9H for bug-gnu-emacs@gnu.org; Mon, 29 Jul 2019 13:45:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hs9hn-0007zI-0Z for bug-gnu-emacs@gnu.org; Mon, 29 Jul 2019 13:45:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:40235) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hs9hm-0007yk-Rq for bug-gnu-emacs@gnu.org; Mon, 29 Jul 2019 13:45:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hs9hl-0001jl-VC for bug-gnu-emacs@gnu.org; Mon, 29 Jul 2019 13:45:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?=C5=A0t=C4=9Bp=C3=A1n_?= =?UTF-8?Q?N=C4=9Bmec?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 29 Jul 2019 17:45:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 36828 X-GNU-PR-Package: emacs Original-Received: via spool by 36828-submit@debbugs.gnu.org id=B36828.15644222746620 (code B ref 36828); Mon, 29 Jul 2019 17:45:01 +0000 Original-Received: (at 36828) by debbugs.gnu.org; 29 Jul 2019 17:44:34 +0000 Original-Received: from localhost ([127.0.0.1]:49056 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hs9hK-0001ii-AK for submit@debbugs.gnu.org; Mon, 29 Jul 2019 13:44:34 -0400 Original-Received: from mail-wr1-f45.google.com ([209.85.221.45]:45808) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hs9hI-0001iS-68 for 36828@debbugs.gnu.org; Mon, 29 Jul 2019 13:44:32 -0400 Original-Received: by mail-wr1-f45.google.com with SMTP id f9so62759931wre.12 for <36828@debbugs.gnu.org>; Mon, 29 Jul 2019 10:44:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:in-reply-to:references:user-agent:date :message-id:mime-version:content-transfer-encoding; bh=tz0tniwk2BW26uSKZfVh9R7kzTLJkEanLVnnN2yq+vU=; b=WII2VsxXzALg/VcMMZwr2jhVRIIsbmfYFKMFhXSMcihVHsZMS6G8nijdsSlyheASft oo1FLhjOEy8/1ybPP6e1ahRIgpeaGbwbUk9Vw+eQO3p/Bp1pNufJGO2cOqZb+MVDLCna WXaqGxK70pW02FagT5Kbc4D6IWtrohXNY2PVFCnU1g2ZTcobkfDajA0Xf33kvciikaKj Oh4Vq4cbtXd7KgnIoES+qlEop5wd2hQwoiB9zbkIKW+WwQaBGV+Q2LpmCCjE8OOxoizR 2gybeGL4FmttgFnTUYEHUJH4Bt30547ns2y2lIRbpu4AbXxPdf0fBmv3qScVHX6QLzfp ps+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references :user-agent:date:message-id:mime-version:content-transfer-encoding; bh=tz0tniwk2BW26uSKZfVh9R7kzTLJkEanLVnnN2yq+vU=; b=ihBZT5/4Bot6bbJShDvJk6bQJHwPBQNXDsgL4Ayl2UVCznDO8BtlGYUYNFlCWBVbEv wj+S3GHre3sj3bWurP48qf8BhFB/2i4Mk2QD4FtbwyHZPkXJ8xRnUWzXV9zsVn4vNLqh 4QKsiidvP2m62oAkseEqQMZf2Rme1G7UsJl9nd1KQCqSsCuyCVeTX/O9j72NJbCTBZWQ KTArQhtD9TUselcOp8QzocPOaRjelb6XUnSPyeH09LoEJ0XZz6pyYgxhj54qPn4FvgSc k5XPD/Pen25PhRWdQo15mLVM96fiaF7xNNeJkxEfZxxTmN3OUqx+hk1a0Ff9pAh9It6g IPRw== X-Gm-Message-State: APjAAAWlUQjb4O+XIrTEC6wNuKctxsBqKafkSD50INh4463m9B9lHId/ 9qmxX8++PsmPDBYCZ9rWQ98= X-Google-Smtp-Source: APXvYqyRShcBfvVm0zr8o2nb0DX5mrcAyxX5dzgkaD3mMUe1MXfvHjG5MbVJSljHEQ7MHLl1N5/tHw== X-Received: by 2002:adf:fe09:: with SMTP id n9mr127584658wrr.41.1564422266362; Mon, 29 Jul 2019 10:44:26 -0700 (PDT) Original-Received: from localhost ([185.112.167.114]) by smtp.gmail.com with ESMTPSA id z1sm69027201wrv.90.2019.07.29.10.44.25 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Mon, 29 Jul 2019 10:44:25 -0700 (PDT) In-Reply-To: <83k1c0kcbw.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 29 Jul 2019 19:57:55 +0300") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:164056 Archived-At: On Mon, 29 Jul 2019 19:57:55 +0300 Eli Zaretskii wrote: > Once again, we are talking about the situation where there's both an > installed NEWS file and an uninstalled one for the same Emacs > version. The situation where there's just one of them works exactly > as you want. Right? Yes. [Although I wouldn't use the formulation "the same Emacs version" myself, or at least would need to clarify its definition, i.e. typically the source tree build would be newer than the installed version, but would end up in the same installation directory, yes, so that's probably not relevant here.] >> 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. > > But that's not how Emacs works. Emacs looks for its data-directory > where it was configured to look for it. At configure time, you can > specify that place via the --datadir=3DDIR option. The result (or the > default, if you didn't specify --datadir=3DDIR) is recorded in > src/epaths.h, and that's where Emacs will look for the data files. > > IOW, you are describing an Emacs that is very different from how the > real Emacs works, has been working for decades. Emacs does NOT > determine all of the different directories relative to the directory > where its binary executable lives. It does it according to how it was > configured. I think you are mixing up two things. One way to put it would be the (veteran) developer view vs. the user view. You keep saying things like "that's not how Emacs works" (well, that much we can all agree upon at least) or "I'm not sure we should rock that particular boat for an unusual use case such as yours." and I can appreciate that. But =C3=93scar wrote: And is there a good reason for doing that? When Emacs is executed from the build directory, I expect that it works on the contents of that directory (and the correspondent source directory, for out-of-tree builds.) And I described the same expectation in slightly greater detail and asked you Does that really seem less reasonable than your "TRT"? And also asked you to explain your "right thing" and why you think it is right. And I still haven't got your answer to that, only more description of the status quo (which is helpful, too, though, and thank you for that). I can live with "this is how it works, the code is hairy, let's just keep this as a wishlist item" or something to that effect, but you somehow seem to insist on the current behaviour not being wrong at all or at least seem to have some kind of "the right thing" notion apparently quite different from the expectation of myself, the OP and I suspect most users, and at the same time you fail to explain what that TRT is and why it is right or more right than our expectation. Failing all that, if there is no prospect of change at all, would it be possible to at least warn the user in cases like this? Something like "The NEWS file you are accessing is not the one you probably think it is"?