emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Schedule event
Date: Sun, 07 Aug 2011 08:14:06 +0200	[thread overview]
Message-ID: <80y5z5g34h.fsf@somewhere.org> (raw)
In-Reply-To: 87ei0y8gu0.fsf@riotblast.dunsmor.com

Hi Jason,

Jason Dunsmore wrote:
> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>> suvayu ali wrote:
>>> Yes, this would be a nice addition. I always find it difficult to decide
>>> how to put regular timestamps too.
>>
>> By regular timestamps, you mean: inactive timestamps?
>
> I think he means active timestamps with no keyword. The Org FAQ and manual
> refer to active timestamps with no keyword as "plain timestamps".
>
>> Can you, maybe, comment on what makes the decision difficult?
>
> At least for me, in my early Org days, I wasn't sure of the best formatting
> convention for "plain timestamps". I settled on putting them on the line
> directly after the header with the proper indentation, since this is how
> SCHEDULED items were inserted.

OK. I thought the difficult decision was about the type of timestamps:
SCHEDULED, not SCHEDULED but active, or inactive.

Now, I understand he meant about the positioning of the timestamp itself.
Thanks for clarifying this.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2011-08-07  6:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 17:05 Schedule event Jason Dunsmore
2011-08-06  6:19 ` Carsten Dominik
2011-08-06 15:00   ` Sebastien Vauban
2011-08-06 18:15     ` suvayu ali
2011-08-06 18:59       ` Sebastien Vauban
2011-08-06 19:42         ` suvayu ali
2011-08-07  6:12           ` Sebastien Vauban
2011-08-06 19:45         ` Jason Dunsmore
2011-08-07  6:14           ` Sebastien Vauban [this message]
2011-08-06 19:38     ` Jason Dunsmore
2011-08-07 22:06   ` Jason Dunsmore
2011-08-24 10:26     ` Bastien
2011-08-26 12:08       ` Greg Troxel

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=80y5z5g34h.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).