From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xin Shi Subject: Re: Release 5.23a Date: Mon, 10 Mar 2008 22:21:55 -0400 Message-ID: <47D5ECC3.7080100@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> <87zlt66n8u.fsf@columbia.edu> 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 1JYu7r-0005w6-Cl for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:21:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JYu7p-0005vr-UK for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:21:59 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JYu7p-0005vo-IT for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:21:57 -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 1JYu7p-0008TH-BG for emacs-orgmode@gnu.org; Mon, 10 Mar 2008 22:21:57 -0400 Received: from [128.84.46.18] (lnx618.lns.cornell.edu [128.84.46.18]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.13.1/8.12.10) with ESMTP id m2B2Lt2P015023 for ; Mon, 10 Mar 2008 22:21:56 -0400 (EDT) In-Reply-To: <87zlt66n8u.fsf@columbia.edu> 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: emacs-orgmode@gnu.org Hi Xiao-Yong, Thanks for your message! I'll look into the nXhtml mode to turn that off. Xin Xiao-Yong Jin wrote: > Bastien Guerry writes: > > >> 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. >> > > I second that. Because I use `midnight' to take care of > useless buffers and `ido' does well on choosing buffers, > leaving such a buffer open is not completely useless, if > people have enough RAM. > > >> But I certainly wouldn't go for an option about this. >> >> What people think? >> > > I think it could be an option, if someone thinks he/she > would use it. At the very least, we can have an option to > keep our environment green. > > > And a second thought on Xin's issue. I believe the one whom > we should blame to is nXhtml mode, because if I understand > correctly, his problem is that an additional window being > created by nXhtml mode, when the html file is generated. So > I would guess that even if the buffer is killed after the > generation, that additional nXhtml window would still be > there. Therefore, I would suggest that Xin disable the > annoying/useless behaviour of nXhtml mode. > > Xiao-Yong >