From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE,UNPARSEABLE_RELAY autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28637 invoked from network); 5 Aug 2020 09:09:35 -0000 Received: from zero.zsh.org (2a02:898:31:0:48:4558:7a:7368) by inbox.vuxu.org with ESMTPUTF8; 5 Aug 2020 09:09:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=zsh.org; s=rsa-20200801; h=Sender:List-Archive:List-Owner:List-Post:List-Unsubscribe: List-Subscribe:List-Help:List-Id:Content-Transfer-Encoding:Content-Type: MIME-Version:Message-ID:Subject:To:From:Date:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:In-Reply-To:References; bh=jPTpQafMaHWQsavcl2i1107caT+IjpG0oW/pcXGXu3E=; b=MhxzmezNcFHvCfeS5/N9hSmV/7 MfBNayPqBz84lor3YP/JK9jVl51P7Vfvjaj12B787mc0OvQdBIdkmciiVQ3IpmQaxJJ8+iIvh5oRc SNKJUKyUDXONkuC7g0Jb+pnSFTJ8mg2Bj7pKCWD0XtT+NKMWD3/TTuieEilaAFRVHpg24Zc7KzR3H L8WTWm63fuHQ7rsG7BhBshYucJTG4g+eksXAW7W/UD0ZzKCcy0oanxap1T/wzfVW4qytuVS+QvfEM PxWT8W2pAzsafnYR5AQUY5j4xIl7HrzgJLWXpVgUTDRaydI7vGuuMHipsuCTLQw8oYx1t98dUIQmo dL61cPVQ==; Received: from authenticated user by zero.zsh.org with local id 1k3FQM-000MK1-9i; Wed, 05 Aug 2020 09:09:26 +0000 Authentication-Results: zsh.org; iprev=pass (mail.cock.li) smtp.remote-ip=37.120.193.124; dkim=pass header.d=national.shitposting.agency header.s=mail header.a=rsa-sha256 Received: from mail.cock.li ([37.120.193.124]:45752) by zero.zsh.org with esmtp id 1k3FLt-000Kvu-OT; Wed, 05 Aug 2020 09:04:51 +0000 Date: Wed, 5 Aug 2020 11:04:40 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=national.shitposting.agency; s=mail; t=1596618288; bh=j391l6Q+v2DXp4dN+SrZLb25A3qAbm8p9u1989rda/o=; h=Date:From:To:Subject:From; b=dncN9WdC8SykT7CLnukquWVWx84/fIRwsXlf87zSQWRzlBCWh6tpnGgrKpxDI4xSL i6ZTcjZIYRIuAUktRW08ReD0A1Fb8ARF+ahnht6rHsTgeqRvFB4/P3noVeJp5UVHIL +v1FYGeI7Z2NRd7XbgpZ6esraR52LINCi83bMsHcfAyiICEebIlgSBRdSP+za2dxkv OnPoT03fx+huy4XvobfkzV02+SNxqGxkva1XJCzGxY1K+HvKantAu/4OlbR9biEOJP Gpt9intBft7e6NtktsxK0H5X6yzxd3Cwui9FpetD1dUM6QyvJymBuTrzmoCylUPYjG b6IFOZS0WyiFg== From: zsugabubus To: zsh-workers@zsh.org Subject: zle edit-command-line and send-break Message-ID: <20200805090440.7mcsjqc2wa7frzo5@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Seq: 47295 X-Loop: zsh-workers@zsh.org Errors-To: zsh-workers-owner@zsh.org Precedence: list Precedence: bulk X-no-archive: yes List-Id: List-Help: List-Subscribe: List-Unsubscribe: List-Post: List-Owner: List-Archive: Archived-At: Sender: Sympa Owner Hello, I would like to apply some transformation to $BUFFER before and after editing it with `zle edit-command-line`. Modifying $BUFFER before editing is trivial, however the after part is a bit tricky since edit-command-line calls send-break. Currently I use the following workaround to being able to execute custom code: function send-break() { zle -D send-break unfunction send-break read -z BUFFER # ...do something with BUFFER... zle redisplay } zle -N send-break zle edit-command-line It works fine, so I’m wondering why `zle send-break` is used inside edit-command-line and whether `zle redisplay` could be used instead. -- zsugabubus