zsh-users
 help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: multiple kill are not yanked together
Date: Tue, 11 Jan 2022 22:53:19 +0100	[thread overview]
Message-ID: <CAP+y1xCmChEPCTFs_A5puLqjg5ys_yNaM8ccZz1A02n8K2gEHg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7aH_6QDAaoRUUZWAgkyoqiO2qZBZ_PsPFPWQwVWbKL+-A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]

Il giorno mar 11 gen 2022 alle 22:28 Bart Schaefer <
schaefer@brasslantern.com> ha scritto:

> On Tue, Jan 11, 2022 at 9:36 AM Pier Paolo Grassi <pierpaolog@gmail.com>
> wrote:
>
>> Hello, is there some information I can provide about this question?
>>
>
> Version of zsh?
>

zsh 5.8 (x86_64-pc-linux-musl)
it's the version provided  by Roman


> Are you ever able to get this to happen starting from "zsh -f" + compinit?
>
>
no, in this case it works as expected


> Does this happen e.g. after performing completion on one of the words you
> then kill?
>

it happens right after opening a new shell


>
> Oliver would be the most likely person to have insight here, but he's
> unavailable for several days right now.
>
> Il giorno mar 11 gen 2022 alle ore 00:10 Pier Paolo Grassi <
>> pierpaolog@gmail.com> ha scritto:
>>
>>> Hello, it is sometimes that I have this behaviour:
>>> when I use repeatedly a zle widget like kill-word and then I use yank to
>>> restore the killed text, only the last killed word is returned.
>>> I remember that all the consecutive killed word were returned at once,
>>> and the manual support this:
>>> [...] When repeatedly invoking a kill widget, text is  appended  to  the
>>>  cutbuffer instead of replacing it[...]
>>> Is it possible I deactivated this behavior somehow?
>>>
>>
> I don't know of any way to "deactivate this" other than by changing key
> binding or widget definitions.
>

The key bindings for these widgets are simply
bindkey \Cd kill-word
bindkey \Cy yank

I somehow have discovered a way, it seems... now I have to try to
understand which config line is causing it
I will update this thread if I make any progress, thanks

[-- Attachment #2: Type: text/html, Size: 3633 bytes --]

  reply	other threads:[~2022-01-11 21:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 23:10 Pier Paolo Grassi
2022-01-11 17:36 ` Pier Paolo Grassi
2022-01-11 21:28   ` Bart Schaefer
2022-01-11 21:53     ` Pier Paolo Grassi [this message]
2022-01-11 23:29       ` Pier Paolo Grassi

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=CAP+y1xCmChEPCTFs_A5puLqjg5ys_yNaM8ccZz1A02n8K2gEHg@mail.gmail.com \
    --to=pierpaolog@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    --subject='Re: multiple kill are not yanked together' \
    /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

Code repositories for project(s) associated with this 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).