From: "David W. Hodgins" <dwhodgins@nomail.afraid.org>
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 17:08:46 -0500 [thread overview]
Message-ID: <op.vo9o4weaa3w0dxdave__49687.4481942088$1294997253$gmane$org@hodgins.homeip.net> (raw)
In-Reply-To: bfd24856-94a9-4b46-b0b7-8c142f5b87f5@z5g2000yqb.googlegroups.com
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.)
next prev parent reply other threads:[~2011-01-13 22:08 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 ` GURU NEEDED : break a command into several lines and comment each line Berthold Höllmann
2011-01-13 22:08 ` David W. Hodgins [this message]
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='op.vo9o4weaa3w0dxdave__49687.4481942088$1294997253$gmane$org@hodgins.homeip.net' \
--to=dwhodgins@nomail.afraid.org \
--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.