From: Van L <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: 26.2 RC1 copy-and-paste fail
Date: Sat, 23 Mar 2019 01:01:21 +1100 [thread overview]
Message-ID: <m2zhpnj9e6.fsf@scratch.space> (raw)
In-Reply-To: m2a7hnoo1c.fsf@scratch.space
> Do you have any customizations related to encoding selections?
LANG=en_AU.UTF-8
> If nothing else gives a hint, bisect your customizations to find the
> culprit.
I use the same .emacs file for parallel running instances of
GNU/Emacs version 26.1, 26.1.92, 26.2-rc1, 27.0.50. That complicates
it. I will give bisecting a try. Thanks.
next prev parent reply other threads:[~2019-03-22 14:01 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
2019-03-22 8:35 ` Van L
2019-03-22 9:10 ` Eli Zaretskii
2019-03-22 14:01 ` Van L [this message]
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
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=m2zhpnj9e6.fsf@scratch.space \
--to=van@scratch.space \
--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.
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).