Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Bourne / bash problem
- Date: Sun, 05 Apr 2009 01:27:08 +0900
- From: "Stephen J. Turnbull" <stephen@example.com>
- Subject: Re: [tlug] Bourne / bash problem
- References: <c0f4e2b00904040115k14c6f9dcma0448e9904c8fd2f@example.com> <5ffffd040904040413p5af9e2d6yf82fda9c0397eec1@example.com> <fb85f35d0904040710o3d194d4by95af5a0dec1d8ecd@example.com>
James Lang writes: > #!/bin/bash > echo \ > "word1 `echo # comment line 1...> /dev/null` \ > word2 `echo # comment line 2... > /dev/null` \ > word3 `echo # comment line 3... > /dev/null` \ > word4 `echo # comment line 4... > /dev/null` " Eeewwwwww. We are gonna have to nail that cat door shut!<wink> BTW command \ --option `echo >/dev/null # comment line 1` \ --option `echo >/dev/null # comment line 2` \ --option `echo >/dev/null # comment line 3` \ --option `echo >/dev/null # comment line 4` is a little more readable. This c='echo >/dev/null' command \ --option `eval "$c comment line 1"` \ --option `eval "$c comment line 2"` \ --option `eval "$c comment line 3"` \ --option `eval "$c comment line 4"` might also work (partially tested in zsh) and it's up to you to decide if it's any more readable.
- References:
- [tlug] Bourne / bash problem
- From: Bruno Raoult
- Re: [tlug] Bourne / bash problem
- From: Romeo Theriault
- Re: [tlug] Bourne / bash problem
- From: James Lang
Home | Main Index | Thread Index
- Prev by Date: [tlug] Bourne / bash problem
- Next by Date: Re: [tlug] Bourne / bash problem
- Previous by thread: Re: [tlug] Bourne / bash problem
- Next by thread: Re: [tlug] Bourne / bash problem
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links