unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10130@debbugs.gnu.org
Subject: bug#10130: 24.0.91; eldoc error DOC-24.0.91.1 not found
Date: Fri, 25 Nov 2011 19:24:11 +0100	[thread overview]
Message-ID: <87vcq8njqs.fsf@gmail.com> (raw)
In-Reply-To: <83pqgg8uqc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 25 Nov 2011 10:35:55 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>> Date: Thu, 24 Nov 2011 22:09:59 +0100
>> 
>> --8<---------------cut here---------------start------------->8---
>> eldoc error: (error Cannot open doc string file
>> "/usr/local/share/emacs/24.0.91/etc/DOC-24.0.91.1")
>> --8<---------------cut here---------------end--------------->8---
>> 
>> I have in ../etc a file named DOC-24.0.91.3
>> Creating a symlink to DOC-24.0.91.1 workaround the problem.
>> 
>> What is this file for exactly?
>
> When you build Emacs, the build creates 2 hard links to the same
> binary: `emacs' and `emacs-NN.MM.XX.YY'.  It does the same with the
> DOC file, because, as Glenn explained, each build should have its
> matching DOC file.  Building another binary will break the link of
> `emacs' to the binary and link it to the newer binary, and will also
> make another hard link of the form `emacs-NN.MM.XX.YY' by incrementing
> the YY part.
>
> After rebuilding Emacs several times, you will have several
> `emacs-NN.MM.XX.YY' binaries and `emacs' that is linked to one of
> them, normally the one with the largest YY part.  The same is true for
> the DOC file.
>
> This allows you to run previously built binaries by invoking one of
> the `emacs-NN.MM.XX.YY' programs, and the DOC files that go with each
> one of them will then be available for Emacs to use.
>
> IOW, this is a feature (and quite a useful one, e.g., when you are
> faced with a recently introduced bug and want to know which build
> introduced it).

Thank you very much for this explanation Eli.

-- 
  Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 





      reply	other threads:[~2011-11-25 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-24 21:09 bug#10130: 24.0.91; eldoc error DOC-24.0.91.1 not found Thierry Volpiatto
2011-11-24 23:56 ` Glenn Morris
2011-11-25  5:38   ` Thierry Volpiatto
2011-11-25  6:30     ` Thierry Volpiatto
2011-11-25  8:35 ` Eli Zaretskii
2011-11-25 18:24   ` Thierry Volpiatto [this message]

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=87vcq8njqs.fsf@gmail.com \
    --to=thierry.volpiatto@gmail.com \
    --cc=10130@debbugs.gnu.org \
    --cc=eliz@gnu.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.
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).