all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9891@debbugs.gnu.org
Subject: bug#9891: 24.0.90; Duplicated entry at the info directory
Date: Mon, 31 Oct 2011 20:53:33 +0200	[thread overview]
Message-ID: <83wrblm1qq.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0jm=-pfzw1z+=7dOg05aDjV+L4MdPX4k-K-ug46iOr8Qw@mail.gmail.com>

> Date: Sat, 29 Oct 2011 20:55:25 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: 9891@debbugs.gnu.org
> 
> >> I don't have an INFOPATH environment variable, but I've seen that,
> >> inside Emacs, the value of the variable `Info-directory-list' is
> >> ("c:/emacs/trunk/info/" "c:/emacs/build/info/").
> >>
> >> Each of these two directories has a `dir' file.  They are exact copies
> >> from the emacs-trunk repository (with a single `Info' entry).
> >
> > Then I think the duplication in the info menu is expected. IIUC, info
> > does not make any attempt to "uniquify" menu entries (the standalone
> > info program behaves in the same way).

This is false; see Info-dir-remove-duplicates.

> Aha, but then I wonder why the only entry that gets duplicated is the
> `Info' one, instead of every menu entry.  BTW, the extra `Info' entry
> isn't located next to the first one, but at the very end of the buffer
> (just after the `SMTP' entry).

This happens because after concatenating the two identical `dir'
files, the second `Info' entry looks as if it belongs to the last
heading, "Emacs lisp libraries".  Info-dir-remove-duplicates only
removes duplicates under the same heading.

> > I think the only remaining issue that might be a bug is: did the normal
> > Emacs-on-MS-Windows build process create these duplicate directories,
> > or did you do something to end up in that state?

It is normal.






  parent reply	other threads:[~2011-10-31 18:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 19:15 bug#9891: 24.0.90; Duplicated entry at the info directory Dani Moncayo
2011-10-28 16:38 ` Glenn Morris
2011-10-28 17:39   ` Dani Moncayo
2011-10-29 18:23     ` Glenn Morris
2011-10-29 18:55       ` Dani Moncayo
2011-10-29 19:16         ` Dani Moncayo
2011-10-29 20:41         ` Dani Moncayo
2011-10-31 18:57           ` Eli Zaretskii
2011-10-29 20:59         ` Eli Zaretskii
2011-10-29 21:19           ` Dani Moncayo
2011-10-31 18:53         ` Eli Zaretskii [this message]
2011-10-31 18:49     ` Eli Zaretskii
2011-11-01  9:29       ` Juri Linkov
2011-11-01 11:32         ` Eli Zaretskii
2011-11-01 22:31           ` Juri Linkov
2011-11-02  1:39             ` Stefan Monnier
2011-11-02 10:01               ` Juri Linkov
2011-11-02  3:55             ` Eli Zaretskii
2011-11-02 10:07               ` Juri Linkov
2011-11-02 10:57                 ` Eli Zaretskii
2011-11-02 12:41                   ` Stefan Monnier
2011-11-02 13:03                     ` Eli Zaretskii
2011-11-02 14:05                       ` Stefan Monnier
2011-11-02 14:33                         ` Drew Adams
2011-11-02 17:28                         ` Andreas Schwab
2011-11-02 17:54                         ` Eli Zaretskii
2011-11-02 19:52                           ` Stefan Monnier
2011-11-05 13:54                             ` Eli Zaretskii
2022-04-26 13:17     ` Lars Ingebrigtsen

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=83wrblm1qq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=9891@debbugs.gnu.org \
    --cc=dmoncayo@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 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.