zsh-workers
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@zsh.org>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Zsh workers <zsh-workers@zsh.org>
Subject: Re: PATCH: list units in brackets at the end of completion group descriptions
Date: Fri, 27 Aug 2021 18:14:35 +0200	[thread overview]
Message-ID: <77868-1630080875.200330@ENNy.eMSK.zAao> (raw)
In-Reply-To: <CAHYJk3R34nVzupAK9qDtCvzFYf+7YBjxqiMXVaz5f05HxX0nrw@mail.gmail.com>

Mikael Magnusson wrote:
> > -      '3:upload limit in KB/s:(unlimited)'

> some inconsistencies here with kilos and bytes, it should always be kB
> although I doubt anyone would ever think kilobits or kelvinbytes are
> refered to in these contexts. The urpmi one should probably be spelled
> out as bytes/s or B/s though (somehow it feels less clear to me
> without the kilo). Perhaps worth a separate batch cleanup.

I intentionally left them exactly as they were before. That should
be done as a separate cleanup but is not really something I'm keen
to tackle because you'd have to look into each programme to find out
whether it is bits or bytes and kilo or kibi. I'd guess there are plenty
more of these too.

For bandwidth, bits rather than bytes is actually fairly likely.

Oliver


      reply	other threads:[~2021-08-27 16:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27 11:52 Oliver Kiddle
2021-08-27 12:10 ` Daniel Shahaf
2021-10-27 20:51   ` Oliver Kiddle
2021-11-02 12:08     ` Jun T
2021-11-07  1:16       ` Oliver Kiddle
2021-11-08 10:56         ` Jun T
2021-11-10 23:08           ` PATCH: zformat (was list units in brackets at the end of completion group descriptions) Oliver Kiddle
2021-11-22 21:24           ` PATCH: list units in brackets at the end of completion group descriptions Oliver Kiddle
2021-12-01  3:27             ` Daniel Shahaf
2021-08-27 14:44 ` Mikael Magnusson
2021-08-27 16:14   ` Oliver Kiddle [this message]

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=77868-1630080875.200330@ENNy.eMSK.zAao \
    --to=opk@zsh.org \
    --cc=mikachu@gmail.com \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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).