From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: PATCH: _subscript, Re: pws-23
Date: Mon, 21 Jun 1999 13:43:19 +0200 [thread overview]
Message-ID: <9906211143.AA29441@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Kiddle, Oliver""'s message of "Mon, 21 Jun 1999 12:52:37 DFT." <4FBF540FF16FD1119D9600A0C94B2B51F29E95@napier.logica.co.uk>
"Kiddle, Oliver" wrote:
> _subscript in pws-23 seems to have been slightly damaged, probably due to
> word wrapping somewhere.
I've received this one with the first hunk wrapped, too. It's probably
your end, since I've haven't noticed it when Sven and others having been
flinging patches about with abandon.
> I use print -D to print
> the value of the array. This is rather useful with things like path where
> things get compacted to something like ~/bin.
I wish there was a way of getting things like this done without forking,
roughly the way TCL does.
> BTW, the _hosts change which I sent last Friday (and which isn't in pws-23)
> doesn't work with my hosts file at home so I'll send a replacement later in
> the week.
I must have forgotten about that. But we probably need more sophisticated
ways of generating host names from all sorts of different sources.
/etc/hosts isn't all that well used any more.
--
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-06-21 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-21 11:52 Kiddle, Oliver
1999-06-21 11:43 ` Peter Stephenson [this message]
1999-07-01 14:34 ` PATCH: completion for hosts and character classes Oliver Kiddle
1999-07-02 9:10 ` Peter Stephenson
1999-06-21 13:04 ` PATCH: _subscript, Re: pws-23 Andrej Borsenkow
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=9906211143.AA29441@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).