public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.org>
To: Mark Wielaard <mark@klomp.org>
Cc: debugedit@sourceware.org
Subject: Re: [PATCH] find-debuginfo.sh: Add --help, --version and man page.
Date: Fri, 30 Apr 2021 15:19:08 +0300	[thread overview]
Message-ID: <20210430121907.GF5477@altlinux.org> (raw)
In-Reply-To: <93393113c5d29d9861ef6ee5105062cfb3447b23.camel@klomp.org>

Hi Mark,

On Fri, Apr 30, 2021 at 02:10:14PM +0200, Mark Wielaard wrote:
> Hi Dmitry,
> 
> On Fri, 2021-04-30 at 02:06 +0300, Dmitry V. Levin wrote:
> > I suggest to use "cat" instead of multiple echoes, e.g.
> > 
> >   cat <<-'EOF'
> > 	Usage: find-debuginfo.sh [OPTION]... [builddir]
> > 	automagically generates debug info and file lists
> > 
> > 	Options:
> > 	[...]
> > 	--unique-debug-src-base "%{name}-%{VERSION}-
> > %{RELEASE}.%{_arch}")
> > 
> > 	All file names in switches are relative to builddir ('.' if not
> > given).
> >   EOF
> 
> Yes, that is obviously much nicer.

It would look even nicer if EOF was quoted, e.g. 'EOF'.
From bash manual page:
"If any part of word is quoted, the delimiter is the result of quote
removal on word, and the lines in the here-document are not expanded."

[...]
> +--unique-debug-src-base \"%{name}-%{VERSION}-%{RELEASE}.%{_arch}\")

I suggest to quote EOF once and forget about quoting anything in the whole
text.


-- 
ldv

  reply	other threads:[~2021-04-30 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 22:46 Mark Wielaard
2021-04-29 23:06 ` Dmitry V. Levin
2021-04-30 12:10   ` Mark Wielaard
2021-04-30 12:19     ` Dmitry V. Levin [this message]
2021-04-30 12:37       ` Mark Wielaard

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=20210430121907.GF5477@altlinux.org \
    --to=ldv@altlinux.org \
    --cc=debugedit@sourceware.org \
    --cc=mark@klomp.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).