From: Dan Nicolaescu <dann@ics.uci.edu>
To: jidanni@jidanni.org
Cc: 4190@emacsbugs.donarmstrong.com
Subject: bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep
Date: Fri, 21 Aug 2009 07:10:43 -0700 (PDT) [thread overview]
Message-ID: <200908211410.n7LEAhEB019875@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87y6pdctvp.fsf@jidanni.org> (jidanni@jidanni.org's message of "Fri, 21 Aug 2009 19:02:18 +0800")
notabug 4190
thanks
> DN> not beeping is the behavior of prior and next on those platforms.
> 1. Then there should be a way to toggle back on the beeping.
That goal of this package is to be compatible with a platform, we cannot
arbitrarily just turn off features...
> 2. especially as I am not willingly using pc-select, but instead it has been
> foisted upon me via a side effect of some command in
> http://jidanni.org/comp/configuration/.emacs
> Indeed it would take hours of debugging to figure out which.
That does not seem like a good reason to add an extra customization flag
in emacs, a flag that would be used by a single user.
next prev parent reply other threads:[~2009-08-21 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200908202036.n7KKa06C011983@godzilla.ics.uci.edu>
2009-08-18 10:02 ` bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep jidanni
2009-08-20 20:45 ` bug#4190: marked as done (23.1.50; <prior> and <next> of pc-select.el don't beep) Emacs bug Tracking System
2009-09-12 0:40 ` bug#4190: marked as done (allow beeping in pc-select.el) Emacs bug Tracking System
2009-08-21 11:02 ` bug#4190: 23.1.50; <prior> and <next> of pc-select.el don't beep jidanni
2009-08-21 11:10 ` Processed (with 5 errors): " Emacs bug Tracking System
2009-08-21 14:10 ` Dan Nicolaescu [this message]
2009-08-21 14:22 ` jidanni
2009-08-21 17:32 ` Dan Nicolaescu
2009-08-22 0:29 ` 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=200908211410.n7LEAhEB019875@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=4190@emacsbugs.donarmstrong.com \
--cc=jidanni@jidanni.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).