From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: Howto to print ENTER to zle-buffer?
Date: Tue, 13 Dec 2016 17:03:12 -0800 [thread overview]
Message-ID: <161213170312.ZM23037@torch.brasslantern.com> (raw)
In-Reply-To: <20161213192941.z3foaju5gslyeqse@spiegl.de>
On Dec 13, 8:29pm, Andy Spiegl wrote:
} Subject: Re: Howto to print ENTER to zle-buffer?
}
} > Given this -- and assuming you can target zsh-5.3 -- I'd go with:
} I'm still stuck with 5.2. Guess I have to wait a while then. :-(
No, it can still be done; you'll just have to be sure that your
zle-line-init widget doesn't conflict with one the user already has.
Actually if you grab Functions/Misc/add-zle-hook-widget from 5.3 and
make it part of your session manager, it should work in 5.2.
} You define the function "session-startup"
Which I typo'd, I left out the () between the function name and the
open brace ...
} which is then hooked
} to zle such that it is run after initialization? How does it show
} up in the zle buffer then? No "print -z" anymore?
I won't show up in the ZLE buffer, instead it will just execute at
the time zle starts up. I don't know why you'd need it to appear in
the buffer if it's just going to be accept-line'd immediately, but
you can do that like this:
session-startup() {
zle -U $'command-to-run args\n'
add-zle-hook-widget -d line-init $WIDGET
}
To "backport" that to 5.2 without add-zle-hook-widget:
zle-line-init() {
if [[ -n $functions[session-startup] ]]
then
session-startup
unfunction session-startup
fi
# Do whatever the user's zle-line-init did
}
zle -N zle-line-init
session-startup() {
zle -U $'command-to-run args\n'
}
next prev parent reply other threads:[~2016-12-14 2:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 15:01 Andy Spiegl
2016-12-13 16:12 ` Bart Schaefer
2016-12-13 16:47 ` Andy Spiegl
2016-12-13 17:30 ` Bart Schaefer
2016-12-13 19:29 ` Andy Spiegl
2016-12-14 1:03 ` Bart Schaefer [this message]
2016-12-15 18:20 ` Andy Spiegl
2016-12-16 2:29 ` Bart Schaefer
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=161213170312.ZM23037@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).