9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hoc output format
Date: Wed, 12 May 2010 11:06:20 -0700	[thread overview]
Message-ID: <AANLkTin7F2mT7yhs4VQATcvoIsKMDjsYwDzQX2sN6zyV@mail.gmail.com> (raw)
In-Reply-To: <op.vck9apb3hipq0d@santucco.avp.ru>

I've found that awk(1) is more useful
(rather, more powerful) for doing
programmed computations (number
crunching, etc.), where hoc(1) is
more of a convenience for basic
calculations.


Best,
ak

On Wed, May 12, 2010 at 3:41 AM, Alexander Sychev <santucco@gmail.com> wrote:
> Hello!
>
> IFAIK, hoc(1) hasn't got such possibility.
> awk(1) can help:
>
> $ hoc -e PI | awk '{printf "%2.2f", $0}'
> 3.14
>
> On Wed, 12 May 2010 14:24:57 +0400, Rudolf Sykora <rudolf.sykora@gmail.com>
> wrote:
>
>> Hello everyone,
>>
>> is there any way to control the output format of hoc(1), i.e. e.g. the
>> number of decimal places printed?
>>
>> Thanks
>> Ruda
>
>
> --
> Best regards,
>  santucco
>
>



  reply	other threads:[~2010-05-12 18:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 10:24 Rudolf Sykora
2010-05-12 10:41 ` Alexander Sychev
2010-05-12 18:06   ` Akshat Kumar [this message]
2010-05-13  7:51     ` Alexander Sychev
2010-05-13 13:24       ` erik quanstrom
2010-05-13 14:06         ` Alexander Sychev
2010-05-13 14:23           ` erik quanstrom
2010-05-13 15:04             ` Ethan Grammatikidis
2010-05-13 15:09             ` Gorka Guardiola
2010-05-13 15:37               ` erik quanstrom
2010-05-13 15:16             ` roger peppe
2010-05-13 15:31               ` erik quanstrom
2010-05-13 15:53                 ` roger peppe
2010-05-13 16:06                   ` erik quanstrom
2010-05-13 16:16                     ` roger peppe
2010-05-13 15:54               ` Ethan Grammatikidis
2010-05-13 16:08                 ` roger peppe
2010-05-13 15:20             ` Rudolf Sykora

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=AANLkTin7F2mT7yhs4VQATcvoIsKMDjsYwDzQX2sN6zyV@mail.gmail.com \
    --to=akumar@mail.nanosouffle.net \
    --cc=9fans@9fans.net \
    /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 NNTP newsgroup(s).