all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Richard Stallman <rms@gnu.org>
Cc: larsi@gnus.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: master 2a7488d: Add support for displaying short documentation for function groups
Date: Mon, 19 Oct 2020 11:05:19 +0300	[thread overview]
Message-ID: <874kmqiqoc.fsf@mail.linkov.net> (raw)
In-Reply-To: <E1kUM8W-000582-K3@fencepost.gnu.org> (Richard Stallman's message of "Sun, 18 Oct 2020 23:47:04 -0400")

>   > For example, with a dynamically generated Info manual with groups of functions
>   > and the addressing scheme such as (info "(shortdoc) regexp functions"),
>   > would the users of the standalone Info reader expect that visiting
>   > the same Info location should produce the same documentation to them
>   > in the standalone Info reader?
>
> I think it ought to work for that if possible.
>
> Why can't the dynamically generated manual be written into Info files
> which are then accessible in all the usual ways?

It would require an additional step of running 'make' to update
the generated manuals, whereas most Help commands have the advantage
of immediately displaying the most recent information.

However, the Emacs Info reader could display the most recent information,
but for the users of the standalone Info read we could write that
into Info files.



  reply	other threads:[~2020-10-19  8:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201011035127.7723.3256@vcs0.savannah.gnu.org>
     [not found] ` <20201011035128.E3FD320667@vcs0.savannah.gnu.org>
2020-10-11  3:55   ` master 2a7488d: Add support for displaying short documentation for function groups Lars Ingebrigtsen
2020-10-11 13:49     ` Eli Zaretskii
2020-10-11 21:47       ` Lars Ingebrigtsen
2020-10-11 23:38         ` Drew Adams
2020-10-12  8:05           ` Gregory Heytings via Emacs development discussions.
2020-10-12 16:20             ` Drew Adams
2020-10-12 16:50               ` Gregory Heytings via Emacs development discussions.
2020-10-12 17:29                 ` Drew Adams
2020-10-13 20:05     ` Juri Linkov
2020-10-13 20:35       ` Drew Adams
2020-10-14  7:48         ` Juri Linkov
2020-10-13 20:55       ` T.V Raman
2020-10-14  7:52         ` Juri Linkov
2020-10-14 14:41           ` T.V Raman
2020-10-14  4:12       ` Lars Ingebrigtsen
2020-10-14  7:59         ` Juri Linkov
2020-10-15  6:43           ` Lars Ingebrigtsen
2020-10-15 12:24             ` Stefan Monnier
2020-10-18 20:12               ` Juri Linkov
2020-10-19  3:47                 ` Richard Stallman
2020-10-19  8:05                   ` Juri Linkov [this message]
2020-10-23 20:24     ` Stefan Kangas
2020-10-24 19:59       ` Lars Ingebrigtsen
2020-10-24 23:51         ` Stefan Kangas
2020-10-25 13:04           ` Lars Ingebrigtsen
2020-10-27 13:48       ` Basil L. Contovounesios
2020-10-27 14:33         ` Stefan Kangas
2020-10-27 15:43           ` Basil L. Contovounesios
2020-10-27 17:33             ` Lars Ingebrigtsen
2020-10-27 22:02               ` Stefan Kangas
2020-10-28  8:20                 ` Mattias Engdegård
2020-10-28 13:50                   ` Stefan Kangas
2020-10-28 11:04                 ` Lars Ingebrigtsen
     [not found]   ` <CADwFkmnXuyh2cAddLtgTNmsSv8av3o9qk98CVcTAzq6B8Lrpkw@mail.gmail.com>
     [not found]     ` <87blgknjze.fsf@gnus.org>
2020-10-30 11:58       ` Stefan Kangas
2020-10-30 12:05         ` Lars Ingebrigtsen
2020-10-30 12:27           ` Stefan Kangas

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=874kmqiqoc.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@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 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.