unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: RE: can we please define a face for compile.el mouseover?
Date: Tue, 15 Feb 2011 14:41:58 -0800	[thread overview]
Message-ID: <F214997A3A5646FEA54A0723D1504E21@us.oracle.com> (raw)
In-Reply-To: <jwvipwlvw9m.fsf-monnier+emacs@gnu.org>

> > Can we please define a face to be used for the `mouse-face' 
> > property in the `compile.el' code?
> 
> Why do you want a different mouse-face in compile.el than elsewhere?

I want users to _be able_ to customize mouseover appearance differently in one
context from another.  I don't want to _require_ them to use different faces any
more than I want to require them to use the same face (the case today, and not
even customizable).

In my own case, I want mouseover in compilation/grep buffers to just underline
the text.  But I generally want mouseover to use face `highlight' elsewhere.
And on the mode line I want it to use face `mode-line-highlight' - which it does
(that's a raised box BTW - it has no relation to the mouseover appearance
elsewhere).

I also apply `mouse-face' to the whole grep/compilation line, but that's just
me.  I believe that users should get visual feedback indicating that they can
click anywhere on the line.  Also, mousing over the line anywhere (e.g. far off
to the right) highlights (underlines) the whole line, making it easy to visually
scan rows (like using a ruler) - it's especially useful with sparse table data
or code.

And of course I've mentioned all of this umpteen times in the past...
But thanks for asking. ;-)

> > It doesn't make sense to hard-code `highlight' in this code.
> > For a user to be able to use a different face for mouseover 
> > s?he needs to duplicate EACH of the
> 
> Actually, you should be able to do it cleanly using face-remapping.

Users should be able to do it by _customizing_ the particular face used for
mouseover in the particular context.  Why complicate things unnecessarily?  One
might be able to use face remapping here and there all over the place to
simulate face customization, but why?

If you think two particular contexts are similar a priori, then define their
mouseover faces to inherit the same way - same default appearance.  But at least
let the user customize them to look different if that's what s?he wants.




  reply	other threads:[~2011-02-15 22:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 19:26 can we please define a face for compile.el mouseover? Drew Adams
2011-02-15 19:42 ` Eli Zaretskii
2011-02-15 22:43   ` Drew Adams
2011-02-15 21:12 ` Stefan Monnier
2011-02-15 22:41   ` Drew Adams [this message]
2011-02-16  2:32     ` Stefan Monnier
2011-02-16  4:03       ` Drew Adams
2011-02-19 21:11         ` Stefan Monnier
2011-02-19 21:32           ` Chong Yidong

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=F214997A3A5646FEA54A0723D1504E21@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).