From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: djc@resiak.org, 19716@debbugs.gnu.org
Subject: bug#19716: Excessive Windows registry accesses
Date: Thu, 07 Dec 2017 20:44:55 -0500 [thread overview]
Message-ID: <87fu8mf0x4.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83zj92megb.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Jan 2015 05:51:48 +0200")
tags 19716 wontfix
close 19716
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 28 Jan 2015 22:06:49 +0100
>> From: PK <djc@resiak.org>
>>
>> > Anyway, why do you think this [duplicated identical OpenKey accesses] is a bug?
>>
>> Because it suggests faulty logic to me. Normally if I were looking for a
>> resource and either finding it or not, I'd keep the outcome the first time
>> and use that outcome. (Not found? Don't look again. Found? Use what was
>> found.)
>
> The Registry is a place that can change outside Emacs control. So the
> fact we didn't find there something doesn't make sure it won't be
> found on the next access.
>
>> If it's cheap to make those more than 3600 duplicate registry accesses,
>> then I suppose there's nothing wrong with it. (I tend to suspect that very
>> little in Windows is cheap, but I haven't measured the cost of those
>> calls.) You seem to hint that it's logic transliterated from X, which
>> *does* have cheap access, and I can see the value in not fiddling with
>> logic that works. Still...
>
> X resources can be put into the Registry whenever the user wants, and
> should work starting from then.
>
> Please do time these accesses. I don't think they are expensive, but
> if your data shows otherwise, we could look into this.
Seems no data is forthcoming.
prev parent reply other threads:[~2017-12-08 1:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 18:32 bug#19716: Excessive Windows registry accesses PK
2015-01-28 19:14 ` Eli Zaretskii
[not found] ` <54C94F69.3090403@resiak.org>
2015-01-29 3:51 ` Eli Zaretskii
2017-12-08 1:44 ` Noam Postavsky [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fu8mf0x4.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=19716@debbugs.gnu.org \
--cc=djc@resiak.org \
--cc=eliz@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.
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.