From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Extended-period events in agenda views
Date: Tue, 2 Nov 2010 08:53:19 +0100 [thread overview]
Message-ID: <6609317F-3A73-4C43-8F30-13B9019ED23E@fastmail.net> (raw)
In-Reply-To: <BA9DEC26-8E9A-4D1D-AC03-EC6CB260B11A@gmail.com>
Hi Carsten,
On 1 Nov 2010, at 20:55, Carsten Dominik wrote:
> I don't think so. But what I am also missing is a clear idea on
> *how* this event should be generated and *how* it should be
> displayed. Apparently you do not want the event listed in the
> agenda, but you say "maybe a special font". If the event is not
> listed, what else should be in a general font?
I can think of several ways to do this:
1) a small marker (such as a star) in front of every day in the
specific period, with a link to the event that caused it. I'd see at a
glance that the days is special and if I need to know the details,
they are just a click away. Problem: if several periods cover the
same day, what does the link point to? There could be one star per
special event, as long as their number remains reasonable.
2) Another visual marker for the days concerned, such as a special
typeface (difficult, since bold and italic are already taken), or a
different color. Problem: how to get at more detailed information? It
could be shown in the minibuffer when the cursor is at that day, for
example.
As for generating the event, a list of day ranges would be just fine.
They could have some property attached to them to distinguish them
from ordinary events.
Konrad.
next prev parent reply other threads:[~2010-11-02 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 11:32 Extended-period events in agenda views Konrad Hinsen
2010-11-01 19:55 ` Carsten Dominik
2010-11-02 7:53 ` Konrad Hinsen [this message]
2010-11-01 20:41 ` Chris Thompson
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6609317F-3A73-4C43-8F30-13B9019ED23E@fastmail.net \
--to=konrad.hinsen@fastmail.net \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).