From: Eshel Yaron via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74218@debbugs.gnu.org, stefankangas@gmail.com, me@fabionatali.com
Subject: bug#74218: [PATCH] Ask confirmation before sending region to search engine.
Date: Thu, 07 Nov 2024 10:12:53 +0100 [thread overview]
Message-ID: <m1ldxv5rvu.fsf@sp-byods-145-109-33-156.wireless.uva.nl> (raw)
In-Reply-To: <86bjyrqvb0.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 07 Nov 2024 10:53:23 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eshel Yaron <me@eshelyaron.com>
>> Cc: Fabio Natali <me@fabionatali.com>, Eli Zaretskii <eliz@gnu.org>,
>> 74218@debbugs.gnu.org
>> Date: Thu, 07 Nov 2024 09:42:29 +0100
>>
>> I too agree that it's a good idea to optionally require confirmation.
>> However, I suspect that a yes/no question is not the best interface in
>> this case. Instead, it's better to simply prepopulate the minibuffer
>> with the contents of the region. Then you confirm with RET and cancel
>> with C-g. In addition, this lets you examine and edit your input.
>
> Why copy the region into the mini-window when it is already shown in
> the current buffer's window? By default, it will be highlighted, but
> if not (e.g., transient-mark-mode was disabled), we could forcibly
> highlight it. Why is that not enough?
While point is always visible, mark can be out of view, so the region
need not be fully visible in the selected window. But more importantly,
using the minibuffer provides a smoother and more consistent UX compared
to an additional yes/no question, IMO.
> Copying stuff into the minibuffer has the disadvantage of resizing the
> mini-window, and then it could hit the limits on such resizes, which
> will prevent the user from seeing large portions of the text, if the
> region is large.
>
> Also, does anyone have an opinion about asking for confirmation only
> for regions that are large enough? E.g., when the region is a single
> word, do we want to ask for confirmation anyway?
I think it makes sense to have an option that is sensitive to the size
of the region, although personally I'd probably stick to "always ask",
especially if the prompt for confirmation isn't too obtrusive.
next prev parent reply other threads:[~2024-11-07 9:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 0:46 bug#74218: [PATCH] Ask confirmation before sending region to search engine Fabio Natali via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 12:34 ` Eli Zaretskii
2024-11-06 13:18 ` Fabio Natali via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 13:38 ` Eli Zaretskii
2024-11-06 15:27 ` Fabio Natali via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-07 1:51 ` Stefan Kangas
2024-11-07 8:42 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-07 8:53 ` Eli Zaretskii
2024-11-07 9:02 ` Robert Pluim
2024-11-07 10:49 ` Eli Zaretskii
2024-11-07 11:03 ` Robert Pluim
2024-11-07 11:05 ` Eli Zaretskii
2024-11-07 11:19 ` Robert Pluim
2024-11-07 11:29 ` Fabio Natali via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-07 11:56 ` Eli Zaretskii
2024-11-07 14:04 ` Fabio Natali via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-07 9:12 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-07 10:52 ` 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=m1ldxv5rvu.fsf@sp-byods-145-109-33-156.wireless.uva.nl \
--to=bug-gnu-emacs@gnu.org \
--cc=74218@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=me@eshelyaron.com \
--cc=me@fabionatali.com \
--cc=stefankangas@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).