zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Shift-Insert overwrites ZLE CUTBUFFER
Date: Wed, 9 Nov 2016 09:27:45 -0800	[thread overview]
Message-ID: <161109092745.ZM2477@torch.brasslantern.com> (raw)
In-Reply-To: <43312.1477929414@hydra.kiddle.eu>
In-Reply-To: <20161031161605.23af1751@pwslap01u.europe.root.pri>

Moving this to -workers ...

On Oct 31,  4:56pm, Oliver Kiddle wrote:
}
} Associating it with the existing cut/paste features at least puts
} it in a logical and memorable place, at least once you're aware of
} the feature. And if you know about things like yank-pop or vi "0
} then it is not so likely to be bothersome. But I'd be open to
} something better.

On Oct 31,  4:16pm, Peter Stephenson wrote:
}
} I'm not particularly bothered either way, but $ZLE_PASTED suggest
} itself.

An idea that I just had, spawned in part by Oliver's change to
"print -v" behavior when the target variable is declared as an array:

If ZLE_PASTED has been declared, then the pasted text is copied there
instead of into CUTBUFFER.  If it's been declared as an array, it
acts similarly to $killring, i.e., the pasted text is unshifted to
the front and the last element is dropped.


       reply	other threads:[~2016-11-09 17:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMtVo_PG_fd62V1FZ4r7fRUragzzS6H4McN5sO1=hhY=6DR6Yg@mail.gmail.com>
     [not found] ` <161025091249.ZM7232@torch.brasslantern.com>
     [not found]   ` <CAMtVo_N6qOQr++Amzn11+m3pkOxjc908mwFUerur77+OWd92uw@mail.gmail.com>
     [not found]     ` <161026090133.ZM11120@torch.brasslantern.com>
     [not found]       ` <CAMtVo_P09j6fyJytA21iu_qOom6bCTvJEWn-dXTBX97Bp00Sdg@mail.gmail.com>
     [not found]         ` <161026165138.ZM12130@torch.brasslantern.com>
     [not found]           ` <87h97x36sa.fsf@lwm.klanderman.net>
     [not found]             ` <161027133523.ZM15655@torch.brasslantern.com>
     [not found]               ` <43312.1477929414@hydra.kiddle.eu>
     [not found]                 ` <CGME20161031160350epcas3p4849616fbcc05783a9966320a28ed731c@epcas3p4.samsung.com>
     [not found]                   ` <20161031161605.23af1751@pwslap01u.europe.root.pri>
2016-11-09 17:27                     ` Bart Schaefer [this message]
2016-11-10 16:21                       ` Oliver Kiddle
2016-11-10 17:17                         ` Bart Schaefer
2016-11-15 21:41                           ` Oliver Kiddle
2016-11-15 22:07                             ` Bart Schaefer
2016-11-17 16:53                               ` Oliver Kiddle
2016-11-18  3:16                                 ` Bart Schaefer
2016-11-20 22:32                                   ` Oliver Kiddle

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=161109092745.ZM2477@torch.brasslantern.com \
    --to=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).