From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 31094@debbugs.gnu.org
Subject: bug#31094: Code for second solution
Date: Sun, 08 Apr 2018 16:54:51 +0300 [thread overview]
Message-ID: <83fu45ztuc.fsf@gnu.org> (raw)
In-Reply-To: <20180408131700.uwh3bozuqu76xf7m@E15-2016.optimum.net> (message from Boruch Baum on Sun, 8 Apr 2018 09:17:01 -0400)
> Date: Sun, 8 Apr 2018 09:17:01 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: 31094@debbugs.gnu.org
>
> The first code snippet already only changes behavior when the function
> is called with either two or three universal prefix args.
I was under the impression that the first variant was not what you were
promoting.
> The second snippet is controlled by a boolean defcustom variable,
> defaulting to the current long print-out behavior.
That sounds sub-optimal to me: completely changing the behavior of a
command given an option is not the best UI, IMO. Two different
commands are better.
next prev parent reply other threads:[~2018-04-08 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-08 7:39 bug#31094: 25.2: Feature Reuqest: apropos-value: limit scope [CODE INCLUDED] Boruch Baum
2018-04-08 11:09 ` bug#31094: Code for second solution Boruch Baum
2018-04-08 13:06 ` Eli Zaretskii
2018-04-08 13:17 ` Boruch Baum
2018-04-08 13:54 ` Eli Zaretskii [this message]
2018-04-08 14:13 ` Boruch Baum
2018-04-08 16:32 ` Eli Zaretskii
2022-01-23 14:45 ` bug#31094: 25.2: Feature Reuqest: apropos-value: limit scope [CODE INCLUDED] Lars Ingebrigtsen
2022-01-23 18:02 ` Juri Linkov
2022-01-23 18:29 ` Lars Ingebrigtsen
2022-01-23 20:02 ` Juri Linkov
2022-01-24 9:26 ` Lars Ingebrigtsen
2022-01-24 17:58 ` Juri Linkov
2022-01-24 18:33 ` Lars Ingebrigtsen
2022-01-24 19:19 ` Juri Linkov
2022-01-25 12:03 ` Lars Ingebrigtsen
2022-01-25 2:06 ` Michael Heerdegen
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=83fu45ztuc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31094@debbugs.gnu.org \
--cc=boruch_baum@gmx.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 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.