From: Eli Zaretskii <eliz@gnu.org>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: 55712@debbugs.gnu.org
Subject: bug#55712: the fix for this broke the ability to paste into gmail plain text
Date: Wed, 10 Aug 2022 14:10:45 +0300 [thread overview]
Message-ID: <83czd8s6a2.fsf@gnu.org> (raw)
In-Reply-To: <CA+G3_PMDNE6jZMK-zfmVO-dXk_HViyL=yMFHxd+3At=FNBCc0w@mail.gmail.com> (message from Tom Gillespie on Tue, 9 Aug 2022 21:10:00 -0700)
> From: Tom Gillespie <tgbugs@gmail.com>
> Date: Tue, 9 Aug 2022 21:10:00 -0700
>
> I have a bug where emacs can no longer paste into gmail
> compose windows that are set to plain text, and the fix for
> this bug 03b780e387e54c23ac9322e329aca6e5ab4f18e6
> bisected as the bad commit. Reverting the commit resolves
> the issue.
>
> The issue is on linux under X11 on master at all points after
> 03b780. To reproduce, copy some text from emacs and try
> to paste it into a gmail compose window that is set to plain
> text mode.
>
> I do not know exactly which part of the changes induced the
> behavior, but reverting the commit clearly fixes the issue and
> allows me to paste into plain text mode compose again.
Hard to understand how completion could be related to pasting.
Could you please run the modified code under Edebug, put a breakpoint
where that commit made changes, and show the Lisp backtrace when that
breakpoint is hit? Maybe that will give us some hints.
Thanks.
prev parent reply other threads:[~2022-08-10 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 18:36 bug#55712: 29.0.50; Bad interaction between icomplete and completion-auto-select Knut Anders Hatlen
2022-05-29 19:55 ` Juri Linkov
2022-05-30 17:36 ` Juri Linkov
2022-05-30 20:55 ` Knut Anders Hatlen
2022-05-31 17:53 ` Juri Linkov
2022-08-10 4:10 ` bug#55712: the fix for this broke the ability to paste into gmail plain text Tom Gillespie
2022-08-10 11:10 ` Eli Zaretskii [this message]
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=83czd8s6a2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55712@debbugs.gnu.org \
--cc=tgbugs@gmail.com \
/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).