From: bhoel@despammed.com (Berthold Höllmann)
To: help-gnu-emacs@gnu.org
Subject: Re: GURU NEEDED : break a command into several lines and comment each line
Date: Thu, 13 Jan 2011 22:45:20 +0100 [thread overview]
Message-ID: <87wrm8scjz.fsf__49823.6947380521$1294997219$gmane$org@pchoel.xn--hllmanns-n4a.de> (raw)
In-Reply-To: bfd24856-94a9-4b46-b0b7-8c142f5b87f5@z5g2000yqb.googlegroups.com
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
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
-----------
#!/bin/bash -xv
COMMAND=command # comment1
COMMAND=$COMMAND -sw1 \ # comment2
COMMAND=$COMMAND -sw2 \ # comment3
COMMAND=$COMMAND arguments
$COMMAND
---------
?
Regards
Berthold
> One ought to be able to comment every single switch if desired for
> whatever reason.
>
> Bolega
>
>
--
A: Weil es die Lesbarkeit des Textes verschlechtert.
F: Warum ist TOFU so schlimm?
A: TOFU
F: Was ist das größte Ärgernis im Usenet?
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next parent reply other threads:[~2011-01-13 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bfd24856-94a9-4b46-b0b7-8c142f5b87f5@z5g2000yqb.googlegroups.com>
2011-01-13 21:45 ` Berthold Höllmann [this message]
2011-01-13 22:08 ` GURU NEEDED : break a command into several lines and comment each line David W. Hodgins
2011-01-13 22:46 ` suvayu ali
2011-01-13 22:47 ` Pascal J. Bourguignon
2011-01-14 3:12 ` Stefan Monnier
[not found] ` <jwvaaj4b2sb.fsf-monnier+gnu.emacs.help@gnu.org>
2011-01-14 6:28 ` bolega
2011-01-14 17:41 ` Pascal J. Bourguignon
2011-01-13 21:18 bolega
2011-01-14 8:07 ` Oleksandr Gavenko
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='87wrm8scjz.fsf__49823.6947380521$1294997219$gmane$org@pchoel.xn--hllmanns-n4a.de' \
--to=bhoel@despammed.com \
--cc=berthold@xn--hllmanns-n4a.de \
--cc=help-gnu-emacs@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.