unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Sean O'Rourke <sean@drdirtbag.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65069@debbugs.gnu.org
Subject: bug#65069: ispell-region does not preserve the region
Date: Tue, 8 Aug 2023 20:21:14 -0600	[thread overview]
Message-ID: <BE8F7FB7-38D6-49F0-A8FD-30D6B4412925@drdirtbag.com> (raw)
In-Reply-To: <83350xu8qz.fsf@gnu.org>

Thanks for the prompt and thorough response, Eli.  My use case is that I store multiple blog posts in a single file.  When I compose one, I select it, run ispell-region, then copy-paste the corrected text into a webpage.  Ispell changing the region is therefore unhelpful to me, but if that’s an uncommon usage pattern, I can just defadvice it myself to get the old behavior back — no need for another user option.

Sean

> On Aug 5, 2023, at 3:41 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Sean O'Rourke <sean@drdirtbag.com>
>> Date: Fri, 4 Aug 2023 05:21:13 -0600
>> 
>> Before Emacs 29.1, selecting a region and running ispell-region would leave point and mark unchanged.  Now it leaves one end of the region at the last place ispell stopped.  I don’t know if this is intended behavior, but it is less convenient than the way it worked before.
> 
> It was deliberate, see bug#14816 (and the corresponding change to the
> doc string of ispell-region).  With Emacs 29.1, the region is left
> around the portion of text that was not yet spell-checked, so it is
> more useful for continuing spell-checking.  I guess we could add a
> user option to avoid doing that, for those who prefer the old
> behavior, but is this really needed?






  reply	other threads:[~2023-08-09  2:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 11:21 bug#65069: ispell-region does not preserve the region Sean O'Rourke
2023-08-05  9:41 ` Eli Zaretskii
2023-08-09  2:21   ` Sean O'Rourke [this message]
2023-08-09 11:29     ` Eli Zaretskii
2023-08-20 17:04       ` Juri Linkov

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=BE8F7FB7-38D6-49F0-A8FD-30D6B4412925@drdirtbag.com \
    --to=sean@drdirtbag.com \
    --cc=65069@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).