🚀 go-pugleaf

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

bolega <gnuist006@gmail.com> writes:

> Basically, I have spent a few hours experimenting and searching on the
> comp.unix.shell
>
> how to break a command with several switches into more than one line
> AND to be able to put some comment on each line.
>
> #!/bin/bash -xv
>
> command       \ # comment1
>          -sw1 \ # comment2
>          -sw2 \ # comment3
>          arguments

How about=20

=2D----------
#!/bin/bash -xv

COMMAND=3Dcommand       # comment1
COMMAND=3D$COMMAND -sw1 \ # comment2
COMMAND=3D$COMMAND -sw2 \ # comment3
COMMAND=3D$COMMAND arguments

$COMMAND
=2D--------
?

Regards=20
Berthold=20
> One ought to be able to comment every single switch if desired for
> whatever reason.
>
> Bolega
>
>

=2D-=20
A: Weil es die Lesbarkeit des Textes verschlechtert.
F: Warum ist TOFU so schlimm?
A: TOFU
F: Was ist das gr=C3=B6=C3=9Fte =C3=84rgernis im Usenet?

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)

iEYEARECAAYFAk0vcpYACgkQcXJNT6Y4fveF1gCgmw41BZEHgyVzx6gn6HFsS+6W
zBEAn0OyciTF+qNI5tn/ATiOGROw2dW5
=ki9L
-----END PGP SIGNATURE-----
--=-=-=--

On Thu, 13 Jan 2011 16:18:31 -0500, bolega <gnuist006@gmail.com> wrote:

> how to break a command with several switches into more than one line
> AND to be able to put some comment on each line.
> command       \ # comment1
>          -sw1 \ # comment2

Not what you want to hear, but that will not work.  With the above,
the backslash is being used to escape the following space, rather
then a newline, as is required to continue the line.  Even if it
were to work that way, would the next line be considered a continuation
of the command, or of the comment?

Your stuck with

command       \
          -sw1
# comment1
# comment2

Regards, Dave Hodgins

-- 
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

> #!/bin/bash -xv

> command       \ # comment1
>          -sw1 \ # comment2
>          -sw2 \ # comment3
>          arguments

> One ought to be able to comment every single switch if desired for
> whatever reason.

Thanks for the riddle.  Here's a solution:

  command        $(: # comment1
  )        -sw1  $(: # comment2
  )        -sw2  $(: # comment3
  )        arguments


-- Stefan

On Jan 13, 7:12 pm, Stefan Monnier <monn...@iro.umontreal.ca> wrote:
> > #!/bin/bash -xv
> > command       \ # comment1
> >          -sw1 \ # comment2
> >          -sw2 \ # comment3
> >          arguments
> > One ought to be able to comment every single switch if desired for
> > whatever reason.
>
> Thanks for the riddle.  Here's a solution:
>
>   command        $(: # comment1
>   )        -sw1  $(: # comment2
>   )        -sw2  $(: # comment3
>   )        arguments
>
> -- Stefan

thanks to all four of you who replied and solved this problem to a
large extent, building on each other's ideas.

I would have done it by the first method of concatenating or pipes
into a sed which replaced end by the next and # can be placed after
pipes. the string then fed into a bash.

Stefan, whats the purpose of the colon ? it works without colon also.
Is it subshell or some environment import ? like the colon which can
substitute the #!/bin/bash on the top ?

Bolega

bolega <gnuist006@gmail.com> writes:

> On Jan 13, 7:12�pm, Stefan Monnier <monn...@iro.umontreal.ca> wrote:
>> > #!/bin/bash -xv
>> > command � � � \ # comment1
>> > � � � � �-sw1 \ # comment2
>> > � � � � �-sw2 \ # comment3
>> > � � � � �arguments
>> > One ought to be able to comment every single switch if desired for
>> > whatever reason.
>>
>> Thanks for the riddle. �Here's a solution:
>>
>> � command � � � �$(: # comment1
>> � ) � � � �-sw1 �$(: # comment2
>> � ) � � � �-sw2 �$(: # comment3
>> � ) � � � �arguments
>>
>> -- Stefan
>
> thanks to all four of you who replied and solved this problem to a
> large extent, building on each other's ideas.
>
> I would have done it by the first method of concatenating or pipes
> into a sed which replaced end by the next and # can be placed after
> pipes. the string then fed into a bash.
>
> Stefan, whats the purpose of the colon ? it works without colon also.
> Is it subshell or some environment import ? like the colon which can
> substitute the #!/bin/bash on the top ?

The colon is a built-in command equivalent to true.


The syntax specified for $( ... ) (in man bash) is:

       $(command)

so a command is expected.  The shortest command doing nothing is :.

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.