Re: [O] Bug: non-interactive org-export-region-as... modifies kill-ring [7.9.2 (release_7.9.2-103-g488eea)]
Bastien b...@altern.org writes: Christopher Schmidt christop...@ch.ristopher.com writes: Title says it all. For example evaling (org-export-region-as-latex (point-min) (point-max) nil (get-buffer-create res)) via M-: in an org-mode buffer will put the export content in the kill ring. That's not nice. I think only the interactive call should do that. There is org-export-copy-to-kill-ring. I added a new choice 'if-interactive which is now the default: exported text will only be pushed to the kill ring when export is done interactively. You can always set it to nil if you want. Thank you very much. Christopher
[O] Bug: non-interactive org-export-region-as... modifies kill-ring [7.9.2 (release_7.9.2-103-g488eea)]
Title says it all. For example evaling (org-export-region-as-latex (point-min) (point-max) nil (get-buffer-create res)) via M-: in an org-mode buffer will put the export content in the kill ring. That's not nice. I think only the interactive call should do that. Christopher
Re: [O] Bug: non-interactive org-export-region-as... modifies kill-ring [7.9.2 (release_7.9.2-103-g488eea)]
Hi Christopher, Christopher Schmidt christop...@ch.ristopher.com writes: Title says it all. For example evaling (org-export-region-as-latex (point-min) (point-max) nil (get-buffer-create res)) via M-: in an org-mode buffer will put the export content in the kill ring. That's not nice. I think only the interactive call should do that. There is org-export-copy-to-kill-ring. I added a new choice 'if-interactive which is now the default: exported text will only be pushed to the kill ring when export is done interactively. You can always set it to nil if you want. Best, -- Bastien