zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ifh.de>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: _hosts, _hostports, _telnet and _socket
Date: Mon, 13 Sep 1999 11:09:11 +0200	[thread overview]
Message-ID: <199909130909.LAA14546@paris.ifh.de> (raw)
In-Reply-To: "Tanaka Akira"'s message of "12 Sep 1999 12:36:25 +0900." <rsqemg4kdhi.fsf@crane.jaist.ac.jp>

Tanaka Akira wrote:
> `_telnet' uses AA named `telent_ports' to complete hosts and ports ---
> keys for hosts and (word splitted) values for ports.
> (If the host completion is failed, `_hosts' is called.)

Just some random ideas.

I'd have said there was room for an autoloaded function _ports, which can
use telnet_ports and then default to something like
  awk '/^[a-z]/ { print $1 }' /etc/services
if nothing turns up.  As Bart implied, it might be useful to have it
index on commands, too:  you could have the convention, say, that
commands had a trailing * added (quoted, obviously).  Then _ports
could be called like "_ports <cmd> <host>".  You could make it search
the assoc array <cmd>_ports, which is sort of what's happening with
telnet_ports and socket_ports.  In that case indexing on commands is
perhaps superflous and you could have a special key (e.g. '*') giving
a default port.
-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56100 Pisa, Italy


  parent reply	other threads:[~1999-09-13  9:09 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 [this message]
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
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=199909130909.LAA14546@paris.ifh.de \
    --to=pws@ifh.de \
    --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).