Re: Release 5.23a

[Xin Shi <xs32@cornell.edu>]

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 <bzg@altern.org> writes:
>
>   
>> Xin Shi <xs32@cornell.edu> 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
>