From: "Mikael Magnusson" <mikachu@gmail.com>
To: zsh-workers <zsh-workers@sunsite.dk>
Subject: oggenc tabcompletion itch
Date: Mon, 24 Sep 2007 22:27:32 +0200 [thread overview]
Message-ID: <237967ef0709241327u1d6fc7ffm2400e05e1478dc16@mail.gmail.com> (raw)
The options completion for oggenc wants options like -q 3 with a
space, but oggenc accepts -q3 without a space happily too. Being lazy
i usually type -q3 without the space, but then oggenc -q3 <tab>
completes {1..10} instead of filenames, which is my issue.
Is there any easy way to modify the _vorbis completion file to fix
this? (probably also applies to all the other options, though i use
them more rarely).
the line for -q in _vorbis looks like
'(-q --quality)'{-q,--quality=}'[set encoding
quality]:quality:(0 1 2 3 4 5 6 7 8 9 10)' \
and is sent to _arguments -s
--
Mikael Magnusson
next reply other threads:[~2007-09-24 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 20:27 Mikael Magnusson [this message]
2007-09-25 13:44 ` Oliver Kiddle
2007-09-25 14:30 ` [patch] " Mikael Magnusson
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=237967ef0709241327u1d6fc7ffm2400e05e1478dc16@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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).