emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien Guerry <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: Release 5.23a
Date: Tue, 11 Mar 2008 01:15:18 +0000	[thread overview]
Message-ID: <87myp683ix.fsf@bzg.ath.cx> (raw)
In-Reply-To: <47D5D90E.8010508@cornell.edu> (Xin Shi's message of "Mon, 10 Mar 2008 20:57:50 -0400")

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.

But I certainly wouldn't go for an option about this.

What people think?

>> 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.

-- 
Bastien

  reply	other threads:[~2008-03-11  1:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-10 22:04 Release 5.23a Carsten Dominik
2008-03-11  0:03 ` Xin Shi
2008-03-11  0:20   ` Bastien
2008-03-11  0:57     ` Xin Shi
2008-03-11  1:15       ` Bastien Guerry [this message]
2008-03-11  1:52         ` Xiao-Yong Jin
2008-03-11  2:21           ` Xin Shi
2008-03-11  2:05         ` Xin Shi
2008-03-11  2:56   ` Carsten Dominik
2008-03-11  3:47     ` Richard G Riley
2008-03-11  5:11       ` Carsten Dominik
2008-03-11 13:26       ` Xin Shi
2008-03-11 15:00         ` Richard G Riley
2008-03-11 15:03           ` Xin Shi
2008-03-13  7:16           ` Carsten Dominik
2008-03-11 16:58 ` Release 5.23a - [BUG ?] closing-notes Giovanni Ridolfi
2008-03-11 18:23   ` Bastien
2008-03-12 21:14 ` Release 5.23a Jost Burkardt
2008-03-13  7:36   ` Carsten Dominik
2008-03-13 16:34   ` Carsten Dominik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87myp683ix.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).