unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Alan Third <alan@idiocy.org>
Cc: Xu Xin <railwaycat@gmail.com>, John Wiegley <jwiegley@gmail.com>,
	adrian.b.robert@gmail.com, 22746@debbugs.gnu.org,
	Anders Lindgren <andlind@gmail.com>
Subject: bug#22746: 25.0.90; OS X: Visual bell hard to see
Date: Fri, 13 May 2016 08:45:43 -0700 (PDT)	[thread overview]
Message-ID: <3dfcbc7a-8680-485c-9e37-570c9e7a3191@default> (raw)
In-Reply-To: <20160513154154.GA53701@breton.holly.idiocy.org>

> > > > What would be the ideal visible bell? The top and bottom lines
> flashing or
> > > > flashing the entire window, or do people like the warning icon?
> > >
> > > Personally I'd prefer top and bottom lines. Every better: give me a
> > > defcustom to decide between icon, top/bottom, whole screen, or some
> > > alerting function (which in future would allow for connecting with
> alert.el).
> >
> > +1.  And not just for OS X.
> >
> > It could also incorporate what echo-bell.el does, or similar,
> > as one of the option values.
> 
> Am I right in thinking that this would just require exposing the bell
> functions to Emacs lisp, and then providing a simple way to set
> ring-bell-function? Or have I misunderstood?

Are you asking me?  I only suggested perhaps incorporating something
like what echo-bell does, as one of the possible visual-bell behaviors
for the defcustom.

There already is an easy way to set `ring-bell-function', so I'm really
not sure what you are asking.





  reply	other threads:[~2016-05-13 15:45 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 [this message]
2016-05-13 16:03                 ` Alan Third
2016-05-13 16:39                   ` John Wiegley
2016-08-02 22:00                     ` Toon Claes

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=3dfcbc7a-8680-485c-9e37-570c9e7a3191@default \
    --to=drew.adams@oracle.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).