From: Juri Linkov <juri@jurta.org>
Cc: teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Problems with whole buffer Custom functions.
Date: Tue, 24 Jan 2006 23:45:47 +0200 [thread overview]
Message-ID: <87ek2x48tg.fsf@jurta.org> (raw)
In-Reply-To: <E1F1RJb-0000ZP-LO@fencepost.gnu.org> (Richard M. Stallman's message of "Tue, 24 Jan 2006 11:46:43 -0500")
> OTOH, links are underlined blue and don't need
> additional markup like square brackets.
>
> Not on a tty they aren't. There is no underlining.
>
> So I propose not to display links
> in square brackets even on a tty and to update the manual:
>
> No, please don't install that.
I don't insist on removing square brackets. I only wanted to make the
appearance of buttons and links consistent at least on same display types.
Currently there is the following inconsistency on the link appearance:
on graphics terminals:
links in Customize - underlined blue
links in Info - underlined blue
links in Help - underlined
on xterms:
links in Customize - underlined blue with square brackets
links in Info - underlined blue
links in Help - underlined
on ttys:
links in Customize - blue with square brackets
links in Info - blue
links in Help - no highlighting at all
I propose to change them according to the following scheme (I'm still not
quite sure about adding blue to links in the Help buffer):
On graphics terminals:
links in Customize - underlined blue
links in Info - underlined blue
links in Help - underlined (blue?)
On xterms:
links in Customize - underlined blue
links in Info - underlined blue
links in Help - underlined (blue?)
On ttys:
links in Customize - blue
links in Info - blue
links in Help - blue
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2006-01-24 21:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 3:32 Problems with whole buffer Custom functions Luc Teirlinck
2006-01-17 1:27 ` Juri Linkov
2006-01-17 4:13 ` Luc Teirlinck
2006-01-17 21:54 ` Juri Linkov
2006-01-18 0:29 ` Kevin Rodgers
2006-01-23 0:10 ` Richard M. Stallman
2006-01-22 0:45 ` Juri Linkov
2006-01-22 1:46 ` Luc Teirlinck
2006-01-23 1:42 ` Juri Linkov
2006-01-24 16:46 ` Richard M. Stallman
2006-01-24 21:45 ` Juri Linkov [this message]
2006-01-24 23:11 ` Lennart Borgman
2006-01-25 7:55 ` Juri Linkov
2006-01-25 15:45 ` Richard M. Stallman
2006-01-22 1:55 ` Luc Teirlinck
2006-01-23 1:43 ` Juri Linkov
2006-01-22 0:45 ` Juri Linkov
2006-01-22 17:44 ` Richard M. Stallman
2006-01-19 17:44 ` Richard M. Stallman
2006-01-22 0:45 ` Juri Linkov
2006-01-22 17:44 ` Richard M. Stallman
2006-01-22 21:28 ` Drew Adams
2006-01-23 1:47 ` Juri Linkov
2006-01-23 2:58 ` Drew Adams
2006-01-23 6:17 ` Juri Linkov
2006-01-24 16:47 ` Richard M. Stallman
2006-01-23 1:47 ` Juri Linkov
2006-01-24 16:46 ` Richard M. Stallman
2006-01-23 18:04 ` martin rudalics
2006-01-25 3:28 ` Richard M. Stallman
2006-01-22 17:44 ` Richard M. Stallman
-- strict thread matches above, loose matches on Subject: below --
2006-01-25 8:58 LENNART BORGMAN
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ek2x48tg.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.