zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: generals observations about completion system
Date: Tue, 19 Sep 2000 10:04:00 +0100	[thread overview]
Message-ID: <0G140090FMIN8S@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Tue, 19 Sep 2000 04:59:29 -0000." <1000919045929.ZM30416@candle.brasslantern.com>

Bart wrote:
> It does tend to be easier to add new completion functions than it is to
> document them.

I haven't had much time for replying (have you seen the specification for
Bluetooth park mode? :-() but self-documenting functions with something
like pod, except using shell functions to strip out the bits and turn them
into yodl, should be pretty easy.  Adding comments is usually much easier
than fiddling with the full documentation.

Moving the string functions to their own file would be a step in the right
direction, too.  It's hard to know what's in utils.c.  (It's not as if the
rest of the shell doesn't consist of utilities, despite the double
negative.)

By the way, I'm finally getting a week's holiday from tomorrow and luckily
in a PC-free zone.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK                          Tel: +44 (0)1223 392070


  reply	other threads:[~2000-09-19  9:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-17 23:33 E. Jay Berkenbilt
2000-09-19  4:59 ` Bart Schaefer
2000-09-19  9:04   ` Peter Stephenson [this message]
2000-09-19 15:19     ` Bart Schaefer
2000-09-19 15:51       ` Clint Adams
2000-09-20 14:33     ` Thoughts on self-documenting functions Bart Schaefer
2000-10-04 11:44 generals observations about completion system Sven Wischnowsky

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=0G140090FMIN8S@la-la.cambridgesiliconradio.com \
    --to=pws@csr.com \
    --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).