From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: _netcat
Date: Mon, 11 Mar 2002 11:26:06 +0000 [thread overview]
Message-ID: <20020311112606.GA20670@logica.com> (raw)
In-Reply-To: <1020310222552.ZM26165@candle.brasslantern.com>
On Sun, Mar 10, 2002 at 10:25:51PM +0000, Bart Schaefer wrote:
> } nc conflicts with _nedit. On Debian this isn't an issue
> } (nedit's nc is distributed as nedit-nc), so the compdef
> } line in _nedit can be changed accordingly.
Argh. I knew this would happen sooner or later and was hoping nobody
would write an _netcat.
> The one thing we *can't* do is leave `#compdef nc' in *both* of them, as
Agreed.
> #compdef -p *X*/nc
> _nedit "$@"
I don't really like that. I tend to have nc in ~/bin or /usr/local
because distributions tend to link nedit against lesstif instead of real
motif and because I often have newer versions out of cvs.
Admittedly, I can work around it with a compdef in my .zshrc but I don't
like that.
What I would suggest is that we use something like the is_gnu tests in
_netcat which runs nc -h and looks for something like *connect*.
_netcat can then call _nedit if appropriate.
I also think it would be pertinent to rename _is_gnu to something like
_cmd_variant and use the value gnu instead of yes. Does that sound
reasonable?
> Then we'd change the #compdef in _nedit to read
>
> #compdef nedit nedit-nc
Mandrake uses ncl. If anyone has SuSE, could they please check what it
does. I'm fairly unsure but I think they used `netcat' for netcat.
Certainly, I don't remember having problems with the name clash when I
used it.
I'll also check what is going on in the latest nedit cvs because a few
months ago there was a discussion about renaming nc to nedit and nedit
to nedit-server or of making the main nedit program act as a server by
default.
Oliver
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
next prev parent reply other threads:[~2002-03-11 11:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 22:25 Bart Schaefer
2002-03-11 11:26 ` Oliver Kiddle [this message]
2002-03-12 17:38 ` Oliver Kiddle
2002-03-13 8:32 ` Sven Wischnowsky
2002-03-14 12:22 ` Oliver Kiddle
2002-03-15 8:39 ` Sven Wischnowsky
2002-03-15 16:06 ` Oliver Kiddle
2002-03-15 16:45 ` Bart Schaefer
2002-03-20 9:23 ` Sven Wischnowsky
-- strict thread matches above, loose matches on Subject: below --
2002-03-10 4:17 Clint Adams
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=20020311112606.GA20670@logica.com \
--to=okiddle@yahoo.co.uk \
--cc=schaefer@brasslantern.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).