From: Van L <van@scratch.space>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34969@debbugs.gnu.org
Subject: bug#34969: 26.2; `emacs -Q` unable to copy \200's eight-bit detail buffer
Date: Wed, 27 Mar 2019 16:23:08 +1100 [thread overview]
Message-ID: <3A28832C-0A6C-4155-853B-A76F76C0774B@scratch.space> (raw)
In-Reply-To: <83h8bpkmwm.fsf@gnu.org>
> Eli Zaretskii wrote:
>
>> Emacs was started 7-times and a-f steps performed in each once.
>
> Then what does "the second time above" mean?
The meaning is the `2nd run of v26.2: emacs` performing
a-f steps within the new single instance isolated session.
: 1 -- 1st run of v26.2: emacs
: [has *no* problem the 1st run]
: GNU Emacs 26.2 (build 1, x86_64-apple-darwin15.6.0, X toolkit)
: of 2019-03-21
: 4 -- 2nd run of v26.2: emacs <<-- SEE HERE <<--
: [has problem the 2nd run]
: GNU Emacs 26.2 (build 1, x86_64-apple-darwin15.6.0, X toolkit)
: of 2019-03-21
: 6 -- 3rd run of v26.2: emacs
: [has problem the 3rd run]
: GNU Emacs 26.2 (build 1, x86_64-apple-darwin15.6.0, X toolkit)
: of 2019-03-21
: 7 -- 4th run of v26.2; but this is 1st run as: `emacs -Q`
: [has problem the 4th run]
: GNU Emacs 26.2 (build 1, x86_64-apple-darwin15.6.0, X toolkit)
: of 2019-03-21
next prev parent reply other threads:[~2019-03-27 5:23 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A28832C-0A6C-4155-853B-A76F76C0774B@scratch.space \
--to=van@scratch.space \
--cc=34969@debbugs.gnu.org \
--cc=eliz@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.