From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: michael_heerdegen@web.de, 17392@debbugs.gnu.org
Subject: bug#17392: 24.3.90; cursor blinks faster and faster
Date: Fri, 16 May 2014 08:30:59 +0300 [thread overview]
Message-ID: <83lhu2mgrw.fsf@gnu.org> (raw)
In-Reply-To: <CANbX364EoYokTT4FQtp40-npEr5LybNX0TyN47BC4z_GK5FQqA@mail.gmail.com>
> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Thu, 15 May 2014 22:22:12 +0200
> Cc: Michael Heerdegen <michael_heerdegen@web.de>, 17392@debbugs.gnu.org
>
> On Thu, May 15, 2014 at 9:17 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > How can there be race conditions when all the relevant code runs in a
> > single thread?
>
> How do we know that?
Because we write the code.
Please, can we stop this waste of time? You are talking about a code
base with which you are not familiar enough in order to make such
claims. If you don't even know which parts of Emacs run in which
threads, on Windows and on Unix, then there's no point in having this
conversation.
Please stop, there's a real bug out there that needs to be discussed
in this thread.
next prev parent reply other threads:[~2014-05-16 5:30 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 1:44 bug#17392: 24.3.90; cursor blinks faster and faster Michael Heerdegen
2014-05-03 18:33 ` Michael Heerdegen
2014-05-03 22:29 ` Michael Heerdegen
2014-05-05 12:25 ` Stefan Monnier
2014-05-05 13:14 ` Lennart Borgman
2014-05-05 20:17 ` Michael Heerdegen
2014-05-05 23:07 ` Michael Heerdegen
2014-05-05 23:30 ` Michael Heerdegen
2014-05-06 21:20 ` Michael Heerdegen
2014-05-07 2:02 ` Stefan Monnier
2014-05-07 2:14 ` Michael Heerdegen
2014-05-07 13:15 ` Stefan Monnier
2014-05-08 16:52 ` Michael Heerdegen
2014-05-08 17:04 ` Eli Zaretskii
2014-05-08 17:09 ` Lennart Borgman
2014-05-08 17:42 ` Michael Heerdegen
2014-05-08 18:40 ` Lennart Borgman
2014-05-10 10:34 ` Michael Heerdegen
2014-05-10 11:06 ` Eli Zaretskii
2014-05-10 11:40 ` Michael Heerdegen
2014-05-10 12:32 ` Eli Zaretskii
2014-05-10 16:16 ` Eli Zaretskii
2014-05-11 11:09 ` Michael Heerdegen
2014-05-11 16:40 ` Eli Zaretskii
2014-05-13 16:04 ` Michael Heerdegen
2014-05-13 17:50 ` Eli Zaretskii
2014-05-13 17:58 ` Lennart Borgman
2014-05-13 18:14 ` Eli Zaretskii
2014-05-13 18:25 ` Lennart Borgman
2014-05-13 18:44 ` Eli Zaretskii
2014-05-13 18:50 ` Lennart Borgman
2014-05-13 19:47 ` Eli Zaretskii
2014-05-13 20:10 ` Lennart Borgman
2014-05-14 2:40 ` Eli Zaretskii
2014-05-13 20:22 ` Stefan Monnier
2014-05-14 2:43 ` Eli Zaretskii
2014-05-14 14:59 ` Eli Zaretskii
2014-05-14 15:36 ` Michael Heerdegen
2014-05-14 16:00 ` Michael Heerdegen
2014-05-14 16:13 ` Eli Zaretskii
2014-05-14 17:23 ` Michael Heerdegen
2014-05-14 18:15 ` Eli Zaretskii
2014-05-14 19:11 ` Lennart Borgman
2014-05-14 19:30 ` Eli Zaretskii
2014-05-14 20:17 ` Lennart Borgman
2014-05-15 2:40 ` Eli Zaretskii
2014-05-15 3:31 ` Lennart Borgman
2014-05-15 17:04 ` Eli Zaretskii
2014-05-15 19:11 ` Lennart Borgman
2014-05-15 19:17 ` Eli Zaretskii
2014-05-15 20:22 ` Lennart Borgman
2014-05-16 5:30 ` Eli Zaretskii [this message]
2014-05-16 8:41 ` Lennart Borgman
2014-05-15 20:34 ` Glenn Morris
2014-05-15 20:44 ` Lennart Borgman
2014-05-07 2:27 ` Michael Heerdegen
2014-05-07 3:01 ` Michael Heerdegen
2014-05-07 13:57 ` Nicolas Richard
2014-05-18 13:05 ` Stefan Monnier
2014-05-18 13:41 ` Michael Heerdegen
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=83lhu2mgrw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17392@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=michael_heerdegen@web.de \
/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.