unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: martin rudalics <rudalics@gmx.at>
Cc: 40238@debbugs.gnu.org
Subject: bug#40238: Trying to customize the ispell choices buffer via display-buffer-alist has no effect
Date: Fri, 27 Mar 2020 02:12:46 +0100	[thread overview]
Message-ID: <30426985-CA7C-4DC5-92A8-24CA167ED656@univie.ac.at> (raw)
In-Reply-To: <86f5f87e-cd82-c151-6a7c-b11970da06ac@gmx.at>

The point is that “q” kills the entire (external) ispell process, while “x” or “C-g”  do not. But I found the relevant code in ispell.el, and it was an easy matter to change it so that “q” does the job without asking y-or-n.

Konrad

> Am 26.03.2020 um 19:45 schrieb martin rudalics <rudalics@gmx.at>:
> 
> > I see. So, is there a customization, or some code, which gives, only
> > for the ispell problem, an unconditional kill rather than a y-or-n-p?
> 
> What is the "ispell problem"?  Does typing "x" or C-g not do what you
> want?  My knowledge of ispell.el is limited to the occasional use of M-$
> quitting via C-g.
> 
> martin






  reply	other threads:[~2020-03-27  1:12 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 [this message]
2020-03-27  9:02             ` martin rudalics
2020-03-27 11:22               ` Konrad Podczeck
2020-03-28 18:38                 ` martin rudalics
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=30426985-CA7C-4DC5-92A8-24CA167ED656@univie.ac.at \
    --to=konrad.podczeck@univie.ac.at \
    --cc=40238@debbugs.gnu.org \
    --cc=rudalics@gmx.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).