unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: luangruo@yahoo.com, 56712@debbugs.gnu.org
Subject: bug#56712: 29.0.50; x-dnd-tests-do-direct-save fails on Cygwin
Date: Mon, 25 Jul 2022 19:53:58 +0300	[thread overview]
Message-ID: <83ilnldtg9.fsf@gnu.org> (raw)
In-Reply-To: <193b54c8-c047-bb47-7430-f3719ac1e100@cornell.edu> (message from Ken Brown on Mon, 25 Jul 2022 12:24:21 -0400)

> Date: Mon, 25 Jul 2022 12:24:21 -0400
> Cc: Eli Zaretskii <eliz@gnu.org>, 56712-done@debbugs.gnu.org
> From: Ken Brown <kbrown@cornell.edu>
> 
> On 7/24/2022 10:10 PM, Po Lu wrote:
> > It's a bug in the test, which I (hopefully) fixed.  Please give it
> > another try.
> 
> It's fixed, thanks.  So I guessed right about there being a "file:///" that 
> should have been "file://", but I didn't see it staring me in the face in the 
> test file!

FTR: if that test should ever run on native MS-Windows, we'd need that
third slash, because file://c:/foo/bar is not valid on Windows, you
must say file:///c:/foo/bar.

So from my POV, it is best to make that code system-dependent, with
windows-nt using 3 slashes, not 2.





  reply	other threads:[~2022-07-25 16:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 21:10 bug#56712: 29.0.50; x-dnd-tests-do-direct-save fails on Cygwin Ken Brown
2022-07-23  1:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23 17:30   ` Ken Brown
2022-07-23 17:41     ` Ken Brown
2022-07-24  2:26     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-24  5:50       ` Eli Zaretskii
2022-07-24  7:23         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-24  7:42           ` Michael Albinus
2022-07-24  8:55           ` Eli Zaretskii
2022-07-24 10:55             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-24 13:33             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-24 15:40               ` Ken Brown
2022-07-25  1:02                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-25  1:42                   ` Ken Brown
2022-07-25  2:10                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-25 16:24                       ` Ken Brown
2022-07-25 16:53                         ` Eli Zaretskii [this message]
2022-07-26  2:10                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-26  2:38                             ` Eli Zaretskii
2022-07-26  2:52                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83ilnldtg9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=56712@debbugs.gnu.org \
    --cc=kbrown@cornell.edu \
    --cc=luangruo@yahoo.com \
    /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).