emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Cc: Konstantin Kliakhandler <kosta@slumpy.org>
Subject: Re: Kill ring contains non-killed output after an export
Date: Sun, 06 Apr 2014 18:46:01 -0700	[thread overview]
Message-ID: <87ob0dj4iu.fsf@berkeley.edu> (raw)
In-Reply-To: m2lhvio1j1.fsf@slumpy.org


Konstantin Kliakhandler <kosta@slumpy.org> writes:

> Richard Lawrence <richard.lawrence@berkeley.edu> writes:
>> The behavior you are seeing is as expected, though I agree that this
>> behavior is usually not all that useful.  See the variable
>> org-export-copy-to-kill-ring if you want to turn it off.
>
> Thanks! Now the export is much more usable for me. Out of curiousity,
> what is the use case of the default behavior?

I have no idea...if I had to take a guess, it would be that when
exporting a region as a LaTeX *snippet*, such as a table, it could be
useful to yank the resulting code into another buffer.  But I really
can't think of a situation where yanking a whole .tex document from the
kill ring is preferable to just visiting the exported file/buffer.  So
I'm all for changing the default behavior.

Best,
Richard

  reply	other threads:[~2014-04-07  1:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05 16:33 Bug: Kill ring contains non-killed output after an export to pdf [8.2.5h (8.2.5h-30-gdd810b-elpa @ /Users/kosta/.emacs.d/elpa/org-20140303/)] Konstantin Kliakhandler
2014-04-05 17:37 ` Kill ring contains non-killed output after an export Richard Lawrence
2014-04-06 16:39   ` Konstantin Kliakhandler
2014-04-07  1:46     ` Richard Lawrence [this message]
2014-04-17 14:33     ` Bastien
2014-04-17 14:32   ` Bastien
2014-04-17 16:15     ` Nicolas Goaziou
2014-04-17 16:23       ` Bastien

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=87ob0dj4iu.fsf@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=kosta@slumpy.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).