From: Drew Adams <drew.adams@oracle.com>
To: Mirko Vukovic <mirko.vukovic@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: hideshow docstring in elisp or common lisp code
Date: Tue, 13 Nov 2018 07:11:24 -0800 (PST) [thread overview]
Message-ID: <8e55ed17-f584-4040-9d21-3e0b273d6895@default> (raw)
In-Reply-To: <e30dedf4-7fc5-4b11-bf68-7586f3e23bae@default>
You also have similar command
`isearchp-toggle-zone/anti-zone-visibility', which
toggles between showing only the zones (in this case
only the doc strings) and showing only the anti-zones
(in this case all but the doc strings).
Related commands:
`isearchp-make(-anti)-zones-visible',
`isearchp-make(-anti)-zones-invisible', and
`isearchp-toggle-anti-zones-invisible'.
And `isearchp-add-prop-to-other-prop-zones' and
`isearchp-put-prop-on-zones', which you can use to
add a text property such as `invisible' to zones.
And commands to search just within zones:
`isearchp-zones-(backward|forward)(-regexp)'.
By default, the anti-zones are dimmed a bit while
you search, to help the zones to stand out. This is
controlled by options `isearchp-dimming-color' and
`isearchp-dim-outside-search-area-flag'. The latter
option (thus the dimming) can be toggled by `C-M-S-d'
during Isearch.
And command `isearchp-toggle-complementing-domain'
flips whether to search the zones or the anti-zones.
It's bound to `C-M-~' during Isearch. So, for
example, having defined doc strings as the zones,
you can search either doc strings or everything but
doc strings, just by hitting `C-M-~'.
All of the commands just mentioned are from library
`isearch-prop.el'. But the ones specifically for
use with zones require also library `zones.el'.
next prev parent reply other threads:[~2018-11-13 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 22:33 hideshow docstring in elisp or common lisp code Mirko Vukovic
2018-11-09 2:12 ` Michael Heerdegen
2018-11-11 9:03 ` Andreas Röhler
2018-11-13 3:34 ` Drew Adams
2018-11-13 15:11 ` Drew Adams [this message]
[not found] <mailman.3529.1541470097.1284.help-gnu-emacs@gnu.org>
2018-11-06 19:05 ` Emanuel Berg
2018-11-08 13:57 ` Mirko
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=8e55ed17-f584-4040-9d21-3e0b273d6895@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mirko.vukovic@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.
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).