public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: readme.gentoo.eclass: use echo -e instead of plain echo (Was: Re: [gentoo-dev] readme.gentoo.eclass: Add a DISABLE_AUTOFORMATTING variable=
Date: Fri, 01 Feb 2013 21:34:48 +0100	[thread overview]
Message-ID: <1359750888.26423.16.camel@belkin4> (raw)
In-Reply-To: <CAB9SyzTA799FY=SUO31=Mpd=RCmD5wedoxru7hwDbpfHa8vPtQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

El vie, 01-02-2013 a las 17:55 +0800, Ben de Groot escribió:
> On 1 February 2013 02:59, Pacho Ramos <pacho@gentoo.org> wrote:
> > El dom, 27-01-2013 a las 18:47 +0100, Pacho Ramos escribió:
> >> El dom, 27-01-2013 a las 15:00 +0100, Pacho Ramos escribió:
> >> > Currently, when people uses DOC_CONTENTS variable to place their desired
> >> > messages, they are automatically reformatted by "fmt" to get proper
> >> > messages (for example, splitting long lines).
> >> >
> >> > But, in some cases, may be useful to disable this behavior and respect
> >> > strictly how DOC_CONTENTS was formatted, for example in that kind of
> >> > messages telling people to run a command and, then, requiring a new line
> >> > to be used. This can also be useful to append extra information to
> >> > DOC_CONTENTS when, for example, additional info is needed when enabling
> >> > a USE flag.
> >> >
> >> >
> >>
> >> Well, after reading man echo I see all this is not needed, I simply need
> >> to use echo -e to get it understand "\n" to create new lines
> >>
> >> New patch attached
> >
> > This will add an option to disabling autoformatting to let people get
> > their doc_contents 100% respected if they want
> 
> How about using an "as-is" argument to readme.gentoo_create_doc?
> That would be more concise. :-)
> 

I have no problem on either solution... but don't have time just now to
work on a patch to achieve it, if you have a bit time, I would really
appreciate :)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-02-01 20:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-27 14:00 [gentoo-dev] readme.gentoo.eclass: Add a DISABLE_AUTOFORMATTING variable Pacho Ramos
2013-01-27 17:47 ` readme.gentoo.eclass: use echo -e instead of plain echo (Was: Re: [gentoo-dev] readme.gentoo.eclass: Add a DISABLE_AUTOFORMATTING variable= Pacho Ramos
2013-01-27 18:05   ` Mike Frysinger
2013-01-27 18:21     ` Pacho Ramos
2013-01-28  4:37       ` Mike Frysinger
2013-01-28  6:37         ` Ben de Groot
2013-01-28 19:30           ` Pacho Ramos
2013-01-29  2:28             ` Mike Frysinger
2013-01-29  6:03             ` Ben de Groot
2013-01-29 21:47               ` Pacho Ramos
2013-01-29 22:06                 ` Michał Górny
2013-01-30  8:27                 ` Ralph Sennhauser
2013-01-30 13:24                 ` Ben de Groot
2013-01-30 18:43                   ` Pacho Ramos
2013-01-31 18:59   ` Pacho Ramos
2013-02-01  9:55     ` Ben de Groot
2013-02-01 11:07       ` Michael Weber
2013-02-01 20:34       ` Pacho Ramos [this message]
2013-02-02 11:04         ` Pacho Ramos
2013-01-31 15:22 ` [gentoo-dev] readme.gentoo.eclass: Add a DISABLE_AUTOFORMATTING variable Dan Douglas
2013-01-31 20:43   ` [gentoo-dev] " Duncan

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=1359750888.26423.16.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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