unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: Re: Underlining in compile.el
Date: Tue, 28 Jun 2005 09:26:39 +1200	[thread overview]
Message-ID: <17088.28432.470.506291@farnswood.snap.net.nz> (raw)
In-Reply-To: <E1DmmJg-0004JF-7p@fencepost.gnu.org>

 > However, ISTR that this complaint was made when there were bugs
 > causing too much of the line to be highlighted.  If fixing those bugs
 > was enough to solve the problem, we don't need to do any more.  Would
 > those that found the situation confusing before please speak up now?

My preference was for just using mouse-1  where text is generally underlined
already e.g info, help, customize (not underlined) etc.

I think you/others said it should apply to all buffers.

My next preference would be to restrict the area where mouse-1 worked e.g in
grep just on file and line number while mouse-2 could still work over the
whole line.  I would not know how to do this, but I am prepared to work on it
after the release.

I stopped following the thread, but I don't like the idea of adding underlining
as links already have mouse-face and a hand pointer.  What next, a little
jingle that plays when the mouse is over the link?

Nick

  parent reply	other threads:[~2005-06-27 21:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-25 16:40 Underlining in compile.el Richard M. Stallman
2005-06-26 21:54 ` Kim F. Storm
2005-06-27  5:37   ` Richard M. Stallman
2005-06-27 15:44     ` Drew Adams
2005-06-28  4:17       ` Richard M. Stallman
2005-06-27 21:26     ` Nick Roberts [this message]
2005-06-28 18:48       ` Richard M. Stallman
2005-06-29  1:42         ` Nick Roberts
2005-06-29  3:33           ` Juri Linkov
2005-06-29  4:15             ` Nick Roberts
2005-06-29  9:33             ` Nick Roberts
2005-06-29 23:55               ` Juri Linkov
2005-08-06 18:43 ` Juri Linkov
2005-08-09  0:27   ` Richard M. Stallman

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=17088.28432.470.506291@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=emacs-devel@gnu.org \
    --cc=storm@cua.dk \
    /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).