From: Eli Zaretskii <eliz@gnu.org>
To: guile-devel@gnu.org
Subject: Don't return file names with backslashes from search-path
Date: Thu, 14 Aug 2014 18:28:22 +0300 [thread overview]
Message-ID: <831tsjhyzt.fsf@gnu.org> (raw)
This small patch plugs yet another hole through which Guile on Windows
could generate file names with backslashes.
OK to commit?
--- libguile/load.c~2 2014-07-03 09:58:29 +0300
+++ libguile/load.c 2014-08-14 17:28:26 +0300
@@ -657,7 +657,8 @@ search_path (SCM path, SCM filename, SCM
if (stat (buf.buf, stat_buf) == 0
&& ! (stat_buf->st_mode & S_IFDIR))
{
- result = scm_from_locale_string (buf.buf);
+ result =
+ scm_from_locale_string (scm_i_mirror_backslashes (buf.buf));
goto end;
}
}
next reply other threads:[~2014-08-14 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 15:28 Eli Zaretskii [this message]
2014-08-14 22:40 ` Don't return file names with backslashes from search-path Mark H Weaver
2014-08-15 6:50 ` Eli Zaretskii
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831tsjhyzt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=guile-devel@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.
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).