From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: A minor problem with exporting to html
Date: Sun, 23 Mar 2014 12:27:22 +0100 [thread overview]
Message-ID: <20140323122722.5ea940e6@aga-netbook> (raw)
In-Reply-To: <87ppldl2nj.fsf@bzg.ath.cx>
Dnia 2014-03-23, o godz. 09:50:24
Bastien <bzg@gnu.org> napisał(a):
> Marcin Borkowski <mbork@wmi.amu.edu.pl> 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?
Well, yes - it did it for me, at least. But it required setting the
option. And I suspect that what the majority of users might
need/expect is having this option set to nil - that was what I meant.
BTW, I also think that Org is awesome. Thanks a lot!
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
prev parent reply other threads:[~2014-03-23 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-23 7:08 A minor problem with exporting to html Marcin Borkowski
2014-03-23 8:18 ` Bastien
2014-03-23 8:44 ` Marcin Borkowski
2014-03-23 8:50 ` Bastien
2014-03-23 11:27 ` Marcin Borkowski [this message]
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=20140323122722.5ea940e6@aga-netbook \
--to=mbork@wmi.amu.edu.pl \
--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).