From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: PATCH: list units in brackets at the end of completion group descriptions
Date: Fri, 27 Aug 2021 12:10:53 +0000 [thread overview]
Message-ID: <846a355a-d3e8-404a-ac80-4b0f5776d115@www.fastmail.com> (raw)
In-Reply-To: <73806-1630065135.858692@atah.qJX1.Jyyu>
Oliver Kiddle wrote on Fri, 27 Aug 2021 11:52 +00:00:
> There might be some more useful way we might indicate where suffixes can
> be appended to a value to denote units. Completing them after a number
> doesn't really make the options clear before a number has been entered.
> Perhaps an initial slash, e.g. 'timeout (seconds) [5] /ms /us /ns'
This design first says "Input a value in seconds", then the default
value, then goes back to say that other units are possible.
I think we should try for a design with more locality in the provision
of information. For instance, assuming the default unit may also be
specified explicitly:
timeout [5 = 5s]
# This intends to communicate that both «5» and «5s» are valid inputs, and equivalent.
timeout [5] ; hr/[s]/ms/us/ns
# Indicate the default value and default unit separately, indicating all units in a group
I'm sure there are better options than these.
Cheers,
Daniel
next prev parent reply other threads:[~2021-08-27 12:11 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 [this message]
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
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=846a355a-d3e8-404a-ac80-4b0f5776d115@www.fastmail.com \
--to=d.s@daniel.shahaf.name \
--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).