From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Setting magic-space in /etc/zshrc
Date: Wed, 25 May 2016 13:22:27 +0200 [thread overview]
Message-ID: <CAKc7PVBXoKKqy5fjyOnNxFw43fXehN14kV0vKQDZL9i_ns4c7Q@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bGM2S7UB0fbGQbkVMDnZnh=o45ieKg__spMSS3fT3U5g@mail.gmail.com>
On 25 May 2016 at 12:42, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On May 25, 2016 10:12 PM, "Sebastian Gniazdowski" <sgniazdowski@gmail.com>
> wrote:
>>
>> When shell startups, it shows: " " magic-space. When I issue "bindkey
>> ' '", it shows self-insert.
>
> I'm not able to reproduce this on OSX with 5.0.2 or a recent build of
> 5.2-dev-1 (the only OS/versions I have accessable at the moment). If
> happening, this may have something to do with the emacs / vicmd keymaps
> selected automatically by examining the VISUAL / EDITOR environment
> settings, such that you are seeing/binding one keymap in /etc/zshrc and
> another later.
You are apparently right. I have bindkey -v. Removing it on Fedora
causes bindkey ' ' to display magic-space also after complete startup.
In the widget, I was creating own keymap by copying it from emacs. So
it had the /etc/zshrc influence in it. However, I was also doing some
checks while debugging: added bindkey ' ' to overriding self-insert
widget – shown self-insert. Added magic-space override – and it wasn't
called on space.
Best regards,
Sebastian Gniazdowski
prev parent reply other threads:[~2016-05-25 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 10:12 Sebastian Gniazdowski
[not found] ` <CAH+w=7Z1RTUK9Hft_cg3=-GTPo8+fxzKX_5CMcZQN1nGS3H-Cw@mail.gmail.com>
[not found] ` <CAH+w=7Zkvxrgi5KB-1oMSHpfL+j8whbL4meV7Yn=x1wmDai2wQ@mail.gmail.com>
2016-05-25 10:42 ` Bart Schaefer
2016-05-25 11:22 ` 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=CAKc7PVBXoKKqy5fjyOnNxFw43fXehN14kV0vKQDZL9i_ns4c7Q@mail.gmail.com \
--to=sgniazdowski@gmail.com \
--cc=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).