From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcin Borkowski Subject: Re: A minor problem with exporting to html Date: Sun, 23 Mar 2014 09:44:59 +0100 Message-ID: <20140323094459.1208eb2f@aga-netbook> References: <20140323080845.3e5083ac@aga-netbook> <877g7lnx96.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55914) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRe1j-0005R6-BT for emacs-orgmode@gnu.org; Sun, 23 Mar 2014 04:45:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WRe1e-0000Sx-N4 for emacs-orgmode@gnu.org; Sun, 23 Mar 2014 04:45:07 -0400 Received: from msg.wmi.amu.edu.pl ([2001:808:114:2::50]:50893) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRe1e-0000Q4-Fx for emacs-orgmode@gnu.org; Sun, 23 Mar 2014 04:45:02 -0400 Received: from localhost (localhost [127.0.0.1]) by msg.wmi.amu.edu.pl (Postfix) with ESMTP id D0B4C41D4C for ; Sun, 23 Mar 2014 09:45:00 +0100 (CET) Received: from msg.wmi.amu.edu.pl ([127.0.0.1]) by localhost (msg.wmi.amu.edu.pl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tNROsjiUOKWv for ; Sun, 23 Mar 2014 09:45:00 +0100 (CET) Received: from aga-netbook (99-234.echostar.pl [213.156.99.234]) by msg.wmi.amu.edu.pl (Postfix) with ESMTPSA id A5BD34206C for ; Sun, 23 Mar 2014 09:45:00 +0100 (CET) In-Reply-To: <877g7lnx96.fsf@bzg.ath.cx> 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: emacs-orgmode@gnu.org Dnia 2014-03-23, o godz. 09:18:45 Bastien napisa=C5=82(a): > Hi Marcin, >=20 > Marcin Borkowski writes: >=20 > > exporting to HTML messes up with the kill ring (all the exported > > content is put on top of the the kill ring). Am I the only one > > experiencing this? Is it a feature or a bug? >=20 > (setq org-export-copy-to-kill-ring nil) >=20 > I'm all for using nil as the default value by the way. >=20 > Would anyone strongly oppose to this? >=20 Ooops, it's all in the manual... 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? 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? Best, --=20 Marcin Borkowski http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski Adam Mickiewicz University