unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: hmelman@gmail.com, 15748@debbugs.gnu.org
Subject: bug#15748: 24.3.50; `customize-group': Provide a way to hide/show all values
Date: Wed, 11 May 2022 16:49:42 +0300	[thread overview]
Message-ID: <83r150qivd.fsf@gnu.org> (raw)
In-Reply-To: <87fslgcmzv.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  11 May 2022 13:44:20 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: hmelman@gmail.com,  15748@debbugs.gnu.org
> Date: Wed, 11 May 2022 13:44:20 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Thanks, but can we have some documentation about its usage?  For
> > starters, in which buffers it is supposed to be used, and how?  I
> > thought this was for the buffer created by customize-group, but there
> > it seems I can use 'H' only once: after that one time, which reveals
> > all the variables, any subsequent 'H' press says "Invalid widget type"
> > and does nothing.  (I used the buffer created for the 'display' group,
> > in case it matters.)
> 
> Yes, it matters -- I was testing in a group with a different widget
> selection, so I didn't see this bug.  Now fixed on the trunk.

It now works in "*Customize Group*" buffers I tried, but the problem
is still there in some other similar cases.  For example, try

  M-x customize-apropos RET window RET

In the resulting buffer, the second 'H' still gets the same Invalid
widget error.  The same happens in a buffer created by
customize-faces.

Also, what about "M-x customize-browse"?  The buffer looks
differently, but don't we want 'H' to do the same there?

> > I tried to understand whether I did something wrong by reading the doc
> > string of the new command, but it didn't add anything to my
> > understanding; it doesn't even say which "widgets" is it talking
> > about.
> >
> > I think we need to improve the user documentation of this new feature.
> 
> It just toggles the visibility, like that arrow thing.  I don't know
> what further can be said.

I've now made the doc string more detailed.





  reply	other threads:[~2022-05-11 13:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 15:09 bug#15748: 24.3.50; `customize-group': Provide a way to hide/show all values Drew Adams
2021-10-23 18:49 ` Howard Melman
2022-05-10 15:48   ` Lars Ingebrigtsen
2022-05-10 16:44     ` Howard Melman
2022-05-10 17:04     ` Eli Zaretskii
2022-05-11 11:44       ` Lars Ingebrigtsen
2022-05-11 13:49         ` Eli Zaretskii [this message]
2022-05-12  0:28           ` Lars Ingebrigtsen
2022-05-12  6:40             ` Eli Zaretskii
2022-05-10 17:15     ` Drew Adams
2022-05-11 15:02       ` Howard Melman
2022-05-11 15:12         ` Lars Ingebrigtsen
2022-05-11  7:05     ` Juri Linkov
2022-05-11 11:45       ` 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

  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=83r150qivd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15748@debbugs.gnu.org \
    --cc=hmelman@gmail.com \
    --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 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).