all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: 26.2 RC1 copy-and-paste fail
Date: Fri, 22 Mar 2019 10:15:22 +0300	[thread overview]
Message-ID: <835zsbtm5x.fsf@gnu.org> (raw)
In-Reply-To: <m2a7hnoo1c.fsf@scratch.space> (message from Van L on Fri, 22 Mar 2019 09:33:51 +1100)

> From: Van L <van@scratch.space>
> Date: Fri, 22 Mar 2019 09:33:51 +1100
> 
> > What exactly does "FAILS" mean here?  I may be blind, but this last
> > C-y does work for me, it pastes a second copy of the \200 description
> > into *scratch*.
> 
> When I paste I expect the second description of \200 eight-bit to land on
> *scratch* buffer. What I get is anything but that. For example, in the
> following quote block after //[paste 3] there is no way I can copy and
> paste the details of \200 eight-bit to there. What is pasted is an
> earlier copy of anything else in the kill ring. If it isn't an Emacs
> problem then maybe the clipboard mechanism on XQuartz/darwin is bung.

Yes, that could be it.  Is this in "emacs -Q"?  If so, do you have
some clipboard-handling application running on your system, which
could be causing this?

Failing all of the above, please submit a bug report.



  reply	other threads:[~2019-03-22  7:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04  1:46 26.1.92, 26.1-mac-7.4; unrecognised escaped chars in *Help* Van L
2019-03-05 16:07 ` Eli Zaretskii
2019-03-06  0:47   ` Van L
2019-03-06 16:13     ` Eli Zaretskii
2019-03-21 12:13       ` 26.2 RC1 copy-and-paste fail Van L
2019-03-21 14:44         ` Eli Zaretskii
2019-03-21 22:33           ` Van L
2019-03-22  7:15             ` Eli Zaretskii [this message]
2019-03-22  8:35               ` Van L
2019-03-22  9:10                 ` Eli Zaretskii
2019-03-22 14:01             ` Van L
2019-03-22 14:43               ` Eli Zaretskii
2019-03-24  4:34                 ` Van L

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=835zsbtm5x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.