all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
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:53:23 +0200	[thread overview]
Message-ID: <86bjyrqvb0.fsf@gnu.org> (raw)
In-Reply-To: <m1bjyr77uy.fsf@sp-byods-145-109-33-156.wireless.uva.nl> (message from Eshel Yaron on Thu, 07 Nov 2024 09:42:29 +0100)

> 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?

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?





  reply	other threads:[~2024-11-07  8:53 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bjyrqvb0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74218@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.