From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Neil Conway <nrc@cs.berkeley.edu>
Cc: 7958@debbugs.gnu.org
Subject: bug#7958: Unresponsive visual bell on OSX
Date: Wed, 02 Feb 2011 20:47:58 +0100 [thread overview]
Message-ID: <4D49B4EE.60701@swipnet.se> (raw)
In-Reply-To: <AANLkTimXpELsLWS29N2ij8RD-aa435OCNr0JwkPj-Z20@mail.gmail.com>
I can't reproduce this, starting from -Q and evalling (setq visible-bell t)
and making the bell ding. This on trunk and the emacs-23 branch.
Can you reproduce this when starting with -Q?
Jan D.
Neil Conway skrev 2011-02-02 05.39:
> I'm using Emacs 23.2 (from MacPorts) on OSX 10.6.6. My .emacs includes
> "(setq visible-bell t)", but when I do something that causes the bell
> to be triggered, Emacs becomes very unresponsive (sometimes hanging
> for 3 or 4 seconds, usually (much) longer).
>
> Steps to repro:
> 1. Set visual bell to true
> 2. Run Emacs in console mode; I've tested using Terminal.app and iTerm2
> 3. Open a reasonably-sized file (e.g., 10 lines) and scroll past the
> end of the file, e.g., using C-v
>
> Instead of a visual bell, emacs instead refuses to respond to user
> input for a lengthy period of time. If I attach with gdb, a typical
> call stack looks like:
>
> #0 0x00007fff88c81fca in __semwait_signal ()
> #1 0x00007fff88c81e59 in nanosleep ()
> #2 0x0000000100544fe5 in napms ()
> #3 0x00000001005494fb in delay_output ()
> #4 0x0000000100549738 in tputs ()
> #5 0x0000000100067007 in tty_ring_bell ()
> #6 0x0000000100005ae5 in Fding ()
> #7 0x00000001000f3713 in Feval ()
> [...]
>
> I can actually get emacs to operate normally by forcing the bottom few
> stack frames to return via "ret".
>
> If I remove (setq visual-bell t) from my .emacs, I don't see this behavior.
>
>
next prev parent reply other threads:[~2011-02-02 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 4:39 bug#7958: Unresponsive visual bell on OSX Neil Conway
2011-02-02 19:47 ` Jan Djärv [this message]
2014-02-03 23:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D49B4EE.60701@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=7958@debbugs.gnu.org \
--cc=nrc@cs.berkeley.edu \
/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.