unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 56712@debbugs.gnu.org
Subject: bug#56712: 29.0.50; x-dnd-tests-do-direct-save fails on Cygwin
Date: Sun, 24 Jul 2022 21:42:26 -0400	[thread overview]
Message-ID: <0669c533-4f60-50c5-21c1-ea779dedcee2@cornell.edu> (raw)
In-Reply-To: <87wnc2ypgb.fsf@yahoo.com>

On 7/24/2022 9:02 PM, Po Lu wrote:
> Ken Brown <kbrown@cornell.edu> writes:
> 
>> On 7/24/2022 9:33 AM, Po Lu wrote:
>>> Now done.  Ken, could you please re-run the test and show the detailed
>>> error that is signalled?
>>
>> Thanks.  The error is now clear:
>>
>> Test x-dnd-tests-do-direct-save condition:
>>      (file-missing "Opening output file" "No such file or directory"
>>      "//tmp/x-dnd-testvZQUCZ/x-dnd-test-targetKiqqPT")
>>
>> According to POSIX, the meaning of exactly 2 slashes at the beginning
>> of a path name is system dependent.  On Cygwin it's interpreted as a
>> UNC path.  That explains the error, but I don't immediately see where
>> the extra slash comes from.  (There are plenty of references to UNC
>> paths and to "file://" and "file:///" in dnd.el, so maybe there's some
>> code in there that incorrectly assumes that MS-Windows is the only
>> platform on which exactly 2 initial slashes has a special meaning.)
>>
>> Ken
> 
> Unless system-type can be windows-nt on Cygwin, I don't think that can
> happen.

No, system-type is cygwin on Cygwin.

>  I will look into this, thanks.

Thanks.

Ken





  reply	other threads:[~2022-07-25  1:42 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 [this message]
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
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=0669c533-4f60-50c5-21c1-ea779dedcee2@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=56712@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --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).