From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matt Lundin <mdl@imapmail.org>
Subject: Re: [PATCH] Close calendar buffer after scheduling an item
Date: Fri, 05 Feb 2010 23:11:02 -0500
Message-ID: <87vdebknqh.fsf@fastmail.fm>
References: <5e3a506e1002051924jce1863fgbf70ee64e05df0ff@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Ndby5-0007Wk-4t
	for emacs-orgmode@gnu.org; Fri, 05 Feb 2010 23:08:25 -0500
Received: from [199.232.76.173] (port=57593 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Ndby4-0007Wc-OF
	for emacs-orgmode@gnu.org; Fri, 05 Feb 2010 23:08:24 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <lundin@fastmail.fm>) id 1Ndby3-0000jS-5w
	for emacs-orgmode@gnu.org; Fri, 05 Feb 2010 23:08:24 -0500
Received: from out2.smtp.messagingengine.com ([66.111.4.26]:49390)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <lundin@fastmail.fm>) id 1Ndby2-0000iw-Rv
	for emacs-orgmode@gnu.org; Fri, 05 Feb 2010 23:08:22 -0500
In-Reply-To: <5e3a506e1002051924jce1863fgbf70ee64e05df0ff@mail.gmail.com>
	(Nathaniel Flath's message of "Fri, 5 Feb 2010 22:24:23 -0500")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Nathaniel Flath <flat0103@gmail.com>
Cc: emacs-orgmode@gnu.org

Nathaniel Flath <flat0103@gmail.com> writes:

> If you schedule an item with org-schedule, the *Calendar* buffer will
> stay around.=C2=A0 This also occurs with org-deadline, and any other
> functions that use org-read-date.=C2=A0 The patch attached just closes th=
is
> buffer once the date is read.

Might I ask why it is necessary to kill the *Calendar* buffer? AFAICT,
the default behavior of M-x calendar is to keep the *Calendar* buffer
alive even after "quitting" the calendar view with "q".

With this patch, if one creates a *Calendar* buffer with M-x calendar,
org-mode will subsequently kill it. I would prefer that the behavior of
org-mode remain consistent with that of emacs calendar.=20

Best,
Matt