From: Peter Stephenson <p.stephenson@samsung.com>
To: "Nicolas Desprès" <nicolas.despres@gmail.com>, zsh-workers@zsh.org
Subject: Re: Crash when completion script call itself.
Date: Fri, 29 Sep 2017 12:10:08 +0100 [thread overview]
Message-ID: <20170929121008.3da15b34@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAPqtr1KToL4KMX0Rh7dgtpqR9MvgJL06N-ChiXY6Qf-uCwOqsw@mail.gmail.com>
On Sat, 30 Sep 2017 00:03:53 +1300
Nicolas Desprès <nicolas.despres@gmail.com> wrote:
> On Fri, Sep 29, 2017 at 11:45 PM, Peter Stephenson <p.stephenson@samsung.com
> > wrote:
> >
> > ...come to think of it, slightly more helpfully, you can at least see
> > how far it gets on your system...
> >
> > i=0; fn() { print $(( ++i )); fn; }; fn
> >
>
> 767 and then crash. Maybe setting it to 500 would be enough? I think I
> remember that Python limit is 500 too.
I've no personal objection to reducing it to 500 by default (and I'll
probably add a variable anyway), but I'd like to know if anyone has
strong feelings --- given this is a bit of a kludge anyway and this is
based on a sample of one.
pws
next prev parent reply other threads:[~2017-09-29 11:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170929072715epcas1p4171c28e9b82f94d79796ecca7e564ec3@epcas1p4.samsung.com>
2017-09-29 7:25 ` Nicolas Desprès
2017-09-29 9:34 ` Peter Stephenson
2017-09-29 10:30 ` Nicolas Desprès
2017-09-29 10:40 ` Peter Stephenson
2017-09-29 10:45 ` Peter Stephenson
2017-09-29 11:03 ` Nicolas Desprès
2017-09-29 11:10 ` Peter Stephenson [this message]
2017-09-29 11:27 ` Kamil Dudka
2017-09-29 14:16 ` Peter Stephenson
2017-09-29 15:22 ` Bart Schaefer
2017-09-29 15:36 ` Peter Stephenson
2017-09-29 17:48 ` Bart Schaefer
2017-10-02 15:40 ` Peter Stephenson
2017-10-03 14:45 ` Kamil Dudka
2017-10-03 17:55 ` Mikael Magnusson
2017-10-04 8:20 ` Peter Stephenson
[not found] ` <9379.1507044225@thecus.kiddle.eu>
2017-10-03 15:50 ` Peter Stephenson
2017-09-29 23:00 ` Nicolas Desprès
2017-09-29 11:38 ` Nicolas Desprès
2017-09-29 11:37 ` Martijn Dekker
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=20170929121008.3da15b34@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=nicolas.despres@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).