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: Sat, 05 Apr 2014 10:37:36 -0700	[thread overview]
Message-ID: <87d2gvk78f.fsf@berkeley.edu> (raw)
In-Reply-To: m2lhvjivn7.fsf@slumpy.org

Hi Konstantin,

Konstantin Kliakhandler <kosta@slumpy.org> writes:

> Whenever I export an org file to pdf, subsequently my kill-ring contains
> the tex code of the intermediate latex stage.
> ...
> What I would expect to get: the last thing I killed.

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.

Changing the default value of this variable was recently discussed on
this list:

http://thread.gmane.org/gmane.emacs.orgmode/84048/focus=84055

Looks like there haven't been any strong objections to changing it, but
maybe the subject of this thread will grab some more attention for the
issue.

Best,
Richard


(If possible, please encrypt your reply to me using my PGP key:
Key ID: CF6FA646
Fingerprint: 9969 43E1 CF6F A646.
See http://www.ocf.berkeley.edu/~rwl/encryption.html for more information.)

  reply	other threads:[~2014-04-05 17:39 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 ` Richard Lawrence [this message]
2014-04-06 16:39   ` Kill ring contains non-killed output after an export Konstantin Kliakhandler
2014-04-07  1:46     ` Richard Lawrence
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=87d2gvk78f.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).