all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 28630@debbugs.gnu.org, tom@tromey.com, agrambot@gmail.com,
	dgutov@yandex.ru
Subject: bug#28630: 27.0.50; C-g while a non-main thread is sitting crashes Emacs
Date: Tue, 03 Oct 2017 17:04:28 +0000	[thread overview]
Message-ID: <CAArVCkQcy85mWRrwmsCU0DEW5t9YwxBVkbNWwaadw3PhP+hoYQ@mail.gmail.com> (raw)
In-Reply-To: <833770195e.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Eli Zaretskii <eliz@gnu.org> schrieb am Di., 3. Okt. 2017 um 18:37 Uhr:

> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Tue, 03 Oct 2017 16:22:56 +0000
> > Cc: dgutov@yandex.ru, 28630@debbugs.gnu.org, tom@tromey.com,
> >       agrambot@gmail.com
> >
> >  > Since no released version of Emacs has thread support, I'm not
> surprised that they aren't widely used
> >  yet.
> >
> >  Well, I am, because Reddit, for example, is full of people who say
> >  they use Emacs 26.
> >
> > I guess there's a huge selection bias at play. Most users typically use
> whatever version their OS distributor
> > provides, and that's often not even Emacs 25. Libraries tend to support
> 24.x as well, and therefore can't use
> > threads until they drop compatibility with both 24.x and 25.x.
>
> We are talking about developers, not users.  And newer versions can be
> supported by using the relevant version-comparison stuff.
>

Sure, but it's already a lot of work to use threads unconditionally, and
they are a feature that can't be easily polyfilled. So I can understand
that library developers are hesitant.

[-- Attachment #2: Type: text/html, Size: 1786 bytes --]

  reply	other threads:[~2017-10-03 17:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28  7:22 bug#28630: 27.0.50; C-g while a non-main thread is sitting crashes Emacs Alex
2017-10-01  3:18 ` Alex
2017-10-01 15:01   ` Eli Zaretskii
2017-10-01 18:10     ` Alex
2017-10-01 18:32       ` Eli Zaretskii
2017-10-02  4:30         ` YAMAMOTO Mitsuharu
2017-10-02 12:43           ` YAMAMOTO Mitsuharu
2017-10-02 16:08             ` Eli Zaretskii
2017-10-04  7:39               ` Eli Zaretskii
2017-10-04  7:49                 ` YAMAMOTO Mitsuharu
2017-10-04  8:16                   ` Eli Zaretskii
2017-10-04  8:32                     ` YAMAMOTO Mitsuharu
2017-10-04  9:23                       ` Eli Zaretskii
2017-10-05  3:27                         ` YAMAMOTO Mitsuharu
2017-10-05  7:24                           ` Eli Zaretskii
2017-10-07 13:53                             ` Philipp Stephani
2017-10-07 14:24                               ` Eli Zaretskii
2017-10-07 14:50                                 ` Eli Zaretskii
2017-10-09  8:21                             ` YAMAMOTO Mitsuharu
2017-10-09  8:38                               ` Eli Zaretskii
2017-10-09 10:34                                 ` mituharu
2017-10-09 11:01                                   ` Eli Zaretskii
2017-10-04  7:39               ` YAMAMOTO Mitsuharu
2017-10-04  8:14                 ` Eli Zaretskii
2017-10-02  5:11         ` Eric Abrahamsen
2017-10-02 15:54           ` Eli Zaretskii
2017-10-03  9:35         ` Dmitry Gutov
2017-10-03 14:38           ` Eli Zaretskii
2017-10-03 14:50             ` Philipp Stephani
2017-10-03 15:45               ` Eli Zaretskii
2017-10-03 16:22                 ` Philipp Stephani
2017-10-03 16:35                   ` Eli Zaretskii
2017-10-03 17:04                     ` Philipp Stephani [this message]
2017-10-01 10:08 ` Alan Third
2017-10-01 15:03   ` Eli Zaretskii

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=CAArVCkQcy85mWRrwmsCU0DEW5t9YwxBVkbNWwaadw3PhP+hoYQ@mail.gmail.com \
    --to=p.stephani2@gmail.com \
    --cc=28630@debbugs.gnu.org \
    --cc=agrambot@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=tom@tromey.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 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.