From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Extending zed
Date: Mon, 4 Jun 2018 10:50:42 +0100 [thread overview]
Message-ID: <20180604095044eucas1p2ae6dd78f9518e91e6171d15d3717f924~07CtDwS5C1968619686eucas1p2k@eucas1p2.samsung.com> (raw)
In-Reply-To: <CAKc7PVCV3TCe4k-SyJOiD6aDA+uF5FRM_5Q45X9sLPOeCOunWA@mail.gmail.com>
On Mon, 4 Jun 2018 11:41:56 +0200
Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> Zed always gives me impression that I will touch something improper
> and break the function or file I'm editing. Maybe we could set up few
> things that will make zed more predictable? The page-up, page-down are
> good example, before those binding the keys were calling history and
> really breaking the viewport. Currently "u" key doesn't do undo and
> breaks viewport, could I bind it? I would send a patch. Also, would it
> be possible to implement ESC:wq, i.e. regular way of leaving vim-like
> editor.
bindkey extensions ought to be unproblematic --- you'll see there's
already a zed keymap which binds ^x^w to accept-line.
What we really need is to separate that out so we can set up a default
keyboard and map early before zed actually runs, giving the user the
opportunity to override it. Perhaps this could be a zed-setup function
that zed will call itself if it hasn't yet been run.
pws
next prev parent reply other threads:[~2018-06-04 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180603055854epcas5p1e92f5a41384aeb9d1555751df74f57ee@epcas5p1.samsung.com>
2018-06-03 5:57 ` Sebastian Gniazdowski
2018-06-04 8:37 ` Peter Stephenson
2018-06-04 9:41 ` Sebastian Gniazdowski
2018-06-04 9:50 ` Peter Stephenson [this message]
2018-06-04 10:17 ` Sebastian Gniazdowski
2018-06-04 16:08 ` Oliver Kiddle
2018-06-05 14:40 ` Sebastian Gniazdowski
2019-07-28 11:01 ` Sebastian Gniazdowski
[not found] ` <20180604105042.69c54bee@camnpupstephen.cam.scsc.local>
2018-06-04 9:56 ` Peter Stephenson
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='20180604095044eucas1p2ae6dd78f9518e91e6171d15d3717f924~07CtDwS5C1968619686eucas1p2k@eucas1p2.samsung.com' \
--to=p.stephenson@samsung.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).