From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: A minor problem with exporting to html Date: Sun, 23 Mar 2014 09:50:24 +0100 Message-ID: <87ppldl2nj.fsf@bzg.ath.cx> References: <20140323080845.3e5083ac@aga-netbook> <877g7lnx96.fsf@bzg.ath.cx> <20140323094459.1208eb2f@aga-netbook> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRe70-00005z-8d for emacs-orgmode@gnu.org; Sun, 23 Mar 2014 04:50:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WRe6u-0001vb-VE for emacs-orgmode@gnu.org; Sun, 23 Mar 2014 04:50:34 -0400 Received: from rs249.mailgun.us ([209.61.151.249]:49587) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRe6u-0001vX-NQ for emacs-orgmode@gnu.org; Sun, 23 Mar 2014 04:50:28 -0400 In-Reply-To: <20140323094459.1208eb2f@aga-netbook> (Marcin Borkowski's message of "Sun, 23 Mar 2014 09:44:59 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Marcin Borkowski Cc: emacs-orgmode@gnu.org Marcin Borkowski writes: > But I'd strongly suggest making nil the default value. I find the > current setting strongly unintuitive (unless one read the manual, that > is;)), and not really needed (at least for me). If I have the export > results in a separate buffer or file, why would I need them in the kill > ring? I guess the default value is a left-over from the time when the HTML export was just a quick hack, targetting users who want to export small Org buffer and copy that into another (bigger) HTML file. Not sure. > Besides, I often want to do something like this: kill a fragment > of my buffer (usually some option, but not necessarily), export the > file, decide that I preferred the previous version, and yank it back. > Obviously, I can use undo - but what about yanking it in another place, > for instance? I don't know any other place than the kill-ring, but setting `org-export-copy-to-kill-ring' to nil should solve the problem, already, no? -- Bastien