[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 26.2 RC1 copy-and-paste fail
From: |
Eli Zaretskii |
Subject: |
Re: 26.2 RC1 copy-and-paste fail |
Date: |
Fri, 22 Mar 2019 10:15:22 +0300 |
> 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.
- 26.1.92, 26.1-mac-7.4; unrecognised escaped chars in *Help*, Van L, 2019/03/03
- Re: 26.1.92, 26.1-mac-7.4; unrecognised escaped chars in *Help*, Eli Zaretskii, 2019/03/05
- Re: 26.1.92, 26.1-mac-7.4; unrecognised escaped chars in *Help*, Van L, 2019/03/05
- Re: 26.1.92, 26.1-mac-7.4; unrecognised escaped chars in *Help*, Eli Zaretskii, 2019/03/06
- Re: 26.2 RC1 copy-and-paste fail, Van L, 2019/03/21
- Re: 26.2 RC1 copy-and-paste fail, Eli Zaretskii, 2019/03/21
- Re: 26.2 RC1 copy-and-paste fail, Van L, 2019/03/21
- Re: 26.2 RC1 copy-and-paste fail,
Eli Zaretskii <=
- Re: 26.2 RC1 copy-and-paste fail, Van L, 2019/03/22
- Re: 26.2 RC1 copy-and-paste fail, Eli Zaretskii, 2019/03/22
- Re: 26.2 RC1 copy-and-paste fail, Van L, 2019/03/22
- Re: 26.2 RC1 copy-and-paste fail, Eli Zaretskii, 2019/03/22
- Re: 26.2 RC1 copy-and-paste fail, Van L, 2019/03/24