zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@math.gatech.edu
Subject: Re: Non-intuitive completion
Date: Sat, 13 Mar 1999 09:26:50 -0800	[thread overview]
Message-ID: <990313092650.ZM633@candle.brasslantern.com> (raw)
In-Reply-To: <199812031148.MAA14745@beta.informatik.hu-berlin.de>

On Dec 3, 12:48pm, Sven Wischnowsky wrote:
} Subject: Re: Non-intuitive completion
}
} Bart Schaefer wrote:
} 
} > ...
} > 
} > Now, if you'd like to see some REALLY strange behavior, which definitely
} > IS a bug in my book, try
} > 
} > zsh% bindkey '^I' expand-or-complete
} > zsh% setopt nounset
} > zsh% print $ZSH_*<TAB>
} 
} The patch below fixes the problem by making zerr() set errflag
} independent of the setting of noerrs. I am far from knowing if this
} should go there (or in paramsubst() or in prefork(), or in...).

I notice this patch isn't in pws-11.  Is it made irrelevant by the new
completion stuff?  If not, can anyone think of a way to test whether
it's the right thing to do WRT not breaking other uses of zerr() ?

Here it is again so you don't have to search the archives:

} *** os/utils.c	Thu Dec  3 09:10:46 1998
} --- Src/utils.c	Thu Dec  3 12:07:49 1998
} ***************
} *** 52,59 ****
}   void
}   zerr(const char *fmt, const char *str, int num)
}   {
} !     if (errflag || noerrs)
}   	return;
}       errflag = 1;
}       trashzle();
}       /*
} --- 52,61 ----
}   void
}   zerr(const char *fmt, const char *str, int num)
}   {
} !     if (errflag || noerrs) {
} ! 	errflag = 1;
}   	return;
} +     }
}       errflag = 1;
}       trashzle();
}       /*

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


  reply	other threads:[~1999-03-13 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-03 11:48 Sven Wischnowsky
1999-03-13 17:26 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-15 10:06 Sven Wischnowsky
1998-12-01  2:47 Phil Pennock
1998-12-01  6:28 ` Bart Schaefer

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=990313092650.ZM633@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).