unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Ergus <spacibba@aol.com>
Cc: emacs-devel@gnu.org, Drew Adams <drew.adams@oracle.com>,
	Juri Linkov <juri@linkov.net>
Subject: Re: isearch region or thing at point.
Date: Fri, 03 May 2019 17:28:57 +0100	[thread overview]
Message-ID: <87lfznbiye.fsf@tcd.ie> (raw)
In-Reply-To: <20190501160344.qfh7fslj23meprzu@Ergus> (Ergus's message of "Wed,  1 May 2019 18:03:44 +0200")

Ergus <spacibba@aol.com> writes:

> I would prefer a keybind for it, even a different one, but otherwise
> nobody will use the command and the people will continue using
> workarounds like now. I didn't take M-y or C-y because they were already
> taken and M-w was not colliding with anything in my emacs -Q.
>
> Many people just find the emacs commands while using emacs (thanks to
> which-key or counsel-completion or Helm they discover the keybinds) and
> commands without a keybind are VERY less visible/accessible unless they
> explicitly know and configure a bind for them. The users find them only
> after reading a lot of documentation in the manual (which no many people
> do). But which-key simplifies the life a lot. Specially for new users.

FWIW, docstrings of mode functions, etc. can always include a synoptic
list of useful commands and/or bindings.  It's not always necessary to
resort to reading the code or manual, and shouldn't be.

> In fact the "right" to do (IN MY OPINION) is to define a keybind for all
> the commands like this. (which insert text from active-region into
> minibuffer once in the minibuffer, that could help for
> replace-regex/find-file/flyspell/and many others) that will solve a lot
> of collisions and will simplify the user experience a lot. (memorization)
>
> We have a lot of package that already proposes patches for this issue
> trying to figure out somehow when to insert text from region (or near to
> point) to the minibuffer (all the thing-at-point-like packages in elpa
> && melpa are workarounds for this general issue).

I doubt all of them are "workarounds" per se, so much as customisations,
extensions, etc.

> BTW: The isearch+ package isn't in elpa||melpa?? I can't find it in the
> packages-list, so probably that's why I didn't check it before (I try to
> avoid this kind of issues as much as possible before proposing
> changes). Is there any reason why it is not in elpa||melpa? Because I
> don't know anyone who uses it; for sure because they don't know it.

See https://emacs.stackexchange.com/q/38553/15748.

> Let's wait for Eli, Basil and the others... Maybe they will propose a
> genial solution (as usual).

Sorry, I don't usually take a stance on things like default key bindings
and the like, because everyone has different preferences and I know I
can (almost) always adapt them to my liking.  Besides, I'm no authority
around here.

How well/prominently a mode advertises/documents its usage is a
different matter.

Thanks,

-- 
Basil



  parent reply	other threads:[~2019-05-03 16:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27  0:14 isearch region or thing at point Ergus
2019-04-27  2:15 ` Basil L. Contovounesios
2019-04-29  0:41   ` Ergus
2019-04-29  1:30     ` Ergus
2019-04-29  1:31     ` Ergus
2019-04-29 19:41     ` Juri Linkov
2019-04-29 20:50       ` Ergus
2019-04-30 15:39       ` Drew Adams
2019-04-30 16:57         ` Ergus
2019-04-30 19:58           ` Juri Linkov
2019-04-30 16:25       ` Ergus
2019-04-30 18:49         ` Noam Postavsky
2019-04-30 19:03           ` Ergus
2019-04-30 19:24             ` Noam Postavsky
2019-04-30 20:05               ` Ergus
2019-04-30 20:38                 ` Noam Postavsky
2019-04-30 22:39         ` Basil L. Contovounesios
2019-04-30 23:16           ` Ergus
2019-04-30 23:33             ` Basil L. Contovounesios
2019-05-01  0:13               ` Ergus
2019-05-01 20:57                 ` Juri Linkov
2019-05-03 16:27                 ` Basil L. Contovounesios
2019-05-01 11:20               ` Ergus
2019-05-01 14:33                 ` Drew Adams
2019-05-01 16:03                   ` Ergus
2019-05-01 16:25                     ` Drew Adams
2019-05-03 16:28                     ` Basil L. Contovounesios [this message]
2019-05-04  9:29                     ` Eli Zaretskii
2019-05-03 16:28                 ` Basil L. Contovounesios
2019-05-04  9:26                 ` Eli Zaretskii
2019-05-04 12:15                   ` Ergus
2019-05-04 14:17                     ` Drew Adams
2019-05-04 14:56                       ` Ergus
2019-05-04 15:24                         ` Drew Adams
2019-05-04 21:06                           ` Juri Linkov
2019-05-04 22:40                             ` Drew Adams
2019-05-06 19:41                               ` Juri Linkov
2019-05-07  2:56                                 ` Drew Adams
2019-05-07 19:56                                   ` Ergus

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=87lfznbiye.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=spacibba@aol.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).