From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32226@debbugs.gnu.org
Subject: bug#32226: shadowfile test failures
Date: Sat, 21 Jul 2018 15:59:21 +0200 [thread overview]
Message-ID: <87zhyk1yh2.fsf@gmx.de> (raw)
In-Reply-To: <83o9f0yaji.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Jul 2018 16:37:37 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I don't see why this would be impossible. The test suite is run from
> the MSYS Bash anyway, and if I start Emacs from there, I get this:
>
> (executable-find "sh")
> => "d:/usr/MSYS/bin/sh.exe"
The test suite is also run interactively (that's what I do), so it
cannot be guaranteed that (executable-find "sh") gives a non-nil
result. For this case, there is the REMOTE_TEMPORARY_FILE_DIRECTORY trick.
> (even though the directory where sh.exe leaves is not on the
> system-wide PATH on my systems, although most other users do place it
> on PATH). So use executable-find to get the absolute file name of the
> shell, instead of a literal "/bin/sh", and I think everything else
> should "just work", no?
>
>> So you shall declare a usable remote directory via that environment
>> variable for the MS WIndows case. If you could give me a recipe how to
>> setup a mock-up method for MS Windows - the better!
>
> Does the above fit the bill? If not, what else is needed for the
> mock-up method?
I will check your proposal next week, when I'm at work. Maybe it works,
but likely I will find only an MS Windows machine which does not offer
any sh.exe - that's Murphy. In that case, I will produce a patch which
you could check.
(All of this shouldn't stop us from closing this bug report, after
confirmation of Glenn)
Thanks, and best regards, Michael.
next prev parent reply other threads:[~2018-07-21 13:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 17:22 bug#32226: shadowfile test failures Glenn Morris
2018-07-20 19:08 ` Eli Zaretskii
2018-07-21 10:36 ` Michael Albinus
2018-07-21 12:03 ` Eli Zaretskii
2018-07-21 12:13 ` Michael Albinus
2018-07-21 12:25 ` Eli Zaretskii
2018-07-21 12:48 ` Michael Albinus
2018-07-21 13:37 ` Eli Zaretskii
2018-07-21 13:56 ` Eli Zaretskii
2018-07-21 13:59 ` Michael Albinus [this message]
2018-07-21 14:21 ` Eli Zaretskii
2018-07-21 14:41 ` Michael Albinus
2018-07-23 9:55 ` Michael Albinus
2018-07-23 15:59 ` Eli Zaretskii
2018-07-23 16:18 ` Michael Albinus
2018-07-23 16:39 ` Eli Zaretskii
2018-07-23 16:52 ` Michael Albinus
2018-07-25 10:48 ` Michael Albinus
2018-07-25 14:47 ` Eli Zaretskii
2018-07-25 15:19 ` Michael Albinus
2018-07-21 10:33 ` Michael Albinus
2018-07-24 17:44 ` Glenn Morris
2018-07-25 11:22 ` Michael Albinus
2018-08-12 16:19 ` Michael Albinus
2018-08-12 23:46 ` Glenn Morris
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=87zhyk1yh2.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=32226@debbugs.gnu.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 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).