From: Eric Bavier <ericbavier@openmailbox.org>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: octave: Add fftw, arpack, and glu inputs.
Date: Sun, 10 May 2015 14:39:04 -0500 [thread overview]
Message-ID: <20150510143904.636b0b8c@PocketWee> (raw)
In-Reply-To: <87sib5q591.fsf@netris.org>
On Sat, 09 May 2015 08:56:10 -0400
Mark H Weaver <mhw@netris.org> wrote:
> Eric Bavier <ericbavier@openmailbox.org> writes:
>
> > @@ -411,11 +416,11 @@ extremely large and complex data collections.")
> > "/bin/sh"))))
> > (home-page "http://www.gnu.org/software/octave/")
> > (synopsis "High-level language for numerical computation")
> > - (description "GNU Octave is a high-level interpreted language that is specialized
> > -for numerical computations. It can be used for both linear and non-linear
> > -applications and it provides great support for visualizing results. Work may
> > -be performed both at the interactive command-line as well as via script
> > -files.")
> > + (description "GNU Octave is a high-level interpreted language that is
> > +specialized for numerical computations. It can be used for both linear and
> > +non-linear applications and it provides great support for visualizing results.
> > +Work may be performed both at the interactive command-line as well as via
> > +script files.")
>
> As you have it now, the first line of the string will actually be much
> shorter than the others.
In what situations is this an actual issue? The recutils output will
re-wrap lines already (e.g. 'guix search' and 'guix package --show').
`~Eric
next prev parent reply other threads:[~2015-05-10 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 21:27 [PATCH] gnu: octave: Add fftw, arpack, and glu inputs Eric Bavier
2015-05-09 12:56 ` Mark H Weaver
2015-05-10 19:39 ` Eric Bavier [this message]
2015-05-10 19:46 ` Mark H Weaver
2015-05-11 3:17 ` Eric Bavier
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150510143904.636b0b8c@PocketWee \
--to=ericbavier@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).