Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Non-intuitive completion
- X-seq: zsh-workers 5783
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Non-intuitive completion
- Date: Sat, 13 Mar 1999 09:26:50 -0800
- In-reply-to: <199812031148.MAA14745@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199812031148.MAA14745@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author