From: Michael Heerdegen <michael_heerdegen@web.de>
To: 14192@debbugs.gnu.org
Subject: bug#14192: 24.3.50; recursive edit while running ispell not working usefully
Date: Fri, 12 Apr 2013 18:51:14 +0200 [thread overview]
Message-ID: <87ppxzd75p.fsf@web.de> (raw)
In-Reply-To: <87hajbkd3v.fsf@web.de> (Michael Heerdegen's message of "Fri, 12 Apr 2013 17:00:52 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Hi,
>
> I think the most common use of entering a recursive edit in an ispell
> session (C-r) would be to modify the checked buffer - especially, to
> substitute the currently checked word with some other text. But
> whenever I exit the recursive edit (C-M-c), the deleted text reappears
> and is highlighted again as unknown by ispell. I see this in emacs -Q,
> e.g. after M-x ispell-buffer in *scratch*.
Some comments after debugging a bit:
`ispell-process-line' sets the variable `replace' to the result of
`ispell-command-loop'. `ispell-command-loop', however, returns the
_old_ word. Why?
In `ispell-command-loop', search for the cond-clause of (= char ?\C-r).
The clause returns (list word nil), where `word' is the (old, unchanged)
current word. There is this comment at that position:
; recheck starting at this word.
If I change the clause so that it just returns nil, the bug is fixed,
but the replaced text is not being checked again (I could live with
that).
As a fix, we could try to return something reflecting the change that
was maybe made in the buffer.
Regards,
Michael.
next prev parent reply other threads:[~2013-04-12 16:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 15:00 bug#14192: 24.3.50; recursive edit while running ispell not working usefully Michael Heerdegen
2013-04-12 16:51 ` Michael Heerdegen [this message]
2024-01-10 11:19 ` Stefan Kangas
2024-01-11 3:13 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 6:49 ` Eli Zaretskii
2024-01-11 23:14 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13 7:57 ` Stefan Kangas
2024-01-14 1:13 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-11 20:35 ` Stefan Kangas
2024-01-11 23:30 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 7:44 ` Eli Zaretskii
2024-01-14 1:25 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 6:29 ` Eli Zaretskii
2024-01-16 19:23 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-16 19:28 ` Eli Zaretskii
2024-01-27 9:09 ` 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=87ppxzd75p.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=14192@debbugs.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 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.