From: "Grégoire Jadi" <gjadi@omecha.info>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 29170@debbugs.gnu.org, jca@wxcvbn.org
Subject: bug#29170: 26.0.90; Emacs freezes when capturing an org-template
Date: Fri, 13 Aug 2021 09:36:33 +0200 [thread overview]
Message-ID: <87a6lllrsu.fsf@puffy.omecha.info> (raw)
In-Reply-To: <87v94e4x5l.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 09 Aug 2021 14:31:34 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Grégoire Jadi <gjadi@omecha.info> writes:
>
>> So we think it is safe to backport this change upstream.
>
> [...]
>
>> dnl SIGIO exists, but the feature doesn't work in the way Emacs needs.
>> - hpux* | nacl | openbsd | solaris | unixware )
>> + hpux* | nacl | solaris | unixware )
>
> Thanks; I've now applied this to Emacs 28.
Thanks !
>
>> Please note that the real issue is not fixed. The issue is in the
>> broken SIGIO code itself. I was able to reproduce the bug by enabling
>> emacs_broken_SIGIO on Ubuntu LTS 20.04. I didn't take the time to find
>> a fix though.
>
> The remaining operating systems that uses the broken_SIGIO code paths
> are pretty obscure -- I guess Solaris is still used to some degree.
>
> Hm, let's see... I guess the code paths that are exercised are the ones
> where USABLE_SIGIO is undefined? Do you have a simple test case for
> this (on Ubuntu, for instance)? I think it might make sense to open a
> new bug report for this.
Yes, the same snippet used to trigger the bug on OpenBSD can be used:
> (let ((value 'SECONDARY)
> (x-selection-timeout 2000))
> ;;; from org-get-x-clipboard in lisp/org-compat.el
> (gui-get-selection value 'UTF8_STRING)
> (gui-get-selection value 'COMPOUND_TEXT)
> (gui-get-selection value 'STRING)
> (gui-get-selection value 'TEXT))
Best regards,
--
gjadi
PGP : AF26 E9C2 A1C8 8D32 A868 4386 1373 5477 2B65 1894
next prev parent reply other threads:[~2021-08-13 7:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877dtojnf0.fsf@elite.giraud>
2017-11-06 14:20 ` bug#29170: 26.0.90; Emacs freezes when capturing an org-template Grégoire Jadi
2017-11-08 18:00 ` bug#29170: Infinite loop noticed on Emacs in OpenBSD Piotr Isajew
2017-11-09 15:06 ` Manuel Giraud
2017-11-17 14:36 ` Grégoire Jadi
2017-11-22 14:44 ` Manuel Giraud
2017-11-22 14:50 ` Grégoire Jadi
2017-11-22 15:00 ` Manuel Giraud
2020-08-24 11:43 ` Stefan Kangas
2020-08-24 11:45 ` Stefan Kangas
2020-10-02 5:16 ` bug#29170: 26.0.90; Emacs freezes when capturing an org-template Lars Ingebrigtsen
2020-10-02 7:12 ` Eli Zaretskii
2020-10-02 14:30 ` Lars Ingebrigtsen
2020-10-02 15:08 ` Eli Zaretskii
2020-10-02 17:55 ` daimrod
2020-10-03 17:51 ` Lars Ingebrigtsen
2020-10-08 21:43 ` daimrod
2020-10-10 19:57 ` Lars Ingebrigtsen
2021-08-08 14:33 ` Grégoire Jadi
2021-08-08 14:49 ` Eli Zaretskii
2021-08-08 14:53 ` Grégoire Jadi
2021-08-09 12:31 ` Lars Ingebrigtsen
2021-08-13 7:36 ` Grégoire Jadi [this message]
2021-08-13 11:50 ` Lars Ingebrigtsen
2021-08-13 11:52 ` Lars Ingebrigtsen
2021-05-25 10:55 ` bug#29170: bug29170 graeme vetterlein
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=87a6lllrsu.fsf@puffy.omecha.info \
--to=gjadi@omecha.info \
--cc=29170@debbugs.gnu.org \
--cc=jca@wxcvbn.org \
--cc=larsi@gnus.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 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).