git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Joachim Durchholz <jo@durchholz.org>
To: git@vger.kernel.org
Subject: Re: problem with backslash in directory name
Date: Fri, 7 Apr 2017 10:24:14 +0200	[thread overview]
Message-ID: <06bad45d-ad0b-aafe-47e8-172e44ab69cc@durchholz.org> (raw)
In-Reply-To: <20170407063057.yjbqavu4uiipslpc@sigill.intra.peff.net>

Am 07.04.2017 um 08:30 schrieb Jeff King:
> Probably it's "read" which does backslash expansion, but nothing else.
> Just grepping git-submodule.sh, some of the "read" calls should probably
> be "read -r"

http://wiki.bash-hackers.org/commands/builtin/read has this to say:

> Essentially all you need to know about -r is to ALWAYS use it. The
 > exact behavior you get without -r is completely useless even for weird
 > purposes. It basically allows the escaping of input which matches
 > something in IFS, and also escapes line continuations. It's explained
 > pretty well in the POSIX read[1] spec.

[1] 
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/read.html#tag_20_109

(That's the kind of stuff that makes me shy of using shell scripts - 
always yet another surprise in waiting...)

  reply	other threads:[~2017-04-07  8:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07  6:12 problem with backslash in directory name Joachim Durchholz
2017-04-07  6:30 ` Jeff King
2017-04-07  8:24   ` Joachim Durchholz [this message]
2017-04-07  8:40   ` Joachim Durchholz
2017-04-07 16:53   ` Brandon Williams
2017-04-07 16:55     ` Stefan Beller
2017-04-07 17:23       ` [PATCH] submodule: prevent backslash expantion in submodule names Brandon Williams
2017-04-07 17:35         ` Joachim Durchholz
2017-04-08 10:59         ` Jeff King
2017-04-08 20:32           ` Joachim Durchholz
2017-04-17  3:09           ` Junio C Hamano

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=06bad45d-ad0b-aafe-47e8-172e44ab69cc@durchholz.org \
    --to=jo@durchholz.org \
    --cc=git@vger.kernel.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://80x24.org/mirrors/git.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).