From: "Mark J. Reed" <markjreed@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: exit to shell from nested function calls.
Date: Fri, 17 May 2024 15:00:04 -0400 [thread overview]
Message-ID: <CAA=-s3zS41FgdXgsTbjupOeijArZXBHTPmj0gJEZin7VHF6tdQ@mail.gmail.com> (raw)
In-Reply-To: <2b657d1a-4bf3-4756-bb1f-6df9d49ecb13@eastlink.ca>
[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]
The Bolsky & Korn KornShell book is a good start, actually. Lots of stuff
zsh has added that's not in there, but as far as first principles go ...
Mark J. Reed <markjreed@gmail.com>
On Fri, May 17, 2024 at 14:53 Ray Andrews <rayandrews@eastlink.ca> wrote:
>
>
> On 2024-05-17 10:36, Bart Schaefer wrote:
>
> On Fri, May 17, 2024, 10:04 AM Bart Schaefer <schaefer@brasslantern.com>
> wrote:
>
>> ... make it a script first, then think about
>> whether it's simple enough to become a function.
>>
>
> Forgot to mention, you can also get the best of both worlds by writing a
> function with sections (up to even the whole function body) wrapped in
> subshell parens.
>
> My whole project of trying to learn zsh 'as you go', was wrong from the
> start. There are things like the above that can only be learned by
> instruction -- or by endless grief. Need zsh classroom where the teacher
> knows what you need to know before you know you need to know it. A very
> good book would be nice too.
>
>
>
[-- Attachment #2: Type: text/html, Size: 2376 bytes --]
next prev parent reply other threads:[~2024-05-17 19:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 14:21 Ray Andrews
2024-05-16 20:26 ` Roman Perepelitsa
2024-05-16 21:28 ` Ray Andrews
2024-05-17 15:40 ` Mark J. Reed
2024-05-17 15:58 ` Ray Andrews
2024-05-17 16:46 ` Mark J. Reed
2024-05-17 17:04 ` Bart Schaefer
2024-05-17 17:36 ` Bart Schaefer
2024-05-17 18:52 ` Ray Andrews
2024-05-17 19:00 ` Mark J. Reed [this message]
2024-05-17 20:28 ` Ray Andrews
2024-05-18 2:09 ` Bart Schaefer
2024-05-17 17:29 ` Thomas Lauer
2024-05-17 18:43 ` Ray Andrews
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='CAA=-s3zS41FgdXgsTbjupOeijArZXBHTPmj0gJEZin7VHF6tdQ@mail.gmail.com' \
--to=markjreed@gmail.com \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@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).