unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ami Fischman <usenet@fischman.org>
Cc: emacs-devel@gnu.org
Subject: Re: specific coloring of diary calendar entries
Date: Mon, 16 Dec 2002 22:18:50 -0800	[thread overview]
Message-ID: <m3n0n5cgmt.fsf@fischman.org> (raw)
In-Reply-To: <E18NiLq-0006fa-00@fencepost.gnu.org> (Richard Stallman's message of "Sun, 15 Dec 2002 18:39:14 -0500")

I misread your previous post on this subject.  Specifically, I thought you
were asking for the tags to allow different attributes from color (so
there'd be [bgcolor:blah], [underline:blah], [bold:blah], etc tags).  Doing
that much work would just be silly, as someone who knows enough to define
the attributes of an emacs face can just create the face and use an sexp.

Upon re-reading your suggestion, I think what you are saying is you want the
ability to say [work] or [home] and have `work' and `home' be "categories"
-- presumably a conglomerate of face attributes that apply to the entry.
But how is this simpler than defining a "work" or "home" face and having an
sexp entry invoke it?

I guess I'm looking at two situations: the emacs expert and the emacs
novice.  The former knows how to create a face and attach it to an entry
even without my patches (using sexp's); the latter will now be able to
define f/g colors for his/her diary entries.  Is the difference between
defining/using "semantic categories" and defining/using emacs faces+sexp
entries really as large as the gap between expert and novice?  I think the
answer is no.  If you disagree, please let me know.

I'm not morally opposed to adding features to these patches.  I just don't
think there is an elegant way to add them to the code (the color patches are
already somewhat "glued on") and so would rather not do so unless there's a
demonstrated need or demand for them.  If others would like to see some form
of semantic categorization (going beyond f/g color, which can be achieved
with file-glob-color), please speak up :)

Cheers,
-- 
  Ami Fischman
  usenet@fischman.org

  parent reply	other threads:[~2002-12-17  6:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 23:58 specific coloring of diary calendar entries Ami Fischman
2002-12-12  1:02 ` Alan Shutko
2002-12-12 18:24   ` Ami Fischman
2002-12-12 18:56     ` Ami Fischman
2002-12-12 19:31     ` Alan Shutko
2002-12-13 10:14       ` Kai Großjohann
2002-12-14  1:05     ` Alan Shutko
2002-12-14  1:42       ` Miles Bader
2002-12-13 22:22 ` Richard Stallman
2002-12-13 23:37   ` Ami Fischman
2002-12-14  0:07     ` Alan Shutko
2002-12-15 23:39     ` Richard Stallman
2002-12-16  0:31       ` Alex Schroeder
2002-12-17 18:44         ` Richard Stallman
2002-12-17  6:18       ` Ami Fischman [this message]
2002-12-17  9:42         ` Alex Schroeder
2002-12-17 16:03           ` Alan Shutko
2002-12-17 11:05         ` Kai Großjohann
2002-12-17 16:02           ` Alan Shutko
2002-12-17 11:07         ` Kai Großjohann
2002-12-18  2:01         ` Richard Stallman
2002-12-18 22:27           ` Ami Fischman
2002-12-19  6:02             ` Ami Fischman
2002-12-19 18:03               ` Ami Fischman

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=m3n0n5cgmt.fsf@fischman.org \
    --to=usenet@fischman.org \
    --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).