From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xin Shi Subject: Re: Release 5.23a Date: Mon, 10 Mar 2008 22:05:51 -0400 Message-ID: <47D5E8FF.4090708@cornell.edu> References: <876ACC10-F511-4735-B045-9C9AE248A25A@gmail.com> <47D5CC47.40107@cornell.edu> <87ve3urtzq.fsf@bzg.ath.cx> <47D5D90E.8010508@cornell.edu> <87myp683ix.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JYtsN-0005RI-Td for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:05:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JYtsJ-0005Qd-DK for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:05:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JYtsJ-0005Qa-7w for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:05:55 -0400 Received: from granite2.mail.cornell.edu ([128.253.83.142] helo=authusersmtp.mail.cornell.edu) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JYtsI-0005Al-Oq for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:05:54 -0400 In-Reply-To: <87myp683ix.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Bastien Guerry Cc: emacs-orgmode@gnu.org Bastien Guerry wrote: > Xin Shi writes: > > >> Is that possible to make it kill the buffer on the C-c C-e h case? Or >> let user to customize this behavior? I don't know the reason to keep >> that buffer in this case. >> > > I don't know what the default should be, I have no personal preference. > I think it's quite useful to have the exported file accessible through > the list of buffers even if you don't want to jump to it. > > If there are programs still need to access that buffer, I agree to keep it in the buffer list. Otherwise, I don't think people want to EDIT that html file inside Emacs by hand :) > But I certainly wouldn't go for an option about this. > > What people think? > > I'm using firefox to view the output. If there are people still using the Emacs to view the output .html file, let's just keep it there. >>> Note two differences with "publishing": (1) publishing require a file to >>> be part of a project and (2) publishing will kill exported buffers. >>> >>> >> I'm not sure where are these two differences comes from? Are they >> behaviors in org or in general? >> > > I'm not sure what do you mean by "in general". In case of publishing, > since you can publish a project from *any* buffer, it doesn't really > make sense to keep the exported buffers alive, right? As for the (1), > the truth is that it would be nice to be able to add a file to a project > on the fly. > >