From: Eli Zaretskii <eliz@gnu.org>
To: Van L <van@scratch.space>
Cc: 34969@debbugs.gnu.org
Subject: bug#34969: 26.2; `emacs -Q` unable to copy \200's eight-bit detail buffer
Date: Sun, 24 Mar 2019 17:22:32 +0200 [thread overview]
Message-ID: <83pnqgnvpj.fsf@gnu.org> (raw)
In-Reply-To: <m2y3557xf7.fsf@scratch.space> (message from Van L on Sun, 24 Mar 2019 14:39:56 +1100)
> From: Van L <van@scratch.space>
> Date: Sun, 24 Mar 2019 14:39:56 +1100
>
> : 6
> : [has problem the third time]
> : [on XQuartz]
> : [~/bin/emacs26.2r1 links to \200nfs\200/build/emacs26.2-rc1/bin/emacs-26.2]
> : GNU Emacs 26.2 (build 1, x86_64-apple-darwin15.6.0, X toolkit)
> : of 2019-03-21
>
> : 7 `emacs -Q`
> : [this is the first time for `emacs -Q]
> : [has problem the forth time run for thise version]
> : [on XQuartz]
> : [~/bin/emacs26.2r1 links to \200nfs\200/build/emacs26.2-rc1/bin/emacs-26.2]
> : GNU Emacs 26.2 (build 1, x86_64-apple-darwin15.6.0, X toolkit)
> : of 2019-03-21
Does "the forth time" mean do all the steps 4 times before the problem
happens? Or does it mean repeat only some of the steps 4 times?
IOW, can you please show the transcript of repeated steps in these
situations?
What happens if you set interprogram-cut-function and
interprogram-paste-function to nil?
(And why do your symlink targets include \200 characters?)
next prev parent reply other threads:[~2019-03-24 15:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 3:39 bug#34969: 26.2; `emacs -Q` unable to copy \200's eight-bit detail buffer Van L
2019-03-24 15:22 ` Eli Zaretskii [this message]
2019-03-25 3:14 ` Van L
2019-03-25 17:46 ` Eli Zaretskii
2019-03-25 23:46 ` Van L
2019-03-26 16:23 ` Eli Zaretskii
2019-03-26 22:08 ` Van L
2019-03-27 3:37 ` Eli Zaretskii
2019-03-27 5:23 ` Van L
2019-03-27 15:46 ` Eli Zaretskii
2019-03-27 22:10 ` Van L
2019-03-31 1:02 ` Van L
2019-03-31 16:16 ` Eli Zaretskii
2019-04-01 1:01 ` Van L
2019-04-01 4:34 ` Eli Zaretskii
2019-04-02 11:07 ` Van L
2022-04-13 2:03 ` bug#34969: [macOS, external clipboard manager?] can't " Lars Ingebrigtsen
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pnqgnvpj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34969@debbugs.gnu.org \
--cc=van@scratch.space \
/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.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).