From: Angelo Graziosi <angelo.g0@libero.it>
To: martin rudalics <rudalics@gmx.at>, Eli Zaretskii <eliz@gnu.org>
Cc: sebastian_rose@gmx.de, hong@topbug.net, emacs-devel@gnu.org
Subject: Re: Current master does not work with sr-speedbar package (W64 build)
Date: Thu, 6 Dec 2018 17:12:51 +0100 (CET) [thread overview]
Message-ID: <461330378.433529.1544112771118@mail.libero.it> (raw)
In-Reply-To: <5C08E773.8070309@gmx.at>
> Il 6 dicembre 2018 alle 10.10 martin rudalics <rudalics@gmx.at> ha scritto:
>
>
> > I have uninstalled the sr-speedbar and tried to reinstall it, but
> > this fails because Emacs tries to set permission to
> > c:/msys64/tmp/src which, usually, does not exist. Some change in the
> > last month caused this. Maybe , if I have time, I will try to bisect
> > this to know when it occurred.
>
> Please do that bisection. What was the last time (on master, I
> suppose) this worked as you expected?
Just for the record,
building http://git.savannah.gnu.org/cgit/emacs.git/snapshot/emacs-88762b4063a42a69234bda74b1626b646734715a.tar.gz, which should be a 20181118 master source, builds Emacs 26.90.1... as also confirms this: http://git.savannah.gnu.org/cgit/emacs.git/tree/README?id=88762b4063a42a69234bda74b1626b646734715a...
Is this to be expected?
next prev parent reply other threads:[~2018-12-06 16:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 17:50 Current master does not work with sr-speedbar package (W64 build) Angelo Graziosi
2018-12-04 17:57 ` Eli Zaretskii
2018-12-04 23:31 ` Angelo Graziosi
2018-12-05 18:34 ` Eli Zaretskii
2018-12-05 22:42 ` Angelo Graziosi
2018-12-05 23:07 ` Angelo Graziosi
2018-12-06 0:07 ` Angelo Graziosi
2018-12-06 0:12 ` Angelo Graziosi
2018-12-06 0:54 ` Angelo Graziosi
2018-12-06 6:48 ` Eli Zaretskii
2018-12-06 9:10 ` martin rudalics
2018-12-06 16:12 ` Angelo Graziosi [this message]
2018-12-06 6:35 ` Eli Zaretskii
2018-12-06 9:00 ` Angelo Graziosi
2018-12-06 9:17 ` Eli Zaretskii
2018-12-06 11:28 ` Angelo Graziosi
2018-12-06 12:57 ` Eli Zaretskii
2018-12-06 17:49 ` Angelo Graziosi
2018-12-06 18:20 ` Eli Zaretskii
2018-12-06 19:36 ` Angelo Graziosi
2018-12-06 19:47 ` Eli Zaretskii
2018-12-06 20:45 ` Angelo Graziosi
2018-12-06 23:55 ` Angelo Graziosi
2018-12-07 8:04 ` Eli Zaretskii
2018-12-07 8:57 ` Eli Zaretskii
2018-12-07 16:34 ` Angelo Graziosi
2018-12-07 16:44 ` Eli Zaretskii
2018-12-07 6:22 ` Eli Zaretskii
2018-12-07 8:34 ` Angelo Graziosi
2018-12-07 0:36 ` Stefan Monnier
2018-12-07 7:13 ` martin rudalics
2018-12-07 13:00 ` Stefan Monnier
2018-12-07 13:16 ` martin rudalics
2018-12-07 13:26 ` Stefan Monnier
2018-12-07 13:49 ` martin rudalics
2018-12-10 15:07 ` Stefan Monnier
2018-12-07 13:58 ` Eli Zaretskii
2018-12-07 13:22 ` Eli Zaretskii
2018-12-06 18:45 ` martin rudalics
2018-12-06 19:34 ` Angelo Graziosi
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=461330378.433529.1544112771118@mail.libero.it \
--to=angelo.g0@libero.it \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hong@topbug.net \
--cc=rudalics@gmx.at \
--cc=sebastian_rose@gmx.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 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).