From: Michel <michel.barret@gmail.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@zsh.org
Subject: Re: Predefine the next buffer
Date: Sun, 9 May 2021 22:53:52 +0200 [thread overview]
Message-ID: <CADprNYmPMBRYjvpMGO9qF_YrY55msLFTqtqjVUPeqrXy2sVBQA@mail.gmail.com> (raw)
In-Reply-To: <594d109998dd94a1654334f55a8d679fad742b70.camel@ntlworld.com>
[-- Attachment #1: Type: text/plain, Size: 365 bytes --]
> So "foo" is something like a shell function thatʼs going to do some
> stuff, and you want it also to set up the next editing command line for
> you?
>
> Try this:
>
> foo() {
> print -z bar
> }
>
Exactly this! Thank you very much.
(BTW user questions really belong on zsh-users.)
>
Sorry I'm not sure
_____________________
Michel BARRET
[-- Attachment #2: Type: text/html, Size: 859 bytes --]
prev parent reply other threads:[~2021-05-09 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 19:11 Michel
2021-05-09 20:02 ` Peter Stephenson
2021-05-09 20:53 ` Michel [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=CADprNYmPMBRYjvpMGO9qF_YrY55msLFTqtqjVUPeqrXy2sVBQA@mail.gmail.com \
--to=michel.barret@gmail.com \
--cc=p.w.stephenson@ntlworld.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).