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: Mon, 28 Jan 2013 20:30:06 +0100	[thread overview]
Message-ID: <1359401406.2927.49.camel@belkin4> (raw)
In-Reply-To: <CAB9SyzRi7gL56xsFdaL5AvAy3y9rmtW=-wic0gwjvNiNW+suPQ@mail.gmail.com>

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

El lun, 28-01-2013 a las 14:37 +0800, Ben de Groot escribió:
> On 28 January 2013 12:37, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Sunday 27 January 2013 13:21:27 Pacho Ramos wrote:
> >> The problem is that it doesn't work so well. If I have the following at
> >> src_prepare (for example):
> >> src_prepare() {
> >>         DOC_CONTENTS="You must create a symlink rom /etc/splash/tuxonice
> >> to the theme you want tuxonice to use, e.g.: \n
> >>                       # ln -sfn /etc/splash/emergence /etc/splash/tuxonice \n"
> >> ...
> >>
> >> and I handle ${DOC_CONTENTS} with quotes, it will end writing that tabs
> >> also in generated file as the contents of the variable will be put
> >> as-is. On the other hand, if I don't put it between quotes
> >
> > forcibly normalizing whitespace for all callers is wrong imo (as is sending it
> > through `fmt`).  if the caller gave you content to write, it should write it.
> > if the caller didn't want tabs, it shouldn't have used it in the first place.
> > -mike
> 
> I've started using this eclass, but with README files, not the variable,
> because this is currently the only way I can make sure it honours my
> formatting.
> 

Couldn't it be covered if "echo -e" was used (even with fmt) and you,
then, control formatting with some of the sequences it allows (they are
shown in its man page)?

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

  reply	other threads:[~2013-01-28 19:30 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 [this message]
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
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=1359401406.2927.49.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