From: Muhmud Ahmad <muhmud.ahmad@googlemail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Prevent new line when using edit-command-line
Date: Mon, 8 Nov 2021 21:54:09 +0500 [thread overview]
Message-ID: <CALbcwMnvgg94-dj8T7Vzvx9oG_qjBCdG6=RLoP4RBWLmN7HM_g@mail.gmail.com> (raw)
In-Reply-To: <CALbcwMnMWoyOeL2y83GHUBY8LgUQNvLc_14TYsB4wmr8LqUpmA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
I meant "zsh -f"
On Mon, 8 Nov 2021 at 21:53, Muhmud Ahmad <muhmud.ahmad@googlemail.com>
wrote:
> Just tried this with "zfs -f", and I still get the same behaviour. I'm
> definitely at a PS1 prompt, I'm triggering the editor before I type
> anything on the current line at all.
>
> My zsh version is 5.8 (x86_64-pc-linux-gnu)
>
> On Mon, 8 Nov 2021 at 21:46, Bart Schaefer <schaefer@brasslantern.com>
> wrote:
>
>> On Sun, Nov 7, 2021 at 11:18 PM Muhmud Ahmad
>> <muhmud.ahmad@googlemail.com> wrote:
>> >
>> > Is there anyway to stop this behaviour, and just have my command on the
>> same line where I started the editor?
>>
>> I'm not able to reproduce this at the PS1 prompt, that is, for me the
>> buffer is restored at the current prompt. At the PS2 prompt, starting
>> a new PS1 prompt is unavoidable because the existing ZLE "session" has
>> to be restarted in order to merge the previously-entered lines
>> ($PREBUFFER) with the current line ($BUFFER).
>>
>
[-- Attachment #2: Type: text/html, Size: 1722 bytes --]
next prev parent reply other threads:[~2021-11-08 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 7:17 Muhmud Ahmad
2021-11-08 16:46 ` Bart Schaefer
2021-11-08 16:53 ` Muhmud Ahmad
2021-11-08 16:54 ` Muhmud Ahmad [this message]
2021-11-08 17:56 ` Bart Schaefer
2021-11-08 19:14 ` Muhmud Ahmad
2021-11-08 22:29 ` Pier Paolo Grassi
2021-11-08 23:05 ` 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='CALbcwMnvgg94-dj8T7Vzvx9oG_qjBCdG6=RLoP4RBWLmN7HM_g@mail.gmail.com' \
--to=muhmud.ahmad@googlemail.com \
--cc=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).