zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: _urls, _netscape, a seg fault and new completion thoughts
Date: Wed, 13 Oct 1999 16:37:08 +0000	[thread overview]
Message-ID: <991013163708.ZM14753@candle.brasslantern.com> (raw)
In-Reply-To: <991013160900.ZM11391@candle.brasslantern.com>

On Oct 13,  4:09pm, Bart Schaefer wrote:
} Subject: Re: PATCH: _urls, _netscape, a seg fault and new completion thoug
}
} On Oct 13,  4:34pm, Oliver Kiddle wrote:
} } Subject: Re: PATCH: _urls, _netscape, a seg fault and new completion thoug
} }
} } > > Is there a good reason why I don't get a list of matches when
} } > > completing inside quotes?
} } > Hm, this works for me -- unless you mean `cd man m<TAB>' which of
} } > course shouldn't work.
} } 
} } I did mean as I said. It still doesn't work (3.1.6-pws-6 on AIX or 3.1.6
} } on Linux).
} 
} Doesn't work for me either; not even the first bit that works for Oliver.
} 
} Doesn't matter if the command is ls, cd, bindkey ... unambiguous prefixes
} get inserted, but as soon as there's an ambiguity it all stops.

Incidentally, it doesn't work with old-style completion either, so it's
not a problem with the shell functions or compstate.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-10-13 16:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-13 14:17 Sven Wischnowsky
1999-10-13 15:34 ` Oliver Kiddle
1999-10-13 16:09   ` Bart Schaefer
1999-10-13 16:37     ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-10-14  6:43 Sven Wischnowsky
1999-10-13 14:22 Sven Wischnowsky
1999-10-13 12:11 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=991013163708.ZM14753@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.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).