Dnia 2014-03-23, o godz. 09:50:24
Bastien napisał(a):
> 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
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 t
Dnia 2014-03-23, o godz. 09:18:45
Bastien napisał(a):
> Hi Marcin,
>
> Marcin Borkowski writes:
>
> > 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?
>
> (set
Hi Marcin,
Marcin Borkowski writes:
> 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?
(setq org-export-copy-to-kill-ring nil)
I'm all for using nil as the default
Hi all,
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?
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University
