From: Mikael Magnusson <mikachu@gmail.com>
To: Hadrien Lacour <hadrien.lacour@posteo.net>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: zle kill-region without mark consider start of line as mark
Date: Wed, 15 Nov 2017 18:10:29 +0100 [thread overview]
Message-ID: <CAHYJk3TPZ79brYzHsU0xd6QiVupVViRndWF1bq-s1RWD8rBzSg@mail.gmail.com> (raw)
In-Reply-To: <20171115131326.cazeuiazwmfy5dmh@gentoo.gentoo>
REGION_ACTIVE (integer)
Indicates if the region is currently active. It can be
assigned 0 or
1 to deactivate and activate the region
respectively. A value of 2
activates the region in line-wise mode with the
highlighted text
extending for whole lines only; see Character Highlighting below.
On Wed, Nov 15, 2017 at 2:13 PM, Hadrien Lacour
<hadrien.lacour@posteo.net> wrote:
> On Wed, Nov 15, 2017 at 02:00:47PM +0100, Hadrien Lacour wrote:
>> On Wed, Nov 15, 2017 at 11:24:37AM +0000, Peter Stephenson wrote:
>> > On Wed, 15 Nov 2017 11:40:34 +0100
>> > Hadrien Lacour <hadrien.lacour@posteo.net> wrote:
>> > > I have `bindkey -M emacs '^W' kill-region` in my zshrc and using it without
>> > > having set any mark will cut from the beginning of the line to the cursor.
>> > > I've tried to read zle's doc but found no mention of this behaviour.
>> > >
>> > > Any idea about what's happening and how to do nothing if the mark isn't set?
>> >
>> > Internally, there is actually no notion of the mark not being set ---
>> > it's simply initialised to zero, and moved when ask it to be set.
>> > Therefore, if you try and use it, it appears as if it's at the start of
>> > the line.
>> >
>> > The documentation doesn't make this explicit. It could do with
>> > mentioning the default state.
>> >
>> > pws
>>
>> Thanks, that's what I supposed too. I almost have it fixed with
>>
>> markset=
>> my-set-mark()
>> {
>> zle set-mark-command
>> markset=true
>> }
>>
>> my-kill-region()
>> {
>> [ $markset ] && zle kill-region
>> }
>>
>> zle -N my-kill-region
>> zle -N my-set-mark
>>
>> bindkey -M emacs '^@' my-set-mark
>> bindkey -M emacs '^W' my-kill-region
>>
>>
>> But I don't know how to reset markset every newline (other than doing an ugly
>> bindkey for Return).
>
> Disregard this, I just forgot to reset markset in the second widget.
--
Mikael Magnusson
next prev parent reply other threads:[~2017-11-15 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171115104211epcas1p297804141d5350c2100e76f849759952d@epcas1p2.samsung.com>
2017-11-15 10:40 ` Hadrien Lacour
2017-11-15 11:24 ` Peter Stephenson
2017-11-15 13:00 ` Hadrien Lacour
2017-11-15 13:13 ` Hadrien Lacour
2017-11-15 17:10 ` Mikael Magnusson [this message]
2017-11-15 18:00 ` Hadrien Lacour
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=CAHYJk3TPZ79brYzHsU0xd6QiVupVViRndWF1bq-s1RWD8rBzSg@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=hadrien.lacour@posteo.net \
--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).