From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: link appearance and soft face properties
Date: Sun, 19 Jun 2005 10:47:58 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICOEHGCJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1DjSxG-0003Ul-9P@fencepost.gnu.org>
What about having a :link face attribute (property) that is
soft, not hard?
What does "soft" or "hard" mean, here?
Soft: The appearance of a soft text property like :link would be whatever a
user says it is. By default, it might be a set of properties with just one
member: the :underline property.
Hard: The appearance of a hard text property like :underline always means
the same thing: the text is underlined. Users can decide to use it or not
use it, but they cannot redefine it.
That way, a single (possibly user) definition of the :link
attribute would automatically affect any faces that have
that property. And it would also be easy (including for
users) to selectively apply the :link property to face
or mouse-face or both.
I think this can be done by making these faces inherit
from a face named `link'.
I thought that might be the case. Instead of "soft" text properties (which
would be definable as a set of soft and hard text properties), an inheriting
face could be used. IOW, a face is already a set of text properties (you can
say "has" if you don't like "is"), and we already have face inheritance.
A potential difference I see is that the thing that inherits is a face,
rather than a text property. In the present case, we would define (and use
for all links) a `link' face that inherits certain properties (e.g.
:underline) by default. I'm not sure that would be equivalent in flexibility
to defining an inheriting (= "soft") text property :link, but perhaps it
would be.
If we can do this (predefine links in a soft way) using face inheritance,
then why don't we (after the release), in order to give people more
flexibility?
next prev parent reply other threads:[~2005-06-19 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 14:42 mouse-1-click-follows-link LENNART BORGMAN
2005-06-17 15:32 ` link appearance and soft face properties Drew Adams
2005-06-18 2:21 ` Richard Stallman
2005-06-18 13:47 ` Juri Linkov
2005-06-19 3:51 ` Richard Stallman
2005-06-19 17:50 ` Drew Adams
2005-06-20 4:55 ` Juri Linkov
2005-06-20 16:53 ` Drew Adams
2005-06-19 17:47 ` Drew Adams [this message]
2005-06-19 20:06 ` Robert J. Chassell
2005-06-19 22:01 ` Drew Adams
2005-06-20 0:57 ` Robert J. Chassell
2005-06-20 16:53 ` Drew Adams
2005-06-20 1:45 ` Daniel Brockman
2005-06-20 17:51 ` Richard Stallman
2005-06-17 15:36 ` mouse-1-click-follows-link Stefan Monnier
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=DNEMKBNJBGPAOPIJOOICOEHGCJAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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).