From: SW <sabrewolfy@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Yearly repeats on the agenda
Date: Tue, 17 Apr 2012 07:21:14 +0000 (UTC) [thread overview]
Message-ID: <loom.20120417T091907-419@post.gmane.org> (raw)
In-Reply-To: loom.20120417T091154-174@post.gmane.org
SW <sabrewolfy <at> gmail.com> writes:
> Apologies -- the above was a copy and paste nightmare between Emacs and
> Firemacs. What I meant was the following in an org file:
>
> *** <2011-01-01 +1y> New Year's Day :holiday:
>
> and the following appearing on the agenda:
>
> File: <2011-01-01 +1y> New Year's Day :holiday:
>
> What I'm asking about is the fact that the full timestamp itself appears in <>
> in the agenda for this entry, but not for other deadline/schedule/plain
> timestamp entries.
>
And I'd like to disable the timestamp in <> for these entries. They appear ON
the correct day in the agenda, so there is no need to include the full
timestamp. Also, this makes the entry very long in the Agenda. Other entries
(timestamps/deadlines/schedules) appear in the agenda without the timestamp text
in <>.
next prev parent reply other threads:[~2012-04-17 7:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 20:40 Yearly repeats on the agenda SW
2012-04-16 23:24 ` Nick Dokos
2012-04-17 0:52 ` Samuel Wales
2012-04-17 7:16 ` SW
2012-04-17 7:21 ` SW [this message]
2012-04-17 7:39 ` Brian van den Broek
2012-04-17 7:44 ` Brian van den Broek
2012-04-17 12:46 ` SW
2012-04-17 13:11 ` SW
2012-04-17 14:00 ` Brian van den Broek
2012-04-17 14:28 ` Nick Dokos
2012-04-17 10:28 ` SW
2012-04-17 10:39 ` SW
2012-04-17 12:22 ` Nick Dokos
2012-04-17 12:40 ` SW
2012-04-17 13:10 ` Nick Dokos
2012-04-20 12:46 ` Bastien
2012-04-20 12:57 ` SW
2012-04-20 13:17 ` Nick Dokos
2012-04-20 23:52 ` Samuel Wales
2012-05-08 14:10 ` Bastien
2012-05-08 16:50 ` Nicolas Richard
2012-05-10 6:38 ` Bastien
2012-05-10 8:57 ` Nicolas Richard
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=loom.20120417T091907-419@post.gmane.org \
--to=sabrewolfy@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).