zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: Problems with Functions/Misc/nslookup
Date: Thu, 31 May 2001 09:33:48 +0200 (MET DST)	[thread overview]
Message-ID: <200105310733.JAA09718@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <1010530180127.ZM3076@candle.brasslantern.com>

Bart Schaefer wrote:

> Most seriously, on my system it doesn't always notice when the prompt is
> back:
> 
> schaefer[502] nslookup                                              4.0.1-pre-5
> Default Server:  ns.best.com
> Address:  204.156.128.1
> 
> > set querytype=mx
> (hangs here until interrupted)
> 
> I think this may be because nslookup does not print anything at all (not
> even a blank line) before printing the prompt, after executing a `set'
> command.  It does find the prompt after a name lookup (see below).

Yes, that pattern used for zpty -r has to be a bit more intelligent.

> Then there's this interesting completion behavior:
> 
> ...
> 
> > set querytype=m<TAB>
> > set querytype=m:\{a-zA-Z\}=\{A-Za-z\}\ r:\|\[-._,\]=\*\*\ r:\|=\*\* 
> 
> I'm pretty sure it wasn't supposed to literally insert a matcher spec there.
> :-)

Oops.  _values got slightly confused when not given a separator character.

Bye
  Sven

Index: Completion/Base/Utility/_values
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Base/Utility/_values,v
retrieving revision 1.2
diff -u -r1.2 _values
--- Completion/Base/Utility/_values	2001/05/08 12:24:21	1.2
+++ Completion/Base/Utility/_values	2001/05/31 07:32:45
@@ -84,6 +84,7 @@
   # We add the separator character as a autoremovable suffix unless
   # we have only one possible value left.
 
+  sep=()
   [[ ${#snames}+${#names}+${#onames} -ne 1 ]] && compvalues -s sep &&
       expl=( "-qS$sep" "$expl[@]" ) sep=( "-qS$sep" )
 
Index: Functions/Misc/nslookup
===================================================================
RCS file: /cvsroot/zsh/zsh/Functions/Misc/nslookup,v
retrieving revision 1.9
diff -u -r1.9 nslookup
--- Functions/Misc/nslookup	2001/04/02 13:04:05	1.9
+++ Functions/Misc/nslookup	2001/05/31 07:32:45
@@ -36,8 +36,8 @@
 
   zpty -w nslookup "$line"
 
-  zpty -r nslookup line '*
-> '
+  zpty -r nslookup line '(|*
+)> '
   if [[ -n "$pager" && ${#${(f)line}} -gt LINES ]]; then
     print -nr "$line" | eval "$pager"
   else

-- 
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


      reply	other threads:[~2001-05-31  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 18:01 Bart Schaefer
2001-05-31  7:33 ` Sven Wischnowsky [this message]

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=200105310733.JAA09718@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.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).