all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org, jostein@kjonigsen.net,
	npostavs@users.sourceforge.net
Subject: Re: Regarding performance issues with the Emacs 25.1 Windows-build
Date: Tue, 29 Nov 2016 21:47:01 +0000	[thread overview]
Message-ID: <87shqa3qne.fsf@russet.org.uk> (raw)
In-Reply-To: <1480443971.2319495.802762825.27B6DA15@webmail.messagingengine.com> ("Jostein Kjønigsen"'s message of "Tue, 29 Nov 2016 19:26:11 +0100")

Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:
> I haven't seen any more feedback on this on the public mailing-list
> since I last emailed, so I don't know if you've received adequate, or
> any feedback at all at this point.


Yes, you'd replied and one piece of feedback is plenty! Just a bit
work-bombed at the moment, hence the slow movement.


> I therefore wanted to let you know that I've now used this build as
> "my daily driver" since you published it, as a replacement for
> (previously superior) Emacs 24.5, and I've had no major complaints or
> incidents so far.
>
>
> In my opinion, as the one who originally raised this issue, I'm happy to
> consider this issue resolved.

Good and timely feedback. The new version on ftp.gnu.org

https://ftp.gnu.org/gnu/emacs/windows/

I'll wait a few days and then remove the unoptimized version.

> And let me say: Thanks again for your work. It's really appreciated!

No worries, am glad to have got the feedback.

I'll try and get the next pre-release out of the door as soon as I can!

Phil



  reply	other threads:[~2016-11-29 21:47 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09  8:34 Regarding performance issues with the Emacs 25.1 Windows-build Jostein Kjønigsen
2016-11-09 16:22 ` Eli Zaretskii
2016-11-09 16:55   ` Noam Postavsky
2016-11-09 17:18     ` Eli Zaretskii
2016-11-10 15:16       ` Phillip Lord
2016-11-10 22:04       ` Phillip Lord
2016-11-11  7:56         ` Eli Zaretskii
2016-11-11 20:53           ` Phillip Lord
2016-11-14 15:56             ` Phillip Lord
2016-11-14 16:19               ` Eli Zaretskii
2016-11-14 16:55                 ` Phillip Lord
2016-11-14 18:12                   ` Eli Zaretskii
2016-11-15 10:49                     ` Jostein Kjønigsen
2016-11-15 11:42                       ` Jostein Kjønigsen
2016-11-15 13:17                         ` Phillip Lord
2016-11-15 13:30                           ` Jostein Kjønigsen
2016-11-15 15:17                             ` Eli Zaretskii
2016-11-15 15:39                               ` Jostein Kjønigsen
2016-11-20  9:31                                 ` Phillip Lord
2016-11-29 18:26                                   ` Jostein Kjønigsen
2016-11-29 21:47                                     ` Phillip Lord [this message]
2016-11-30  7:56                                       ` Fabrice Popineau
2016-11-30  8:36                                         ` Jostein Kjønigsen
2016-11-30 12:51                                           ` Fabrice Popineau
2016-11-30 20:11                                           ` Richard Stallman
2016-11-30 14:48                                         ` Eli Zaretskii
2016-12-09 21:09                                           ` Fabrice Popineau
2016-12-12 17:18                                             ` Phillip Lord
2016-11-11 19:13         ` Jostein Kjønigsen
2016-11-09 17:21   ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2016-11-21 23:35 Fernando Febles Armas
2016-11-22  3:44 ` Eli Zaretskii
2017-01-09  6:33 jsj.register
2017-01-09  7:40 ` Richard Copley
2017-01-10  7:28   ` jsj.register
2017-01-09  7:57 ` Nikolay Kudryavtsev
2017-01-10  7:30   ` jsj.register

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=87shqa3qne.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jostein@kjonigsen.net \
    --cc=jostein@secure.kjonigsen.net \
    --cc=npostavs@users.sourceforge.net \
    /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.