zsh-workers
 help / color / mirror / code / Atom feed
From: Eitan Adler <lists@eitanadler.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] _powerd: add -M and -m options
Date: Tue, 5 Jun 2018 16:13:26 -0700	[thread overview]
Message-ID: <CAF6rxg=v_uHKJRFpa8X9xghx0Tpe83XLf1wfvzS_bt8T+CLLkw@mail.gmail.com> (raw)
In-Reply-To: <4030.1527448571@thecus>

On 27 May 2018 at 12:16, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> Eitan Adler wrote:
>> allowed values, limiting to numbers is good enough for now.
>>
>> Signed-off-by: Eitan Adler <lists@eitanadler.com>
>> ---
>>  Completion/BSD/Command/_powerd | 2 ++
>>  1 file changed, 2 insertions(+)
>>
>> diff --git a/Completion/BSD/Command/_powerd b/Completion/BSD/Command/_powerd
>> index 18a9fb437..88d7c401b 100644
>> --- a/Completion/BSD/Command/_powerd
>> +++ b/Completion/BSD/Command/_powerd
>> @@ -6,6 +6,8 @@ _arguments -s \
>>      "-a[mode to use while on AC power]:mode:($powerd_mode)" \
>>      "-b[mode to use while on battery power]:mode:($powerd_mode)" \
>>      '-i[CPU idle percent level when begin to degrade performance]:percent:' \
>> +    "-m[maximum frequency to throttle down to]:freq: :_guard '[0-9]#' 'numeric value'" \
>> +    "-M[maximum frequency to throttle up to]:freq: :_guard '[0-9]#' 'numeric value'" \
>
> The syntax here isn't right as the : : in the middle should not be
> there. The second argument after -m or -M will give you the whole _guard
> bit as a description.
>
> What did you intend as the description? Abbreviating the word
> "frequency" to "freq" is fairly pointless and "numeric value" is not
> entirely helpful. "frequency" is better. Better still, include the units
> in round brackets and the default value in square brackets.

I copied this from the man page.

> _guard is not necessary here. _guard solves a particular problem
> that occurs when something that can't be completed but for which a
> message is useful is completed alongside something for which there are
> matches. After -m, only arguments to -m are relevant so _guard isn't
> needed.


Makes sense.  I copied this from another completer. This also explains
why it didn't work exactly the way I expected :)


>
>   '-m[maximum frequency to throttle down to]:frequency (MHz)'

New patch coming up shortly.


-- 
Eitan Adler


  reply	other threads:[~2018-06-05 23:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26  7:08 Eitan Adler
2018-05-27 19:16 ` Oliver Kiddle
2018-06-05 23:13   ` Eitan Adler [this message]
2018-06-05 22:11 Eitan Adler

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='CAF6rxg=v_uHKJRFpa8X9xghx0Tpe83XLf1wfvzS_bt8T+CLLkw@mail.gmail.com' \
    --to=lists@eitanadler.com \
    --cc=okiddle@yahoo.co.uk \
    --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).