all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: larsi@gnus.org, stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: master ec9523a: Add a keybinding to the help menu to display manuals
Date: Thu, 15 Oct 2020 16:51:38 +0300	[thread overview]
Message-ID: <83o8l3y4ut.fsf@gnu.org> (raw)
In-Reply-To: <87k0vs4eun.fsf@rub.de> (message from Stephen Berman on Thu, 15 Oct 2020 00:33:52 +0200)

> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Thu, 15 Oct 2020 00:33:52 +0200
> Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
> 
> And it's even worse if Info-directory-list includes directories that
> contain lots of extensionless files that aren't info files, such as, for
> example, the AUCTeX package from GNU ELPA, which contains such files as
> ChangeLog, COPYING, GNUmakefile, etc., all of which are listed in the
> *Completions* buffer, and if you choose one of them, it gets visited in
> Info mode, which throws the user-error: "No such node or anchor: Top".

Why do we use that directory for Info files?  It sounds like a royal
mess; info.el was never meant to face these problems.

We have a docs directory, where we keep Texinfo sources of the
documentation; why not keep the Info files there?  Then we'd only need
to avoid *.texi files as completion candidates (which is a good idea
anyway).

Alternatively, we could, of course, have a list of files in the
package's main directory that need to be skipped when looking for the
Info files (ChangeLog, COPYING, GNUmakefile, *.el, *.elc, etc.).  But
I think using a separate directory is much cleaner.



  parent reply	other threads:[~2020-10-15 13:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201013010930.20500.91773@vcs0.savannah.gnu.org>
     [not found] ` <20201013010931.ABE62209AA@vcs0.savannah.gnu.org>
2020-10-14 19:06   ` master ec9523a: Add a keybinding to the help menu to display manuals Stefan Kangas
2020-10-14 22:33     ` Stephen Berman
2020-10-15  1:57       ` Stefan Monnier
2020-10-15  7:00         ` Lars Ingebrigtsen
2020-10-15  7:34           ` Stephen Berman
2020-10-15  7:43           ` Eli Zaretskii
2020-10-15  9:00             ` Stephen Berman
2020-10-15 13:51       ` Eli Zaretskii [this message]
2020-10-16  4:08         ` Richard Stallman
2020-10-16  6:10           ` Eli Zaretskii
2020-10-18  4:10             ` Richard Stallman
2020-10-18 14:35               ` Eli Zaretskii
2020-10-19  3:48                 ` Richard Stallman
2020-10-16  4:57         ` Lars Ingebrigtsen
2020-10-15  6:55     ` 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=83o8l3y4ut.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=stefankangas@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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.