zsh-users
 help / color / mirror / code / Atom feed
From: Sven Guckes <guckes@math.fu-berlin.de>
To: zsh-users@math.gatech.edu
Subject: Re: completion control for "man" command
Date: Mon, 15 Jun 1998 02:18:59 +0200	[thread overview]
Message-ID: <19980615021859.B6601@math.fu-berlin.de> (raw)
In-Reply-To: =?iso-8859-1?Q?=3C19980614015032=2E30444=40picard=2Efranken=2Ede=3E=3B_f?= =?iso-8859-1?Q?rom_Thomas_K=F6hler_on_Sun=2C_Jun_14=2C_1998_at_01:50:32A?= =?iso-8859-1?Q?M_+0200?=

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.
:-/  Besides, I wouldn't want to set up a cron job for this, either.

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.  ;-)

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.  ;-)

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

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


  reply	other threads:[~1998-06-15  0:27 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 [this message]
1998-06-15  1:36     ` Bart Schaefer
1998-06-15  8:54     ` Thomas Koehler
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=19980615021859.B6601@math.fu-berlin.de \
    --to=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).