unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: casouri@gmail.com, dim1212k@gmail.com, yantar92@gmail.com,
	emacs-devel@gnu.org, adam@alphapapa.net, eliz@gnu.org
Subject: RE: Request for pointers and advice: displaying several buffers inside a single window
Date: Sat, 11 Apr 2020 22:09:28 -0700 (PDT)	[thread overview]
Message-ID: <2f47e193-63d4-4ffc-9bd1-5cfcb0da915e@default> (raw)
In-Reply-To: <E1jNSa2-0003Co-RX@fencepost.gnu.org>

>   > If you load that library then you can use
>   > these keys on prefix key C-x n M-=:
>   >
>   > v - isearchp-toggle-anti-zones-invisible
>   > V - isearchp-toggle-zones-invisible
>   > ~ - isearchp-toggle-complementing-domain
>   > d - isearchp-toggle-dimming-outside-search-area
> 
> Can anyone come up with a simpler interface for this?
> One that reduces the amount that a user needs to memorize
> before using the feature?

You don't need to memorize anything.  And certainly
not in order to be able to use the feature.  The
predefined keys are just for convenience.

And you can bind any of the commands to whatever
keys you like.

By default, the zone commands are on prefix key
`C-x n', which Emacs uses for narrowing commands
(Emacs binds it to keymap `narrow-map').

(If you use isearch-prop.el or highlight.el then
zones.el adds additional zone commands to the same
keymap.)

I chose that keymap and prefix key for zones mainly
because zones.el optionally advises the standard
narrowing commands (`narrow-region' etc.), so they 
automatically add a narrowing (restriction) as a
zone.  (You can then cycle among restrictions etc.)

But you can use any other keymap or prefix key.

I decided to put all of the toggle commands for use
with zones on keymap `zz-toggles-map'.  And I put
that map on prefix key `M-=' in `narrow-map'.  But
you can use a different prefix key for that map, or
ignore it.

If you do want to use the predefined bindings, and
you don't remember some, using either `C-x n C-h' or
`C-h M-k narrow-map' (`describe-keymap') tells you:

narrow-map
----------

Keymap for narrowing commands.

key             binding
---             -------

C-d             zz-delete-zone
C-r             isearchp-zones-backward
C-s             isearchp-zones-forward
ESC             Prefix Command
#               zz-select-zone-by-id-and-text
A               zz-add-zone-and-unite
C               zz-clone-and-unite-zones
D               isearchp-remove-dimming
H               hlt-highlight-regions-in-buffers
L               zz-set-zones-from-highlighting
P               isearchp-put-prop-on-zones
R               zz-set-zones-matching-regexp
a               zz-add-zone
c               zz-clone-zones
d               narrow-to-defun
h               hlt-highlight-regions
l               zz-add-zones-from-highlighting
n               narrow-to-region
p               narrow-to-page
r               zz-add-zones-matching-regexp
s               zz-select-zone-repeat
u               zz-unite-zones
v               zz-set-izones-var
w               widen
x               zz-narrow-repeat

C-M-r           isearchp-zones-backward-regexp
C-M-s           isearchp-zones-forward-regexp
M-%             zz-query-replace-zones
M-=             zz-toggles-map
C-M-%           zz-query-replace-regexp-zones

M-= V           isearchp-toggle-zones-invisible
M-= d           isearchp-toggle-dimming-outside-search-area
M-= v           isearchp-toggle-anti-zones-invisible
M-= ~           isearchp-toggle-complementing-domain



  reply	other threads:[~2020-04-12  5:09 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 11:54 Request for pointers and advice: displaying several buffers inside a single window Dmitrii Korobeinikov
2020-04-03 13:07 ` Eli Zaretskii
2020-04-04 22:44   ` Dmitrii Korobeinikov
2020-04-05 14:08     ` Adam Porter
2020-04-05 22:55   ` Dmitrii Korobeinikov
2020-04-10 14:45     ` Yuan Fu
2020-04-10 15:35       ` Ihor Radchenko
2020-04-10 16:43         ` Eli Zaretskii
2020-04-10 17:46           ` Ihor Radchenko
2020-04-10 18:07             ` Eli Zaretskii
2020-04-10 18:37               ` Ihor Radchenko
2020-04-10 19:01                 ` Drew Adams
2020-04-10 19:19                   ` Ihor Radchenko
2020-04-10 20:29                     ` Drew Adams
2020-04-11  8:11                       ` Ihor Radchenko
2020-04-11 17:23                         ` Drew Adams
2020-04-12  2:42                           ` Richard Stallman
2020-04-12  5:09                             ` Drew Adams [this message]
2020-04-12  5:15                               ` Drew Adams
2020-04-13  2:21                               ` Richard Stallman
2020-04-13  5:23                                 ` Drew Adams
2020-04-12 23:54                             ` Juri Linkov
2020-04-13  5:23                               ` Drew Adams
2020-04-12 14:25                           ` Ihor Radchenko
2020-04-12 16:38                             ` Drew Adams
2020-04-10 19:12                 ` Eli Zaretskii
2020-04-10 19:25                   ` Ihor Radchenko
2020-04-10 19:34                   ` Ihor Radchenko
2020-04-11  7:34                     ` Eli Zaretskii
2020-04-11  8:35                       ` Ihor Radchenko
2020-04-11  9:25                         ` Eli Zaretskii
2020-04-10 19:09         ` Dmitrii Korobeinikov
2020-04-11  0:05           ` chad
2020-04-11  8:22             ` Eli Zaretskii
2020-04-11  7:30           ` Eli Zaretskii
2020-04-11  7:56             ` Dmitrii Korobeinikov
2020-04-11  8:26               ` Eli Zaretskii
2020-04-11 10:01                 ` Dmitrii Korobeinikov
2020-04-03 18:30 ` [SPAM UNSURE] " Stephen Leake
2020-04-05 13:18   ` Robert Pluim
2020-04-05 20:35     ` Dmitrii Korobeinikov

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=2f47e193-63d4-4ffc-9bd1-5cfcb0da915e@default \
    --to=drew.adams@oracle.com \
    --cc=adam@alphapapa.net \
    --cc=casouri@gmail.com \
    --cc=dim1212k@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=yantar92@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).