From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: seg fault fixed and Makefile change
Date: Mon, 15 May 2000 14:23:24 +0200 (MET DST) [thread overview]
Message-ID: <200005151223.OAA18213@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Oliver Kiddle's message of Mon, 15 May 2000 13:09:05 +0100
Oliver Kiddle wrote:
> Sven Wischnowsky wrote:
> >
> > I couldn't reproduce this (neither before nor after this patch -- your
> > match specs would have helped), but this looks suspiciously similar to
> > the one above... could you try with this patch?
>
> That's fixed it: it now works fine, thanks.
Uff ;-)
> ...
>
> Completion for netscape remote commands doesn't seem to work properly
> anymore:
> netscape -remote <tab>
> Basically, it is a bit too eager to put the \( suffix in. This did
> actually work before but I've always felt that this part of _netscape
> (which I am to blame for) is a bit of a nasty hack. Basically, the
> '(' suffix needs to be quoted unless it already is and that was the
> way I found which worked.
Hm. What exactly doesn't seem to work properly for you anymore? The
only ugliness I can see is that you get the `\(' if the string is not
in quotes but when it is. Why not use:
compadd -s '(' -S '' - ...
or
local suf='('
compquote suf
compadd -qS "$s" - ...
and if the `compset -q' is really needed, put it after the compquote.
I don't really know all the things that are possible with -remote,
though, so these suggestions may not be usable(?).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-05-15 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-15 12:23 Sven Wischnowsky [this message]
2000-05-18 9:45 ` _netscape Oliver Kiddle
-- strict thread matches above, loose matches on Subject: below --
2000-05-15 9:26 PATCH: Re: Seg fault in matcher-list matching Sven Wischnowsky
2000-05-15 12:09 ` seg fault fixed and Makefile change Oliver Kiddle
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=200005151223.OAA18213@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).