From: martin rudalics <rudalics@gmx.at>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: 40238@debbugs.gnu.org
Subject: bug#40238: Trying to customize the ispell choices buffer via display-buffer-alist has no effect
Date: Sat, 28 Mar 2020 19:38:16 +0100 [thread overview]
Message-ID: <afda1c34-0287-b8f9-e0cf-d17b4b93c6e1@gmx.at> (raw)
In-Reply-To: <54CA7F3C-6119-46D0-9DCF-B163DDDC7117@univie.ac.at>
> This I dont’ know. I just changed the code, in ispell.el, lines 2320 and 2326, from
>
> ((= char ?q)
> (if (y-or-n-p "Really kill Ispell process? ")
> (progn
> (ispell-kill-ispell t) ; terminate process.
> (setq ispell-quit (or (not ispell-checking-message)
> (point))
> ispell-pdict-modified-p nil))
> t)) ; continue if they don't quit.
>
> into
>
> ((= char ?q)
> ;; (if (y-or-n-p "Really kill Ispell process? ")
> (progn
> (ispell-kill-ispell t) ; terminate process.
> (setq ispell-quit (or (not ispell-checking-message)
> (point))
> ispell-pdict-modified-p nil))
> ;; t)
> ) ; continue if they don't quit.
We could reserve "Q" for killing Ispell without asking questions. But I
have no idea of the ispell mnemonics and already find "q" for killing
and "X" for suspending (which never suspends anything here IIUC) quite
confusing. Maybe an ispell expert can help us.
martin
next prev parent reply other threads:[~2020-03-28 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 14:56 bug#40238: Trying to customize the ispell choices buffer via display-buffer-alist has no effect Konrad Podczeck
2020-03-26 15:29 ` martin rudalics
2020-03-26 15:52 ` Konrad Podczeck
2020-03-26 16:23 ` Konrad Podczeck
2020-03-26 17:36 ` martin rudalics
2020-03-26 18:05 ` Konrad Podczeck
2020-03-26 18:45 ` martin rudalics
2020-03-27 1:12 ` Konrad Podczeck
2020-03-27 9:02 ` martin rudalics
2020-03-27 11:22 ` Konrad Podczeck
2020-03-28 18:38 ` martin rudalics [this message]
2022-02-10 7:20 ` Lars Ingebrigtsen
2022-03-12 22:42 ` Lars Ingebrigtsen
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=afda1c34-0287-b8f9-e0cf-d17b4b93c6e1@gmx.at \
--to=rudalics@gmx.at \
--cc=40238@debbugs.gnu.org \
--cc=konrad.podczeck@univie.ac.at \
/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).