[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: unwind-protect within while-no-input
From: |
Michael Heerdegen |
Subject: |
Re: unwind-protect within while-no-input |
Date: |
Wed, 08 May 2024 18:17:12 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Spencer Baugh <sbaugh@janestreet.com> writes:
> Sorry, it's not intentional - from my perspective I've been asking for
> the same thing each time, with all the same details. But clearly I have
> been not fully communicating what I mean.
You make us guessing what "it" in "it doesn't work" or "it actually
doesn't work" is.
When it is not clear to you what you actually want, describe the problem
you want to solve and ask for help to solve it.
What we all dislike are questions of the form "I wrote this code, it
doesn't work". As you see, it costs a lot of time to get to the core.
Time that can not be invested into solving other problems.
Michael.
- Re: unwind-protect within while-no-input, (continued)
- Re: unwind-protect within while-no-input, Dmitry Gutov, 2024/05/14
- Re: unwind-protect within while-no-input, Stefan Monnier, 2024/05/25
- Re: unwind-protect within while-no-input, Dmitry Gutov, 2024/05/26
- Re: unwind-protect within while-no-input, Stefan Monnier, 2024/05/26
- Re: unwind-protect within while-no-input, Dmitry Gutov, 2024/05/26
- Re: unwind-protect within while-no-input, Stefan Monnier, 2024/05/28
- Re: unwind-protect within while-no-input, Dmitry Gutov, 2024/05/28
- Re: unwind-protect within while-no-input,
Michael Heerdegen <=
Re: unwind-protect within while-no-input, Stefan Monnier, 2024/05/25