From: Christian Neukirchen <chneukirchen@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: zsh glitch
Date: Thu, 12 Nov 2015 16:48:13 +0100 [thread overview]
Message-ID: <871tbvfcci.fsf@gmail.com> (raw)
In-Reply-To: <CAHYJk3S7oHyibz7iLKFuG8eTHhrVMWWiYEFDQnR1asw=1Y9nxw@mail.gmail.com> (Mikael Magnusson's message of "Tue, 10 Nov 2015 22:43:20 +0100")
Mikael Magnusson <mikachu@gmail.com> writes:
> What you've done is define a function that looks like this
> ls() {
> ls
> }
> and then you call it, which causes an infinite recursion. This usually
> does not end well in any language.
Time to add tail-recursion to zsh!
--
Christian Neukirchen <chneukirchen@gmail.com> http://chneukirchen.org
prev parent reply other threads:[~2015-11-12 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 21:36 Lane Erickson
2015-11-10 21:43 ` Mikael Magnusson
2015-11-11 9:36 ` Peter Stephenson
2015-11-12 15:48 ` Christian Neukirchen [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=871tbvfcci.fsf@gmail.com \
--to=chneukirchen@gmail.com \
--cc=zsh-workers@zsh.org \
/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).