From: Toon Claes <toon@iotcl.com>
To: John Wiegley <jwiegley@gmail.com>
Cc: Alan Third <alan@idiocy.org>,
22746@debbugs.gnu.org, Xu Xin <railwaycat@gmail.com>,
adrian.b.robert@gmail.com, Anders Lindgren <andlind@gmail.com>
Subject: bug#22746: 25.0.90; OS X: Visual bell hard to see
Date: Wed, 03 Aug 2016 00:00:52 +0200 [thread overview]
Message-ID: <m2d1lq25m3.fsf@MacToonPro-2.local> (raw)
In-Reply-To: <m2futlewux.fsf@newartisans.com> (John Wiegley's message of "Fri, 13 May 2016 09:39:02 -0700")
John Wiegley <jwiegley@gmail.com> writes:
> Alan Third <alan@idiocy.org> writes:
>
>>> There already is an easy way to set `ring-bell-function', so I'm really not
>>> sure what you are asking.
>
> Sorry, I just didn't know about it. :)
So, do we keep the current behavior and rely on third-party packages
like echo-bell.el to customize the behavior?
Or, if we should chose to customize built-in the behavior, maybe a few more
settings should be considered:
- Duration: Compared to echo-bell-mode, the default warning sign is
shown way too long. A configurable duration would be nice.
- Image: Maybe people also would like to specify the image shown as
visible bell (e.g. Pikachu: https://twitter.com/ErgoEmacs/status/759546738306748416/photo/1 )
TBH, I suggest to keep the current behavior and let user to set
`ring-bell-function' if they like something different.
Regards,
Toon
prev parent reply other threads:[~2016-08-02 22:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 8:50 bug#22746: 25.0.90; OS X: Visual bell hard to see Adrian Robert
2016-02-20 12:58 ` Anders Lindgren
2016-02-20 15:18 ` Xu Xin
2016-03-08 23:17 ` John Wiegley
2016-05-08 9:15 ` Alan Third
2016-05-11 18:20 ` John Wiegley
2016-05-12 19:17 ` Drew Adams
2016-05-13 15:41 ` Alan Third
2016-05-13 15:45 ` Drew Adams
2016-05-13 16:03 ` Alan Third
2016-05-13 16:39 ` John Wiegley
2016-08-02 22:00 ` Toon Claes [this message]
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=m2d1lq25m3.fsf@MacToonPro-2.local \
--to=toon@iotcl.com \
--cc=22746@debbugs.gnu.org \
--cc=adrian.b.robert@gmail.com \
--cc=alan@idiocy.org \
--cc=andlind@gmail.com \
--cc=jwiegley@gmail.com \
--cc=railwaycat@gmail.com \
/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).