zsh-users
 help / color / mirror / code / Atom feed
From: Thomas Koehler <thomas@wi3d01.informatik.uni-wuerzburg.de>
To: Sven Guckes <guckes@math.fu-berlin.de>
Cc: zsh-users@math.gatech.edu
Subject: Re: completion control for "man" command
Date: Mon, 15 Jun 1998 10:54:27 +0200	[thread overview]
Message-ID: <19980615105427.02760@willkuere.informatik.uni-wuerzburg.de> (raw)
In-Reply-To: <19980615021859.B6601@math.fu-berlin.de>; from Sven Guckes on Mon, Jun 15, 1998 at 02:18:59AM +0200

On Mon, Jun 15, 1998 at 02:18:59AM +0200, Sven Guckes wrote:

> Quoting Thomas Köhler (jean-luc@picard.franken.de):
> > I use the following for man completion. It uses a file ~/tmp/_man_ which
> > stores the filenames in question. If you don't like your loginshell to
> > wait for the creation of the file every now and then (I use 14 days)
> > because it creates the _man_-file, just make a cronjob out of this...
> 
> Well, I wouldn't want my completion control to rely on the existence of a file
> in /tmp - after all everybody at our site is allowed to delete files in /tmp.
> :-/

That's why I use ~/tmp ;-) See the difference? :-)

> Besides, I wouldn't want to set up a cron job for this, either.

Well, I have that in my .zshrc, no cronjob needed. But then, sometimes
the creating of the list when logging in is annoying...

> Now, if I can get our sysadmin (hi, Stucki) to create a little database
> on man pages (with a cronjob or whatever) - that's fine. And, yes, I do
> believe this job can be done with the help of awk, sed, and perl.  ;-)

Or zsh ;-)

> But aren't we discussing the zsh here?  Shouldn't there be a way to do
> the job with the zsh alone?   I'd rather see an elegant solution with
> a few commands within the zsh than a perfomant database solution with
> SAP's R/3 using a Alpha with 4G RAM.  ;-)

Well... my completion was written within 3 minutes and I didn't test how
long it would take to find all the manpages on-the-fly. But if I think
how long it takes to build the file (some seconds), I think it's too
slow to run every time I need the completion...

> Also, I wouldn't mind some more examples in the zsh manuals...

OK, acknowledged :)

> Sven  [who promises to add all his zsh examples to his zsh page SOON]

*looking*
tips.html is pretty cool :-)
compctl.html should have more explanations, but is OK :)

CU,
Thomas [still not having a zsh page]

-- 
    Thomas Köhler    Email:     jean-luc@picard.franken.de
        <><           WWW:    http://home.pages.de/~jeanluc/
                      IRC:               jeanluc
      LCARS --- Linux for Computers on All Real Starships


  parent reply	other threads:[~1998-06-15  9:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-06-13 18:40 Sven Guckes
1998-06-13 23:50 ` Thomas Köhler
1998-06-15  0:18   ` Sven Guckes
1998-06-15  1:36     ` Bart Schaefer
1998-06-15  8:54     ` Thomas Koehler [this message]
1998-06-14  0:29 ` 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=19980615105427.02760@willkuere.informatik.uni-wuerzburg.de \
    --to=thomas@wi3d01.informatik.uni-wuerzburg.de \
    --cc=guckes@math.fu-berlin.de \
    --cc=zsh-users@math.gatech.edu \
    /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).