From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Stanton Subject: Sporadic problems pasting Date: Wed, 2 May 2012 12:06:30 -0700 Message-ID: References: <87lilarevn.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:57024) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SPet0-0007Dh-R7 for emacs-orgmode@gnu.org; Wed, 02 May 2012 15:06:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SPesy-0006Ye-Vf for emacs-orgmode@gnu.org; Wed, 02 May 2012 15:06:50 -0400 Received: from gateway-b.haas.berkeley.edu ([128.32.222.40]:22812) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SPesy-0006Xo-P9 for emacs-orgmode@gnu.org; Wed, 02 May 2012 15:06:48 -0400 In-Reply-To: <87lilarevn.fsf@gmail.com> Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "emacs-orgmode@gnu.org" I've been using org-mode (version 7.8.09, release_7.8.09-482-gf47915) quite a lot over the last 24 hours to edit a file that will turn into a Beamer presentation. During the course of this editing, I've encountered a few problems. I'm not sure if these are org-mode or Emacs problems (I've just updated to Emacs 24.0.96 under OS X), but the first is that on several occasions, when cutting and pasting text in my org-mode buffer, when I press C-y to paste (or yank), instead of doing what I ask, I get a message in the minibuffer telling me something like Quit: pasteboard doesn't contain valid data At this point, I seem to be completely unable to retrieve the text I had previously cut, which is somewhat inconvenient. To try and find out more, I have debug-on-error set to t, but Emacs doesn't enter the debugger when I press C-y; it just gives me that not very useful error message. This doesn't happen anywhere close to 100% of the time, and I have no way to recreate the problem systematically, but it happened probably 4 or 5 times during the last 24 hours.