From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [Feature Request] Re: Can one detect that Zsh/Zle is in recursive-edit?
Date: Tue, 14 Aug 2018 19:44:15 +0200 [thread overview]
Message-ID: <CAKc7PVA2cfOcfDSso11irCgH+fPFu9mJpXjESnDz3pXz8J0vDA@mail.gmail.com> (raw)
In-Reply-To: <20180814170657eucas1p1b9864da7e9086c27fa499e99152e14cb~Kzy2ccSm-2262422624eucas1p1t@eucas1p1.samsung.com>
On Tue, 14 Aug 2018 at 19:14, Peter Stephenson <p.stephenson@samsung.com> wrote:
>
> On Tue, 14 Aug 2018 18:17:36 +0200
> Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> > If there currently is no method of detecting .recursive-edit
> > "session", then could a feature request be responded positively:
> > please add an indicator that Zsh is in .recursive-edit state
> > ("session").
>
> It's certainly easy to do (although probably not hard to add at
> the user level as calls to recursive-edit ought to be explicit).
Cool, thanks. In effect, when new release will be made, I'll send
patches to zsh-autosuggestions and zsh-syntax-highlighting that will
suppress those plugins on ZLE_RECURSIVE > 0 (which often means some
"application" has started a "session" and doesn't want to be
interfered).
--
Sebastian Gniazdowski
News: https://twitter.com/ZdharmaI
IRC: https://kiwiirc.com/client/chat.freenode.net:+6697/#zplugin
prev parent reply other threads:[~2018-08-14 17:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKc7PVC_i6fvhLSoWqFdNa0egtXj+Sfoou0FUQmjU+TXexyOFA@mail.gmail.com>
[not found] ` <CGME20180814161906epcas3p37378a9a3eb58ea9a526c3b9fadd91531@epcas3p3.samsung.com>
[not found] ` <CAKc7PVBsSGqW1m5hKTPYDFTmi+=EqvWAJExCWzBkHW8OjHO_zQ@mail.gmail.com>
2018-08-14 17:06 ` Peter Stephenson
2018-08-14 17:30 ` Bart Schaefer
2018-08-14 17:44 ` Sebastian Gniazdowski [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=CAKc7PVA2cfOcfDSso11irCgH+fPFu9mJpXjESnDz3pXz8J0vDA@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=p.stephenson@samsung.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).