From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: zle-line-finish behavior and documentation
Date: Thu, 21 Jan 2016 11:04:49 -0800 [thread overview]
Message-ID: <160121110449.ZM25615@torch.brasslantern.com> (raw)
In-Reply-To: <20160121124620.GB21104@cventin.lip.ens-lyon.fr>
On Jan 21, 1:46pm, Vincent Lefevre wrote:
}
} OK, but if the goal is to reset the previous prompt, that's too late.
I guess the assumption was that if you're aborting the line there's no
reason to update the previous prompt.
} There would also be other two problems:
} 1) $ZLE_LINE_ABORTED gets empty when one does Ctrl-C on an empty line.
} 2) $ZLE_LINE_ABORTED is not reset when a command line is not aborted.
Hmm. I think it *should* work to do e.g. this:
zle-line-init() {
(( $+ZLE_LINE_ABORTED )) && RPS1=ABORT || unset RPS1
unset ZLE_LINE_ABORTED
zle reset-prompt
}
And indeed ZLE_LINE_ABORTED is set-but-emtpy after an interrupt on a blank
command line, and is unset after an accept-line. For some reason, though,
reset-prompt doesn't redraw the right prompt until the second consecutive
interrupt.
The PS1 prompt does get updated on reset-prompt, it works with:
PS1="%1v$PS1"
zle-line-init () {
(( $+ZLE_LINE_ABORTED )) && psvar[1]='ABORT ' || psvar[1]=''
unset ZLE_LINE_ABORTED
zle reset-prompt
}
next prev parent reply other threads:[~2016-01-21 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 14:56 Vincent Lefevre
2016-01-15 2:22 ` Bart Schaefer
2016-01-21 12:46 ` Vincent Lefevre
2016-01-21 19:04 ` Bart Schaefer [this message]
2016-01-22 1:32 ` Vincent Lefevre
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=160121110449.ZM25615@torch.brasslantern.com \
--to=schaefer@brasslantern.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).