Re: BASH Programming: spaces ignored

From: Kenny McCormack (gazelle_at_yin.interaccess.com)
Date: 05/30/05

  • Next message: Kamal R. Prasad: "Re: getting pathname from descriptor" 
    Date: Mon, 30 May 2005 16:53:41 GMT

    In article <yw1xwtpgkbfa.fsf@ford.inprovide.com>,
    =?iso-8859-1?q?M=E5ns_Rullg=E5rd?= <mru@inprovide.com> wrote:
    ...
    >Always quote string with variables in them, no exceptions. In this

    bash$ foo="echo this is a test"
    bash$ $foo that proves that there are exceptions to every rule
    this is a test that proves that there are exceptions to every rule
    bash$

  • Next message: Kamal R. Prasad: "Re: getting pathname from descriptor"

    Relevant Pages

    • Re: BASH Programming: spaces ignored
      ... >>Always quote string with variables in them, no exceptions. ... > bash$ $foo that proves that there are exceptions to every rule ...
      (comp.unix.programmer)
    • Re: Compiling C++ modules
      ... Without exceptions (which are fragile in a kernel), the former can't return an error instead of initializing the Foo. ... Foo item1, item2; ...
      (Linux-Kernel)
    • Re: Compiling C++ modules
      ... Without exceptions (which are fragile in a kernel), the former can't return an error instead of initializing the Foo. ... Foo item1, item2; ...
      (Linux-Kernel)
    • Re: Environment bug in Bash?
      ... I tried in in bash, ksh, and zsh, all with the same ... env foo=bar echo $foo ... A "simple command" is a sequence of optional variable assignments ... and redirections, ...
      (comp.unix.shell)
    • Re: Environment bug in Bash?
      ... Thinking it might be because echo is ... I tried in in bash, ksh, and zsh, all with the same ... env foo=bar echo $foo ... So, yes, I think you hit a bug in bash 2.x 3.x! ...
      (comp.unix.shell)