From: Tanaka Akira <akr@jaist.ac.jp>
To: <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: _hosts, _hostports, _telnet and _socket
Date: 12 Sep 1999 21:26:09 +0900 [thread overview]
Message-ID: <rsqvh9g8gf2.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of "Sun, 12 Sep 1999 15:26:59 +0400"
In article <000001befd11$ba0b0bb0$21c9ca95@mow.siemens.ru>,
"Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru> writes:
> Again, the same old question - *what* telnet? Ours does not understand any of
> the options you list (more, than -8, host, port).
`_telnet' is based on 4.4BSD (NetBSD 1.4).
And most of options are supported by Solaris 7 and Debian.
Also, I know that SunOS 4.1.4 doesn't support options at all.
> If Linux telnet is so smart - should this be put in Linux then?
I agree that `telnet' has many variants and `_telnet' should complete
only valid options of `telnet' if it is possible.
Extracting existence of options from the help text is better way. But
the help text of telnet is not suitable for `_arguments'.
Hm. Maybe `_arguments' should take an argument for a function to parse
a help text.
--
Tanaka Akira
next prev parent reply other threads:[~1999-09-12 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-12 0:00 Tanaka Akira
1999-09-12 2:20 ` Bart Schaefer
1999-09-12 3:36 ` Tanaka Akira
1999-09-12 21:25 ` Adam Spiers
1999-09-13 14:06 ` Clint Adams
1999-09-13 9:09 ` Peter Stephenson
1999-09-13 18:20 ` Tanaka Akira
1999-09-14 14:25 ` Clint Adams
1999-09-12 11:26 ` Andrej Borsenkow
1999-09-12 12:26 ` Tanaka Akira [this message]
1999-09-17 0:57 ` Tanaka Akira
1999-09-19 0:49 ` Bart Schaefer
1999-09-14 8:34 Sven Wischnowsky
1999-09-15 12:56 ` Tanaka Akira
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=rsqvh9g8gf2.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--cc=zsh-workers@sunsite.auc.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).