From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Problem inserting date Date: Mon, 12 Nov 2012 18:55:42 -0500 Message-ID: <8573.1352764542@alphaville.americas.hpqcorp.net> References: <50A13DCE.10909@gmail.com> <50A1860D.8010903@gmail.com> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38472) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TY3r7-0000oJ-Oq for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 18:55:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TY3r4-0004HY-Mh for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 18:55:53 -0500 Received: from g5t0007.atlanta.hp.com ([15.192.0.44]:35066) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TY3r4-0004Fz-Gc for emacs-orgmode@gnu.org; Mon, 12 Nov 2012 18:55:50 -0500 In-Reply-To: Message from Sean Lynch of "Mon, 12 Nov 2012 18:28:13 EST." <50A1860D.8010903@gmail.com> 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: Sean Lynch Cc: Jude DaShiell , emacs-orgmode@gnu.org Sean Lynch wrote: > > > On 11/12/2012 06:13 PM, Jude DaShiell wrote: > > On Mon, 12 Nov 2012, Sean Lynch wrote: > > > >> I start with the following orgmode file called org-test.org: > >> > >> ---beginning of org-test.org ------- > >> > >> * test > >> ** TODO test add date > >> ** testing > >> > >> ---end of org-test.org ------------ > >> > >> I put the cursor at the end of the first subheading under "test" and hit > >> C-c C-d to insert a date. > >> C-c C-d is bound to org-deadline by default. Do C-h c C-c C-d and make sure that this is true in your case as well. > >> The entire file is replaced with the calendar (instead of this coming up > >> in a new buffer). > >> > >> ---beginning of org-test.org ------- > >> October 2012 November 2012 December 2012 > >> Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa Su Mo Tu We Th Fr Sa > >> 1 2 3 4 5 6 1 2 3 1 > >> 7 8 9 10 11 12 13 4 5 6 7 8 9 10 2 3 4 5 6 7 8 > >> 14 15 16 17 18 19 20 11 12 13 14 15 16 17 9 10 11 12 13 14 15 > >> 21 22 23 24 25 26 27 18 19 20 21 22 23 24 16 17 18 19 20 21 22 > >> 28 29 30 31 25 26 27 28 29 30 23 24 25 26 27 28 29 > >> 30 31 > >> ---end of org-test.org ------------ > >> I cannot reproduce this with Org-mode version 7.9.2 (release_7.9.2-577-gb0a051 @ /home/nick/elisp/org-mode/lisp/) and it sounds as if something is really broken in your setup (e.g. C-c C-d is bound to something strange). > >> The mini buffer gives me the standard prompt to choose the date but when > >> I do, the original file doesn't come back and is still replaced with the > >> calendar. > >> The following message is produced: > >> byte-code: Before first headline at position 1 in buffer org-test.org. > >> You should be able to get a backtrace then by doing M-x toggle-debug-on-error and retrying the problematic command. Nick > >> I read a post that seemed to suggest that this is related to org-goto > >> and the value of org-goto-interface but changing that value doesn't help. > >> > >> Emacs : GNU Emacs 24.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10) > >> of 2012-11-05 on litembilla, modified by Debian > >> Package: Org-mode version 7.9.2 (release_7.9.2-581-gaaf179 @ > >> /home/slynch/.emacs.d/el-get/org-mode/lisp/) > >> > >> > > > > --------------------------------------------------------------------------- > > jude > > Adobe fiend for failing to Flash > > > > Do it again, and notice today is highlighted. Hit enter or click the > > mouse and the highlighted date should appear in your file and the calendar > > will disappear. > > > > No. As I mentioned, the original file doesn't come back. It is replaced > by the calendar and after I choose the date the calendar stays there, > replacing the contents of the original file... And the error message is > produced. > > Also, even if the original file did come back after choosing the date, > this is not the correct behaviour. The calendar should open in a new buffer. >