unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Boruch Baum <boruch_baum@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 30085@debbugs.gnu.org, Kim Storm <storm@cua.dk>
Subject: bug#30085: 25.2: Documentation for cua-rectangle-mark-mode
Date: Fri, 26 Jan 2018 13:57:41 -0500	[thread overview]
Message-ID: <20180126185741.4lkookdzlk7adn7w@E15-2016.optimum.net> (raw)
In-Reply-To: <834lnq3o4i.fsf@gnu.org>

I realize that some elisp code that I wrote for another purpose might be
useful for this mode.

  https://github.com/Boruch-Baum/swiper

One of the elements of `cua-rectangle-mark-mode' is a one-line cheat-sheet
style message of default keybindings of basic features, itself by
default bound to `C-?'.

In my referenced link above, I provide for `swiper' two features:

1) Cheat-sheet style messages that appear above the minibufer.

1.1) Keybinding for the messages (`M'?' by default) turns on the
     display, scrolls to the next message, and turns off the display.

1.2) The default message(s) may be supplemented or replaced by messages
     set by the user.

1.3) The message format includes an easy method to ensure that changing
     a keybinding does not require going back and editing the message.

2) Visual feedback of the current state of the mode. In the case of
   swiper, this is a single-line indication of case-fold status, regex
   method, currently selected action, and auto status. This feedback
   line appears just above the minibuffer.

The elisp code should be usable for other "complicated" emacs commands
without much of any modification. In the case of `swiper', it was
necessary to make a change to function `ivy-read' because of its
recursive nature and its use of unwind.

In the case of `swiper', a pull request has been made to the developer,
and is waiting for feedback.

An example of another candidate for this proposed feature would be
`isearch-forward'.

I would like to eventually offer it in generic form to emacs, but as for
now it hasn't even gotten approved by `swiper'.

-- 
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1  7286 0036 9E45 1595 8BC0





  reply	other threads:[~2018-01-26 18:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12  7:14 bug#30085: 25.2: Documentation for cua-rectangle-mark-mode Boruch Baum
2018-01-12  9:22 ` Eli Zaretskii
2018-01-12 11:00   ` Kim Storm
2018-01-12 18:53     ` Eli Zaretskii
2018-01-26 18:57       ` Boruch Baum [this message]
2018-03-21 12:48       ` Boruch Baum
2020-10-27  1:50         ` Stefan Kangas
2020-10-28  6:40           ` Boruch Baum
2020-12-16  7:43           ` Boruch Baum
2018-01-12 11:06   ` Kim Storm
2019-10-19  1:21 ` Stefan Kangas
2019-10-19  6:39   ` Eli Zaretskii
2020-10-27  1:39     ` Stefan Kangas
2019-10-23 10:56   ` Boruch Baum
2019-10-23 11:10     ` Stefan Kangas
2019-10-28 10:41       ` Lars Ingebrigtsen
2019-10-28 16:11         ` Eli Zaretskii

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=20180126185741.4lkookdzlk7adn7w@E15-2016.optimum.net \
    --to=boruch_baum@gmx.com \
    --cc=30085@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=storm@cua.dk \
    /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).