Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: PATCH: _hosts, _hostports, _telnet and _socket

X-seq: zsh-workers 7783
From: Tanaka Akira <akr@xxxxxxxxxxx>
To: <zsh-workers@xxxxxxxxxxxxxx>
Subject: Re: PATCH: _hosts, _hostports, _telnet and _socket
Date: 12 Sep 1999 21:26:09 +0900
In-reply-to: "Andrej Borsenkow"'s message of "Sun, 12 Sep 1999 15:26:59 +0400"
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
References: <000001befd11$ba0b0bb0$21c9ca95@xxxxxxxxxxxxxx>

In article <000001befd11$ba0b0bb0$21c9ca95@xxxxxxxxxxxxxx>,
  "Andrej Borsenkow" <Andrej.Borsenkow@xxxxxxxxxxxxxx> 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

Follow-Ups:
- Re: PATCH: _hosts, _hostports, _telnet and _socket
  - From: Tanaka Akira

References:
- RE: PATCH: _hosts, _hostports, _telnet and _socket
  - From: Andrej Borsenkow

Messages sorted by: Reverse Date, Date, Thread, Author