zsh-users
 help / color / mirror / code / Atom feed
From: "Thomas Köhler" <jean-luc@picard.franken.de>
To: zsh-users@sunsite.auc.dk
Subject: Re: coproc tutorial (Re: questions)
Date: Tue, 12 Oct 1999 10:42:42 +0200	[thread overview]
Message-ID: <19991012104242.A7824@picard.franken.de> (raw)
In-Reply-To: <199910120653.IAA03827@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Tue, Oct 12, 1999 at 08:53:29AM +0200

On Tue, Oct 12, 1999 at 08:53:29AM +0200,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> wrote:
> 
> Thomas Koehler wrote:
> 
> > > 3.1.6-pws-something (at least the latest pws-6) has Functions/Misc/nslookup
> > > which uses `vared' to read the user input, thus allowing command line
> > > editing. Together with the new completion system this function will
> > > also give you completion *inside* nslookup (and not only nslookup's
> > > arguments).
> > 
> > Now this is really cool... how do I enable this? :-)
> 
> Well, new style completion with the usual call to `compinit' (after
> autoloading and things), and then just make `nslookup' autoloaded and
> call it. For my version of `nslookup' here, it works, but as Bart
> mentioned in 2668, it doesn't work everywhere (and I don't feel like
> spending more time trying to improve the beast, it was mainly a hack
> to show how the `compcontext' parameter can be used).

Ah. OK, tried it now, but it doesn't work: nslookup on my machine
(Debian GNU/Linux) won't work as a coprocess (has this to do with the
fact that it refuses to read from stdin?). Bad luck here...

> > > To workers: seems like noone found this interesting enough to improve
> > > the code I hacked up. Maybe sometime we could write a generic function 
> > > for this task...
> > 
> > Allowing completion from within all stdin/stdout-bound programs?
> > ncftp -L is a candidate here, amongst others...
> 
> ;-) there are may of them...

:-)

> Bye
>  Sven

CU,

Thomas

-- 
 Thomas Köhler Email:   jean-luc@picard.franken.de   | LCARS - Linux for
     <><        WWW:  http://home.pages.de/~jeanluc/ | Computers on All
                IRC:             jeanluc             | Real Starships
   PGP public key: http://www.mayn.de/users/jean-luc/PGP-Public.asc


  reply	other threads:[~1999-10-12  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-12  6:53 Sven Wischnowsky
1999-10-12  8:42 ` Thomas Köhler [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-10-11 10:45 Sven Wischnowsky
1999-10-11 12:55 ` Thomas Köhler
1999-10-04 16:10 Jay Sekora
1999-10-04 18:42 ` Bart Schaefer
1999-10-03  8:30 questions Chris Hansen
1999-10-03 11:10 ` questions Stefan Berglund
1999-10-03 18:45   ` coproc tutorial (Re: questions) Bart Schaefer
1999-10-03 21:08     ` Chris Hansen
1999-10-04  2:01       ` coproc Chris Hansen
1999-10-04  4:41         ` coproc tutorial (Re: questions) Bart Schaefer
1999-10-04  5:21           ` Chris Hansen
1999-10-04  6:22             ` Bart Schaefer

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=19991012104242.A7824@picard.franken.de \
    --to=jean-luc@picard.franken.de \
    --cc=zsh-users@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).