zsh-users
 help / color / mirror / code / Atom feed
From: Frank Schwidom <schwidom@gmx.net>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Roman Perepelitsa <roman.perepelitsa@gmail.com>,
	Mikael Magnusson <mikachu@gmail.com>,
	Frank Schwidom <schwidom@gmx.net>, Zsh Users <zsh-users@zsh.org>
Subject: Re: Hi, can someone help me to convert my bash PS1 to zsh?
Date: Tue, 22 Mar 2022 01:36:48 +0100	[thread overview]
Message-ID: <20220322003648.GA8493@debian64> (raw)
In-Reply-To: <CAH+w=7bsS6Hh7n3M9ZCBtVjcjGk+3W16FpYJc-7n1ChSDCys5w@mail.gmail.com>

On 2022-03-21 14:43:50, Bart Schaefer wrote:
> On Mon, Mar 21, 2022 at 2:14 PM Roman Perepelitsa
> <roman.perepelitsa@gmail.com> wrote:
> >
> > vi mode is as simple as `bindkey -v`.
>
> That doesn't automatically include the (ins) indicator in the prompt,
> though, which seemingly the \$ escape in bash does?
>

No, this is the dollar sign. The (ins) and (cmd) flags are provided by the readline library.

The flag appears on the left side of the last line.
I cannot change it.

I guess zsh don't use readline. But it takes over the settings for the vi keybindings after I startet it from bash. I don't know the exact mechanism.

The readline config at the end of /etc/inputrc is:

set editing-mode vi
set completion-prefix-display-length 1
set show-mode-in-prompt on

The variable 'show-mode-in-prompt' is responsible for this flag.

Regards.



  reply	other threads:[~2022-03-22  0:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 16:06 Frank Schwidom
2022-03-21 16:57 ` Mikael Magnusson
2022-03-21 17:47   ` Frank Schwidom
2022-03-21 17:59     ` Mikael Magnusson
2022-03-21 18:51       ` Roman Perepelitsa
2022-03-21 21:43         ` Bart Schaefer
2022-03-22  0:36           ` Frank Schwidom [this message]
2022-03-21 18:11     ` Bart Schaefer
2022-03-21 18:17       ` Frank Schwidom
2022-03-21 18:56     ` Lawrence Velázquez

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=20220322003648.GA8493@debian64 \
    --to=schwidom@gmx.net \
    --cc=mikachu@gmail.com \
    --cc=roman.perepelitsa@gmail.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).