unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Raffaele Ricciardi <rfflrccrd@gmail.com>
Cc: 14807@debbugs.gnu.org
Subject: bug#14807: 24.3; Enhancement request: let options in customize group buffers to start out visible
Date: Tue, 10 May 2022 15:44:07 +0200	[thread overview]
Message-ID: <877d6th594.fsf@gnus.org> (raw)
In-Reply-To: <51D882ED.8070205@gmail.com> (Raffaele Ricciardi's message of "Sat, 06 Jul 2013 22:49:49 +0200")

Raffaele Ricciardi <rfflrccrd@gmail.com> writes:

> "*** Options in customize group buffers start out hidden if not
> customized.  Use the arrow to the left of the option name to toggle
> visibility."
>
> Would it be possible to make such behaviour customizable for users
> that would prefer the old behaviour?  The old behaviour let users
> check quickly what the behaviour of a package was supposed to be,
> according to the value of its various options.  The new behaviour
> requires users to click on each option to get a glimpse of what to
> expect from a mode.  My guess is that the new behaviour aims to lessen
> the possibility of accidental edits, but that is not an issue with
> more experienced users.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Many customization groups are very large, and some of the widgets take
up a lot of space.  So in my opinion, a user option like this wouldn't
be used by a lot of people, so it's not worth adding, and I'm therefore
closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-05-10 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-06 20:49 bug#14807: 24.3; Enhancement request: let options in customize group buffers to start out visible Raffaele Ricciardi
2022-05-10 13:44 ` Lars Ingebrigtsen [this message]

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=877d6th594.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=14807@debbugs.gnu.org \
    --cc=rfflrccrd@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 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).