unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36828@debbugs.gnu.org, stepnem@gmail.com
Subject: bug#36828: 27.0.50; Uninstalled emacs shows installed documentation
Date: Sat, 26 Oct 2019 22:05:03 +0200	[thread overview]
Message-ID: <87v9sbjms0.fsf@telefonica.net> (raw)
In-Reply-To: <83y2x7tyb1.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Oct 2019 16:45:54 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> Right now I must leave so a quick question: what about beginning with
>> setting data-directory to the source tree in init_callproc_1 when we are
>> running from a non-installed Emacs? (Assuming that we can detect that
>> condition)
>
> We currently detect that by the condition that doesn't work in your
> case:
>
>       if (!NILP (Fequal (srcdir, Vinvocation_directory))
>
> If we solve that problem, we can solve your problem as side effect,
> right?

Yes, I checked that forcing that `if' to true works for NEWS, but I
wonder why we assign Vdata_directory on init_callproc_1 to the installed
Emacs directory ("/usr/local/share/emacs/27.0.50/etc/" on this case)
when we are running a non-installed Emacs. Having Vdata_directory around
pointing to the "wrong" directory looks like a potential problem. And
IMO it is also undesirable to assign it on two different functions, if
we can avoid that.

BTW, fixing the `if' mentioned above also causes C-h r, C-h t and
probably others to use the non-installed docs. Buth C-h i still shows
the directory of info files of the installed version. I guess that
without a `dir' file on the non-installed doc directory we can't solve
this, right?





  reply	other threads:[~2019-10-26 20:05 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9sbjms0.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=36828@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=stepnem@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).