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: Thu, 22 Dec 2011 11:29:57 -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]:58621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdlWz-00020g-KX for emacs-orgmode@gnu.org; Thu, 22 Dec 2011 11:30:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RdlWq-0004C2-I2 for emacs-orgmode@gnu.org; Thu, 22 Dec 2011 11:30:09 -0500 Received: from mail-vw0-f41.google.com ([209.85.212.41]:33298) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RdlWq-0004Bt-Dy for emacs-orgmode@gnu.org; Thu, 22 Dec 2011 11:30:00 -0500 Received: by vbbfn1 with SMTP id fn1so8042246vbb.0 for ; Thu, 22 Dec 2011 08:29:59 -0800 (PST) In-Reply-To: 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 ext= remely > 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 o= f >> =A0 =A0a weird race condition (?). > > I'm sure there was no calendar buffer pre-existing. The wield thing is th= at > whenever this problem happens, the contents of my other buffer would be r= eplaced > with the calendar while the name of the buffer kept unchanged. > To keep this list updated, I just upgraded to the latest Emacs from git, compiled and linked using mingw and this problem no longer exists. Thank yo= u all for your help and merry Christmas. York