From: Eric J Haywiser <ejh1@MIT.EDU>
To: emacs-orgmode@gnu.org
Subject: Bug? deadlines, links & faces (was cosmetic: link-syntax...)
Date: Wed, 10 May 2006 10:08:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.62L.0605100946160.19076@no-knife.mit.edu> (raw)
In-Reply-To: <Pine.GSO.4.62L.0605080830270.13447@mass-toolpike.mit.edu>
Related to my earlier post, the assymetric behavior described below seems
like a clear bug in rendering deadlines in org-agenda view:
> links in org-agenda view entries coming from org files
> hide the URL portion and only display the "description" portion of the link.
This is not true for upcoming and expired org-deadline-warning of deadline
entries containing links. Both display raw link text. However, the same
entry displays only the description portion of the link when it is
rendered on the day of the deadline.
Example follows:
-------------------------------------------------------------------------
* Visit [[http://www.google.com][Google]]
DEADLINE: <2006-05-10 Wed>
DEADLINE: <2006-05-11 Thu>
-------------------------------------------------------------------------
Which appears as:
Wednesday 10 May 2006
8:00...... ----------------
10:00...... ----------------
12:00...... ----------------
14:00...... ----------------
14:00...... ----------------
16:00...... ----------------
18:00...... ----------------
19:00...... ----------------
20:00...... ----------------
testing: Deadline: Visit Google
testing: In 1 d.: Visit [[http://www.google.com][Google]]
-------------------------------------------------------------------------
next prev parent reply other threads:[~2006-05-10 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 13:09 cosmetic: link-syntax, diary files & faces Eric J Haywiser
2006-05-10 14:08 ` Eric J Haywiser [this message]
2006-05-11 8:38 ` Carsten Dominik
2006-05-12 13:36 ` Eric J Haywiser
2006-05-12 14:08 ` Carsten Dominik
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=Pine.GSO.4.62L.0605100946160.19076@no-knife.mit.edu \
--to=ejh1@mit.edu \
--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).