unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: Emacs-Devel <emacs-devel@gnu.org>
Subject: RE: hyperlinks in variable's value - links to libraries
Date: Fri, 6 Jan 2006 17:47:16 +1300	[thread overview]
Message-ID: <17341.63060.125701.419230@kahikatea.snap.net.nz> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICIECNDBAA.drew.adams@oracle.com>

 > Resending. Shall I assume no one is interested?
 > 
 >       ;; Hyperlinks in variable's value are quite frequently
 >       ;; inappropriate e.g C-h v <RET> features <RET>
 >       ;; (help-xref-on-pp from (point))
 >        
 >     I disagree with the "fix" of commenting out this 
 >     line - at the least, I would like such links to be an option.

I commented it out, rather than remove it, in case someone came up with a
better solution, not for someone to lobby to revert it.  I don't think it was
in response to a report you made and `features' was just an example, although
I can't remember the others.

Many variables like mode-line-format or after-load-list have a lot of
underlining, some of which isn't that helpful (a user is hardly likely to want
click on concat or user-init-file) and it makes it harder to see what you're
looking at.

I think its best not to lead users anywhere than up the garden path.  The doc
strings on the other hand can be more carefully crafted to DTRT.

 >     Although it can be slow, it is very useful: looking at `features'
 >     should be an entry point to accessing the features listed.    

The links are still available on mouse-2 as help-follow, they're just not
underlined or highlighted.  Having a help-echo saying "mouse-2, RET: describe
this function" while over a feature is not helpful IMO, a hinder-echo you
could say.

Nick

  parent reply	other threads:[~2006-01-06  4:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-01 21:19 hyperlinks in variable's value - links to libraries Drew Adams
2006-01-06  3:23 ` Drew Adams
2006-01-06  4:44   ` Stefan Monnier
2006-01-06  9:14     ` Lennart Borgman
2006-01-06 17:10     ` Drew Adams
2006-01-09  1:35       ` Stefan Monnier
2006-01-06  4:47   ` Nick Roberts [this message]
2006-01-06 17:10     ` Drew Adams
2006-01-06 22:35       ` Nick Roberts
2006-01-07  1:01         ` Drew Adams
2006-01-07  2:14           ` Nick Roberts
2006-01-07 15:38             ` Drew Adams

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=17341.63060.125701.419230@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=emacs-devel@gnu.org \
    /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).