zsh-workers
 help / color / mirror / code / Atom feed
From: Mark Borges <mdb@cdc.noaa.gov>
To: hzoli@cs.elte.hu
Cc: zsh-workers@math.gatech.edu
Subject: Re: list-expand fix and a bug report
Date: Fri, 21 Jul 1995 14:37:21 -0600	[thread overview]
Message-ID: <9507212037.AA10841@suomi.cdc.noaa.gov> (raw)
In-Reply-To: <9507211829.AA09086@turan.elte.hu>

>> Zoltan Hidvegi(ZH) wrote on Fri, 21 Jul 1995 20:29:30 +0100 (MET DST):
[...]
ZH> The patch below fixes all of these bugs and even some more:

Zoltan--

Do any of these patches for 10.1 (or 10+ for that matter) fix this:

------------------------------------------------------------------------------
>> Mark Borges(mb) wrote on Mon, 17 Jul 95 14:50:50 MDT:
mb> Are you seeing this?

mb> Somewhere between hzoli9 and hzoli10.1 <TAB> completion inside a for
mb> control structure doesn't work. For example,

mb> $ ~/bin/sparc/zsh-2.6h9 -f
mb> bjerknes% echo $ZSH_VERSION
mb> 2.6-beta9
mb> bjerknes% setopt autolist
mb> bjerknes% for i in a*; do
>> echo a<TAB>	# a tab correctly prints out the ambiguous files
mb> a1  a2  a3

mb> but in hzoli10.1:

mb> $ ~/bin/sparc/zsh-2.6h10.1 -f
mb> bjerknes% echo $ZSH_VERSION
mb> 2.6-beta10-hzoli10.1
mb> bjerknes% setopt autolist 
mb> bjerknes% for i in a*; do

>> echo a<TAB>	# Huh? Another a keeps getting added, and no list is printed.

>> echo aa<TAB>
      
>> echo aaa<TAB>	# can go on indefinitely
      
>> echo aaaa
      
>> echo aaaaa
      
>> echo aaaaaa
      
mb> This also has patches from zefram (I forget what they do). I was just
mb> curious if the bug has infected your copy as well.
------------------------------------------------------------------------------
Or, can anyone verify whether vanilla beta 10 has the above bug?

Thanks,

  -mb-


  reply	other threads:[~1995-07-21 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-07-16  2:05 Zefram
1995-07-21 19:29 ` Zoltan Hidvegi
1995-07-21 20:37   ` Mark Borges [this message]
1995-07-24  9:46     ` Zoltan Hidvegi

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=9507212037.AA10841@suomi.cdc.noaa.gov \
    --to=mdb@cdc.noaa.gov \
    --cc=hzoli@cs.elte.hu \
    --cc=zsh-workers@math.gatech.edu \
    /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).