From: Michael Heerdegen <michael_heerdegen@web.de>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 31094@debbugs.gnu.org
Subject: bug#31094: 25.2: Feature Reuqest: apropos-value: limit scope [CODE INCLUDED]
Date: Tue, 25 Jan 2022 03:06:18 +0100 [thread overview]
Message-ID: <87zgnkk1r9.fsf@web.de> (raw)
In-Reply-To: <20180408073916.d5lsceul3gpj34l3@E15-2016.optimum.net> (Boruch Baum's message of "Sun, 8 Apr 2018 03:39:16 -0400")
Boruch Baum <boruch_baum@gmx.com> writes:
> Some of this can be reduced when considegring that in most cases, I know
> in advance that a value will be present in some very commonly used huge
> variables, that won't be of use to me (eg. kill-ring,
> minibuffer-history).
If you are interested in alternative approaches:
In my config I have added a query for a maximal length of the (printed)
value. 0 means "use any", but a positive value filters all variables
with bindings wider than the given limit.
I chose this way because typically you get lots of results, too many to
view them one by one, so most of the time I use isearch to find the
stuff I'm interested in. With a folding approach, the output looks
nicer, but it still contains a lot of stuff I'm surely not interested
in. Most of the time these huge list values are irrelevant for what you
are searching for.
Michael.
prev parent reply other threads:[~2022-01-25 2:06 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
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 [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=87zgnkk1r9.fsf@web.de \
--to=michael_heerdegen@web.de \
--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 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).