From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian van den Broek Subject: Change example timestamps to not occur in headlines Date: Fri, 20 Apr 2012 18:16:28 +0200 Message-ID: <4F918BDC.50106@gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------050906000000030005010701" Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44241) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLGWE-0003uZ-Kj for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 12:17:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SLGVx-0007yT-Rj for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 12:17:10 -0400 Received: from mail-bk0-f41.google.com ([209.85.214.41]:50350) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLGVx-0007xe-C4 for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 12:16:53 -0400 Received: by bkwq16 with SMTP id q16so9204769bkw.0 for ; Fri, 20 Apr 2012 09:16:51 -0700 (PDT) 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: emacs-orgmode This is a multi-part message in MIME format. --------------050906000000030005010701 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi all, [I wondered why my first post wasn't labelled a patch, and then I saw that it attached as octet-stream. Investigating, I was surprised to see that gmail's web interface cannot handle patches as attachments. Sorry for the dupe, but I thought it best to send again in a way that patchwork can detect.] I've attached a small patch to the documentation that resolves a conflict between the manual's advice not to include timestamps in headlines and some of its examples where it does just that. This is the first time I've ever submitted a formal patch using git to any project, so I hope I did things the right way. Sadly, I am not presently in a position to sign assignment papers, but this is a TINYCHANGE. Best, Brian vdB --------------050906000000030005010701 Content-Type: text/x-diff; name="0001-Change-example-timestamps-to-not-occur-in-headlines.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename*0="0001-Change-example-timestamps-to-not-occur-in-headlines.pat"; filename*1="ch" >From 5ccad7cf377a19c8a8b89aba1e12c17fa96a1cb0 Mon Sep 17 00:00:00 2001 From: Brian van den Broek Date: Fri, 20 Apr 2012 17:43:18 +0200 Subject: [PATCH] Change example timestamps to not occur in headlines * doc/doc/org.texi Alter several examples of headings with timestamps in them to include the timestamps in the body instead of the heading. * b/doc/org.texi Alter the same examples in the same way as for org.texi. The Org-mode manual explicitly discourages the inclusion of timestamps in headlines, yet examples do just that. These changes make the manual consistent with its own advice. TINYCHANGE --- doc/org.texi | 12 ++++++++---- doc/orgguide.texi | 12 ++++++++---- 2 files changed, 16 insertions(+), 8 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index a981f68..412a241 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -5393,8 +5393,10 @@ timeline and agenda displays, the headline of an entry associated with a plain timestamp will be shown exactly on that date. @example -* Meet Peter at the movies <2006-11-01 Wed 19:15> -* Discussion on climate change <2006-11-02 Thu 20:00-22:00> +* Meet Peter at the movies + <2006-11-01 Wed 19:15> +* Discussion on climate change + <2006-11-02 Thu 20:00-22:00> @end example @item Timestamp with repeater interval @@ -5405,7 +5407,8 @@ interval of N days (d), weeks (w), months (m), or years (y). The following will show up in the agenda every Wednesday: @example -* Pick up Sam at school <2007-05-16 Wed 12:30 +1w> +* Pick up Sam at school + <2007-05-16 Wed 12:30 +1w> @end example @item Diary-style sexp entries @@ -5449,7 +5452,8 @@ angular ones. These timestamps are inactive in the sense that they do @emph{not} trigger an entry to show up in the agenda. @example -* Gillian comes late for the fifth time [2006-11-01 Wed] +* Gillian comes late for the fifth time + [2006-11-01 Wed] @end example @end table diff --git a/doc/orgguide.texi b/doc/orgguide.texi index f92e97b..a23a532 100644 --- a/doc/orgguide.texi +++ b/doc/orgguide.texi @@ -1325,8 +1325,10 @@ A simple timestamp just assigns a date/time to an item. This is just like writing down an appointment or event in a paper agenda. @smallexample -* Meet Peter at the movies <2006-11-01 Wed 19:15> -* Discussion on climate change <2006-11-02 Thu 20:00-22:00> +* Meet Peter at the movies + <2006-11-01 Wed 19:15> +* Discussion on climate change + <2006-11-02 Thu 20:00-22:00> @end smallexample @noindent @b{Timestamp with repeater interval}@* @@ -1335,7 +1337,8 @@ applies not only on the given date, but again and again after a certain interval of N days (d), weeks (w), months (m), or years (y). The following will show up in the agenda every Wednesday: @smallexample -* Pick up Sam at school <2007-05-16 Wed 12:30 +1w> +* Pick up Sam at school + <2007-05-16 Wed 12:30 +1w> @end smallexample @noindent @b{Diary-style sexp entries}@* @@ -1360,7 +1363,8 @@ angular ones. These timestamps are inactive in the sense that they do @emph{not} trigger an entry to show up in the agenda. @smallexample -* Gillian comes late for the fifth time [2006-11-01 Wed] +* Gillian comes late for the fifth time + [2006-11-01 Wed] @end smallexample -- 1.7.9 --------------050906000000030005010701--