From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: long/short options
Date: Thu, 12 Jul 2001 20:01:50 +0400 [thread overview]
Message-ID: <000601c10aeb$f5cdebb0$21c9ca95@mow.siemens.ru> (raw)
mount under Cygwin is simple, but every option has a long and short form.
Using exclusions I can prevent both to be on command line, but listing looks
somewhat ugly:
(tty1)% mount -s --binary
Completing Windows path
Completing option
--binary -- Unix line endings LF
--cygwin-executable -- all files under mountpoint are cygwin executables
--executable -- all files under mountpoint are executables
--force -- be silent
--text -- (default) DOS line endings CR-LF
-X -- all files under mountpoint are cygwin executables
-b -- Unix line endings LF
-f -- be silent
-t -- (default) DOS line endings CR-LF
-x -- all files under mountpoint are executables
What I'd really like is something like
-b, --binary -- Unix line endings
...
Or do I miss something and this is already possible?
Another question is, in case of
'(-c -i --import-old-mounts -p --show-cygdrive-prefix)--change-cygdrive-
prefix[cygdrive prefix]:cygdrive prefix (POSIX path):_files -/'
I get something like
(tty1)% mount --change-cygdrive-prefix --
No matches for: `cygdrive prefix (POSIX path)' or `file'
^^^^^^^^^
How can I prevent the last part (I want description only from option).
Oh, and is _files /*(/) the right way to complete absolute pathnames? :-)
-andrej
next reply other threads:[~2001-07-12 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-12 16:01 Andrej Borsenkow [this message]
2001-07-13 8:07 ` Sven Wischnowsky
2001-07-13 17:01 ` Bart Schaefer
2001-07-16 7:14 ` Sven Wischnowsky
2001-07-18 13:07 ` PATCH: " Sven Wischnowsky
2001-07-18 13:46 ` Andrej Borsenkow
2001-07-18 13:51 ` Sven Wischnowsky
2001-07-18 13:59 ` Andrej Borsenkow
2001-07-18 17:20 ` Oliver Kiddle
2001-07-19 8:36 ` Sven Wischnowsky
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='000601c10aeb$f5cdebb0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--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).