all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36670@debbugs.gnu.org
Subject: bug#36670: 27.0.50; Wishlist: describe-face should use the new help-buffer infrastructure
Date: Sat, 21 Sep 2019 09:41:51 +0300	[thread overview]
Message-ID: <831rwarw0g.fsf@gnu.org> (raw)
In-Reply-To: <87ef0a60uu.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat,  21 Sep 2019 00:48:09 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 21 Sep 2019 00:48:09 +0200
> 
> Lars Ingebrigtsen <larsi@gnus.org> writes:
> 
> > M-x describe-variable (and -function) uses a new infrastructure based on
> > help-fns-describe-{variable,function}-functions that registers a bunch
> > of little bits to be output, which gives more flexibility.
> >
> > describe-face should use the same thing, and be moved to help-fns.el.
> 
> I have now done this on the trunk, as previously requested by Stefan M.

What does this mean in practice?  I see nothing about this in NEWS or
in the manuals, which makes me wonder how is this "more flexible".  I
guess there were some discussions, but neither the log message nor the
bug discussion mentions any other sources of information.  Could you
please point to those discussions, or fill the void by explaining what
additional flexibility do we gain?  This is for future forensics, if
for nothing else.

Thanks.





  reply	other threads:[~2019-09-21  6:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15 16:14 bug#36670: 27.0.50; Wishlist: describe-face should use the new help-buffer infrastructure Lars Ingebrigtsen
2019-09-20 22:48 ` Lars Ingebrigtsen
2019-09-21  6:41   ` Eli Zaretskii [this message]
2019-09-21  7:44     ` Lars Ingebrigtsen
2019-09-21  8:22       ` Eli Zaretskii
2019-09-21  8:38         ` Lars Ingebrigtsen
2019-09-21  9:05           ` Eli Zaretskii
2019-09-21  9:10             ` 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=831rwarw0g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=36670@debbugs.gnu.org \
    --cc=larsi@gnus.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.