From mboxrd@z Thu Jan 1 00:00:00 1970 From: York Zhao Subject: Re: "org-time-stamp" and "org-time-stamp-inactive" no longer work Date: Tue, 13 Dec 2011 14:38:03 -0500 Message-ID: References: <8739ctwmnj.fsf@gnu.org> <87ehwbjtrb.wl%dmaus@ictsoc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:45034) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RaYAw-0002Hy-BP for emacs-orgmode@gnu.org; Tue, 13 Dec 2011 14:38:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RaYAu-0002Sb-Q3 for emacs-orgmode@gnu.org; Tue, 13 Dec 2011 14:38:06 -0500 Received: from mail-vx0-f169.google.com ([209.85.220.169]:43499) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RaYAu-0002SW-NV for emacs-orgmode@gnu.org; Tue, 13 Dec 2011 14:38:04 -0500 Received: by vcbfk26 with SMTP id fk26so16572vcb.0 for ; Tue, 13 Dec 2011 11:38:03 -0800 (PST) In-Reply-To: <87ehwbjtrb.wl%dmaus@ictsoc.de> 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@gnu.org > > Matt reported a similar problem in > > > > But it seems the problem just ... fixed itself: > > ,---- > | However, oddly, after experiencing the same issue about 6 times in a > | row, the problem mysteriously disappeared just now, and the procedure > | is working fine. =A0I have no idea what the issue is there -- I'll > | report when I find it again. =A0Maybe someone on the list can give me > | suggestions for debugging if it shows up again? > `---- Thanks for the help David and Nick, I would say that my problem looks extre= mely similar (if not exactly the same) like Matt had reported. > =A01. Try to reproduce the bug with a minimal setup, just Emacs + > =A0 =A0 uncompiled Org mode; I will try this at some point. > =A02. If this is possible, see if it occurrs if the calendar buffer is > =A0 =A0already open (e.g. M-x calendar RET) -- maybe this is some kind of > =A0 =A0a weird race condition (?). I'm sure there was no calendar buffer pre-existing. The wield thing is that whenever this problem happens, the contents of my other buffer would be rep= laced with the calendar while the name of the buffer kept unchanged. Thanks, York