From: phillip.lord@russet.org.uk (Phillip Lord)
To: "Jostein Kjønigsen" <jostein@secure.kjonigsen.net>
Cc: jostein@kjonigsen.net, emacs-devel@gnu.org
Subject: Re: Windows snapshot builds
Date: Tue, 27 Mar 2018 21:52:22 +0100 [thread overview]
Message-ID: <87r2o5gs1l.fsf@russet.org.uk> (raw)
In-Reply-To: <1522167476.1298329.1317868904.779AEDB7@webmail.messagingengine.com> ("Jostein Kjønigsen"'s message of "Tue, 27 Mar 2018 18:17:56 +0200")
Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:
> If you keep publishing these, this might be my new way to keep my
> Emacs updated on my Windows-machine!
I plan to, but even if I don't the code is in the repo now and it's
relatively easy to do.
> They -are- very convenient and with an installer like this, I believe
> the basic installation procedure should no longer be a road-block for
> Windows-users to try out Emacs. As such, this is a major milestone.
Yeah, I've watched people try to install Emacs before and the look of
confusion is terrifying to see. Even the fact that the file is called
"-installer.exe" should help significantly.
It's a shame it's slated for Emacs-27. Too late to merge into Emacs-26
now, although I guess it could be back-ported.
> There's still the issue about the lack code-signing, and Windows' GUI
> isn't getting any friendlier about that, but I guess that's a
> technicality we can leave for later, when there are no other issues
> to sort out.
Code-signing is a significant problem. The certificates are not free, I
don't have any need for a personal one and, anyway, it should probably
be done with a certificate from Gnu. AFAICT, though, technologically
it's simple enough.
> Ladies and gentlemen: I believe this man deserves some applause.
> Great work!
I appreciate the compliment. I shall be even happier if it gets lots of
downloads.
Phil
next prev parent reply other threads:[~2018-03-27 20:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 9:50 Windows snapshot builds Phillip Lord
2018-03-27 16:17 ` Jostein Kjønigsen
2018-03-27 16:27 ` Aurélien Aptel
2018-03-27 20:54 ` Phillip Lord
2018-03-27 20:52 ` Phillip Lord [this message]
2018-03-27 22:10 ` Rasmus
2018-03-29 11:07 ` Eli Zaretskii
2018-03-29 20:13 ` Phillip Lord
2018-04-02 12:47 ` Rasmus
2018-04-09 13:12 ` Phillip Lord
2018-04-09 13:19 ` Stefan Monnier
2018-04-09 21:45 ` Rasmus
2018-04-10 0:09 ` Richard Copley
2018-04-10 11:50 ` Phillip Lord
2018-04-10 22:14 ` Rasmus
2018-04-10 4:33 ` Stephen Leake
2018-04-10 11:51 ` Phillip Lord
-- strict thread matches above, loose matches on Subject: below --
2018-10-08 15:57 Windows Snapshot Builds Phillip Lord
2018-10-08 16:30 ` Boris Buliga
2018-10-09 11:15 ` Phillip Lord
2018-10-10 11:12 ` Jostein Kjønigsen
[not found] ` <87r2gvnzg4.fsf@russet.org.uk>
2018-10-12 12:04 ` Phillip Lord
2018-10-10 18:14 ` Alan Third
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=87r2o5gs1l.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=jostein@secure.kjonigsen.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 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).