From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: 6-pws-2
Date: Wed, 01 Sep 1999 10:09:15 +0200 [thread overview]
Message-ID: <9909010809.AA21168@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Mon, 30 Aug 1999 21:03:06 DFT." <990830210306.ZM6724@candle.brasslantern.com>
"Bart Schaefer" wrote:
> Wow, good job, Peter! The only ones you seem to have missed are:
>
> 7414, fix info doc for makeinfo 3.12f
I didn't get that for some reason (or deleted it without applying it).
> 7436, change the way the last command in a pipeline is exec'd
>
> Unless of course I missed the same ones you did, which is possible. Truth
> to tell, I "missed" 7436 on purpose and was watching for whether you would
> include it -- did you intentionally leave it out?
See below.
> There does appear to be one other problem -- there is a complete copy of
> each of two versions of the _xterm completer in Completion/X/_xterm. I
> think the top one is the one to keep.
This was fixed by Sven's patch, too.
Tanaka Akira wrote:
> > - There's an exec.c patch from Tanaka Akira, 7436, left out, because it was
> > followed by an inconclusive discussion. It's supposed to fix exec'ing
> > the last element of the last pipeline. I have not looked at the problem.
>
> I think 7436 is the correct fix to the problem.
I finally looked at it and it seems fine. I don't understand why it wasn't
working that way before. Probably it was overlooked in some other changed.
> > - Personally, I prefer one single completion function for a suite of
> > related commands
>
> The separation is sometimes useful for custumizations because we can
> override each function individually. These functions behaves like `hook'.
> I think it is useful that making hooks more easily without adding new files.
This is a good point, maybe Sven's idea can help with this. It would be
nice to keep it as function-based as possible. Simplifying the initial
implementation (where you could define variables as well as functions) was
a big step to making the whole thing more usable.
--
Peter Stephenson <pws@ibmth.df.unipi.it> Tel: +39 050 844536
WWW: http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy
next prev parent reply other threads:[~1999-09-01 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-30 16:00 6-pws-2 Peter Stephenson
1999-08-30 21:03 ` 6-pws-2 Bart Schaefer
1999-09-01 8:09 ` Peter Stephenson [this message]
1999-08-31 3:37 ` 6-pws-2 Tanaka Akira
1999-08-31 8:43 ` Modules - How to write ? jarausch
1999-08-31 9:27 ` 6-pws-2 Ollivier Robert
1999-08-31 8:15 6-pws-2 Sven Wischnowsky
1999-08-31 21:05 ` 6-pws-2 Bart Schaefer
1999-08-31 8:22 6-pws-2 Sven Wischnowsky
1999-08-31 11:28 ` 6-pws-2 Andrej Borsenkow
1999-08-31 17:10 ` 6-pws-2 Bart Schaefer
1999-09-01 8:24 ` 6-pws-2 Peter Stephenson
1999-08-31 12:38 6-pws-2 Sven Wischnowsky
1999-08-31 16:19 ` 6-pws-2 Tanaka Akira
1999-09-01 8:46 6-pws-2 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=9909010809.AA21168@ibmth.df.unipi.it \
--to=pws@ibmth.df.unipi.it \
--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).