From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Timestamp practices? Date: Wed, 20 Mar 2013 15:39:45 +0100 Message-ID: <877gl2879q.fsf@bzg.ath.cx> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38727) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIKBF-0007Lt-7S for emacs-orgmode@gnu.org; Wed, 20 Mar 2013 10:39:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UIKBA-000336-8p for emacs-orgmode@gnu.org; Wed, 20 Mar 2013 10:39:53 -0400 Received: from mail-wi0-x235.google.com ([2a00:1450:400c:c05::235]:63717) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIKBA-00032v-2I for emacs-orgmode@gnu.org; Wed, 20 Mar 2013 10:39:48 -0400 Received: by mail-wi0-f181.google.com with SMTP id hm6so1904723wib.8 for ; Wed, 20 Mar 2013 07:39:47 -0700 (PDT) In-Reply-To: (Lawrence Bottorff's message of "Wed, 20 Mar 2013 09:30:06 -0500") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Lawrence Bottorff Cc: emacs-orgmode@gnu.org Hi Lawrence, Lawrence Bottorff writes: > I'd like to know the best practice for adding such timestamps. Am I > gaining anything by enclosing the timestamp in such an elaborate > drawer? It really depends on what you want to achieve, but I'd say no, in general. > Are these two commands the best way to do this? Or is there a > more automated approach? I would simply use a bare time-stamp like this * Headline <2013-03-20 mer.> Use C-c . to insert the active time-stamp, or C-c ! to insert an inactive one, or use shift-up/down on the brackets to switch from active to inactive. > In general, I can't help but marvel at the ad-hoc, on-the-fly data > management possibilities org-mode offers. It seems like the sky's the > limit. But I'd like opinions on whether I'm stumbling along a blind > alley. In any case, using a time-stamp in CUSTOM_ID does not seem to be a good idea, as this id will be used as an anchor in various contexts (link search, HTML, etc.) So better use a bare time-stamp I'd say. HTH, -- Bastien