public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH setup 0/3] Setup replacement for incver_ifdep
Date: Thu, 28 Jan 2016 20:22:00 -0000	[thread overview]
Message-ID: <56AA787A.9080503@redhat.com> (raw)
In-Reply-To: <56AA7755.8060801@cornell.edu>

[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]

On 01/28/2016 01:17 PM, Ken Brown wrote:
>>>    install-info $f /usr/share/info/dir ||
>>>    install-info --entry="* $$f ($f): $$f" $$f /usr/share/info/dir
>>>
>>> First, what do those double dollar signs mean?
>>
>> If this is from a Makefile snippet, it says that $f is a make variable,
>> while $$ turns into a literal $f for the shell that make invokes

> 
> It's not a Makefile snippet; it's a snippet from a bash shell script.  Here's more context:
> 
>   for f in /usr/share/info/*; do
>       case "$f" in
>           *\**)
>               ;;
>           */dir|*/dir.info*)
>               ;;
>           *-[0123456789]*)
>               ;;
>           *)
>               install-info $f /usr/share/info/dir ||
>               install-info --entry="* $$f ($f): $$f" $$f /usr/share/info/dir
>               ;;
>       esac
>   done
> 
> It looks to me like all those double dollar signs will just get expanded to the PID of the bash process, so that the second install-info command is nonsense.  But maybe I'm missing something.

Oooh, scary. Yeah, it looks like utter nonsense, as that would indeed
give the PID of bash followed by a literal f, but who wants to look up
info of '1234f'?  I wonder if someone writing the script copied
incorrectly from a Makefile?

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-01-28 20:22 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 15:53 Jon Turney
2015-09-22 15:53 ` [PATCH setup 3/3] Add support for 'trigger:' lines in setup.ini Jon Turney
2015-09-22 15:53 ` [PATCH setup 2/3] Remove unfinished, unused support for 'autodep:' " Jon Turney
2015-09-22 15:54 ` [PATCH setup 1/3] Remove unused regex code Jon Turney
2015-09-22 17:33 ` [PATCH setup 0/3] Setup replacement for incver_ifdep Achim Gratz
2015-09-23 17:17   ` Jon Turney
2015-09-23 18:09     ` Achim Gratz
2015-10-12 13:16 ` Jon Turney
2015-10-12 17:38   ` Achim Gratz
2015-10-15 13:18     ` Jon Turney
2015-10-15 18:01       ` Achim Gratz
2015-10-19 15:41         ` Corinna Vinschen
2015-10-19 17:21           ` Achim Gratz
2015-10-20 10:21             ` Corinna Vinschen
2015-11-23 15:14               ` Jon Turney
2015-11-23 18:54                 ` Achim Gratz
2015-11-24 16:59                   ` Jon Turney
2015-11-24 18:44                     ` Achim Gratz
2015-11-26 10:11                       ` Corinna Vinschen
2015-11-26 18:12                         ` Achim Gratz
2016-01-28 17:33                         ` Jon Turney
2016-01-28 18:06                           ` Achim Gratz
2016-01-28 18:41                             ` [GOLDSTAR] " Corinna Vinschen
2016-01-29 16:37                               ` Andrew Schulman
2016-01-28 18:42                           ` Ken Brown
2016-01-28 20:06                             ` Eric Blake
2016-01-28 20:17                               ` Ken Brown
2016-01-28 20:22                                 ` Eric Blake [this message]
2016-01-29 14:22                                   ` Jon Turney
2016-01-29 14:53                                     ` Ken Brown
2016-01-29 19:17                                       ` Achim Gratz
2016-01-29 21:34                                         ` Ken Brown
2016-02-06 14:29                                       ` Ken Brown
2016-02-06 15:31                                         ` Jon Turney
2016-02-06 15:52                                           ` Jon Turney
2015-11-23 15:14         ` Jon Turney
2015-10-19 15:33   ` [GOLDSTAR] " Corinna Vinschen
2015-10-19 21:06     ` Andrew Schulman

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

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

  git send-email \
    --in-reply-to=56AA787A.9080503@redhat.com \
    --to=eblake@redhat.com \
    --cc=cygwin-apps@cygwin.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.
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).