junegunn/vim-peekaboo

:eyes: " / @ / CTRL-R

vim-peekaboo

Peekaboo extends " and @ in normal mode and <CTRL-R> in insert mode so you can see the contents of the registers.

Installation

Using vim-plug:

Plug 'junegunn/vim-peekaboo'

Usage

Peekaboo will show you the contents of the registers on the sidebar when you hit " or @ in normal mode or <CTRL-R> in insert mode. The sidebar is automatically closed on subsequent key strokes.

You can toggle fullscreen mode by pressing spacebar.

Customization

Config	Default	Description
g:peekaboo_window	vert bo 30new	Command for creating Peekaboo window
g:peekaboo_delay	0 (ms)	Delay opening of Peekaboo window
g:peekaboo_compact	0 (boolean)	Compact display
g:peekaboo_prefix	Empty (string)	Prefix for key mapping (e.g. <leader>)
g:peekaboo_ins_prefix	Empty (string)	Prefix for insert mode key mapping (e.g. <c-x>)

License

MIT

vim-peekaboo's Issues

Prefix remapping prevent peekaboo from working

OS: MX Linux 17

NVIM v0.3.0-1029-g48967695c Build type: RelWithDebInfo.

Nvim configurations

I'd rather avoid shadowing @, which is used for macros, and remap the prefix to another key. I tried several in the format let g:peekaboo_prefix="<leader>2, but it had the effect of preventing peekaboo from working altogether.

Also for marks?

Hi,

Peekaboo is very convenient since it removes the need to remember what is stored in which register.
I think it would be very useful to have a similar mechanism for marks. Indeed marks are conceptually quite similar to registers, in the sense that there is a whole list of automatic and manual marks at different positions and it is often difficult to remember where every mark is located.
Do you think it would be possible to extend peekaboo (or create another plugin along the same concept), but with marks instead of registers?

Screenshot

Cannot read from register in insert mode with macro

What

Running a macro that does in insert mode to read from register does not work, and returns empty string - not contents of register.
Bug is only visible when running macro, not when recording it.

My setup

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 9 2014 22:01:23)
MacOS X (unix) version
Included patches: 1-488
Compiled by Homebrew
The settings in my vimrc (mappings and functions removed)
Tested without other plugins.
Cannot reproduce with peekaboo plugin disabled.

How to reproduce

Record a macro that reads from a register in insert mode like this:
<C-R><register>

So, with 'hello' in the " register, this command qqi<C-R>"<ESC>q, writes 'hello', and is working as expected.

The issue emerges when running the macro with @q.

Expected: hello is printed
Actual: nothing is printed, and the bell rings (visuall and sound bell from terminal)

Possibly related:
If you do exactly the same as above, but add after and before ", then the " will be written out instead of nothing.

Off topic trivia:
When using <C-R><register> in a macro, you will paste whatever was in the register at the time of recording.
When you use <C-R><C-P><register>, you will paste whatever is in the register when you run the macro.

screencapture tool used in README?

@junegunn the gifs you have in READMEs across your repos are very nice.

Specifically I'm thinking of these

• https://github.com/junegunn/vim-easy-align
• https://github.com/junegunn/vim-peekaboo (this repo, hence an issue here...)

What do you use? asciinema for example does not appear to support keypress overlays.

Thanks for any insight.

highlight default link peekabooSelected Todo a poor choice for many colorschemes

hi peekabooSelected cterm=reverse Would work with most colorschemes (but not look as good probably, but i am running into cases when the selected register renders black on black with many themes. Maybe drop the highlight group completely?

@ only works for the first time

If I press @ap, the peekaboo window will show. However, after that, the " and @ will fail to work. No window will show.

No trigger for <c-r> in command mode

Peekaboo doesn't trigger on ctrl+r in :command mode.

Temporarily disabling peekaboo when dealing with extremely large registers

Hi, while using peekaboo I've hit problems when one of the registers contains a lot of data, is there a way to temporarily disable peekaboo?

Release 0.1?

Hi. Peekaboo looks fascinating. Can I get a git tag so I can send my package managers to pull the plugin with a version number? Tyvm sir

Plugin blocks Mappings that include double quote character (")

Hi,

I love your plugin, but my mappings such as

nmap <M-o> "+gP
imap <M-o> <ESC>"+gP

No longer work because your plug-in changes the double quote character. Is there a way around this?

Thanks!

Calling shell command on InsertEnter autocmd event hinders peekaboo

Here is a minimal .vimrc to show problem case:

" minimalvimrc
set nocompatible

" Add vim-peekaboo repository to runtime path.
set runtimepath+=/tmp/vim-peekaboo
runtime! 'plugin/vim-peekaboo.vim'

augroup foobar
  autocmd!
  " `silent! !true` provokes the same behavior.
  autocmd InsertEnter * silent! call system('true')
augroup END

Run vim -u minimalvimrc, then enter insert mode and press <C-r>0 (or insert any other register). For me, it doesn't output register content, but inserts <Plug>(pkbcr)0.

Question: format for g:peekaboo_window

My apologies for asking this question here, but I couldn't find how to configure the position of the peekaboo window. I noticed the setting g:peekaboo_window but it's not clear to me what format I should use for that.

I wanted to make the peekaboo_window show up at the top in a horizontal split, so my failed attempt was:

let g:peekaboo_window='split topleft'

thanks

Using expression register in an abbreviation fails

The following abbreviation is broken when using vim-peekabo.

iabbr tdate <c-r>=strftime("%Y-%m-%d")<cr>

When vim-peekaboo is installed, the text inserted is literally strftime("%Y-%m-%d").

gvim window shrinking

As my peekaboo window opens and closes my gvim window slowly get more and more narrow. There a resize happening that is causing my window to shrink

can this be made to work for C-r in cmode?

I guess there is some reason why it's not already mapped to cmode or you would have already done so. But just double checking.

I naively tried:

cnoremap call peekaboo#peek(1, 'ctrl-r', 0)

and the sidebar shows up, but not sure how to go on. Needless to say, my knowledge of viml is limited to let this and let that...

neovim: i_CTRL-r at end of line broken

I've noticed that with Neovim, (e.g. <c-r>*) in insert mode at the end of line will insert the register not at the end, but one character before it.

foo_
=> fobar_o

Can you confirm this?

Strange behaviour with register in macro, normal mode

This is a nasty one. And I'm not even sure of what is going on.

What

Special sequence of commands, involving moving a line up/down, pasting from a specified register, and moving back, produces strange output.

My setup

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Nov 9 2014 22:01:23)
MacOS X (unix) version
Included patches: 1-488
Compiled by Homebrew
The settings in my vimrc (mappings and functions removed)
Tested without other plugins.
Cannot reproduce with peekaboo plugin disabled.

Macros that trigger the bug

These produce the exact same output when peekaboo is enabled.
Should paste a word under the cursor

• o^[""pk
• $a^M^[""pk
• j""pk
  Should paste a word over the cursor
• k""pj

How to reproduce

1. Fill the " register with the word YES
2. Record this macro o^[""pk, or one from the list above (or just yank it into the q register)
3. Go to the start of a line with text on (text makes it easier to see, but is not required)
4. Run the macro

Expected:

some text that was here before
YES

Actual:

sYESome text that was here before
(empty line inserted from the  o-command, if you used the macro with an o-command)

Notes:
The bug does occur for other registers than the one used in the example.
The bug does not occur if you paste without specifying register with ".
The bug does not occur if you don't move back to the starting line. So this macro does not trigger it: k""p (the same as the last macro in the list of macros, but without the j for returning to the line).

Pasting ignores the space before the cursor

fmt.Println("|string") // ya"
test :=⋅| //<C-r>" // middle dot denotes a space here
--- Result:
test :="string"⋅ // note the middle dot's position, denoting a space
--- Expected:
test :=⋅"string"

Window is being resized when pasting in insert mode

Hi, thanks a lot for this plugin. The solved issue #61 allows me to use this plugin again...

Often, when I paste in insert mode (ctrl+r<register>p), I get the window resized to one line:

I can't get a pattern for that, So I don't know how to reproduce it, but it happens very often when pasting in insert mode. I don't have this problem when pasting in normal mode.

I'm using nvim 0.4.3. This was not a thing until 0.4.1

pasting in the expression register `"=`

If I enter in the expression register "=, either by doing <C-R>= in insert mode or "= in normal mode, and then try to paste something, as soon as I press ", the text Peekaboo is written on the commandline, and I can't paste anything unless I do the workaround of entering the commandline window with <C-F>.

Register 0 is shown wrong

Register 0 is shown wrong in the peekaboo window.

https://github.com/junegunn/vim-peekaboo/blob/master/autoload/peekaboo.vim#L32

This is caused by Vim's string equality, 0 == '%' is true. So for register 0, register '%' is printed instead. This can be fixed by checking that the register is a Number or using a regex.

Breaks the repeat/dot command (e.g. with `ciw<C-r>a`)

A command like ciw<C-r>a cannot be repeated with the . (dot) command.

It behaves like i<C-r>a<Esc>.

This might get fixed by using https://github.com/tpope/vim-repeat?!

Vim / Neovim install error / solution

Issue: Failed to install in Vim (Neovim) using the approach listed.

Aside:

## Symlinks (to use Vim settings with Neovim):
ln -s ~/.vim ~/.config/nvim
ln -s ~/.vimrc ~/.config/nvim/init.vim

Solution: I manually recreated the autoload | plugin | syntax directory structure shown at https://github.com/junegunn/vim-peekaboo in /home/victoria/.vim/ (copied raw files/code to those locations).

In my case, I needed to create the /home/victoria/.vim/plugin/ and /home/victoria/.vim/syntax directories.

[victoria@victoria .vim]$ tree -L 2 -F ~/.vim -I 'bundle*|init*|readme*|spell*|swap|undo|view|vim*'
/home/victoria/.vim
├── autoload/
│   ├── pathogen.vim
│   └── peekaboo.vim
├── plugin/
│   └── peekaboo.vim
└── syntax/
    └── peekaboo.vim

when this plugin be loaded lazy will occur some problem

	call dein#add('junegunn/vim-peekaboo', {
				\ 'on_map': ['"', '@'],
				\ })

when type '@' or '"', nothing will occur. utill user :edit to refresh, the plugin will work.

Thank you!

<C-r> broken in macros

e.g.

hello world

qqVyo<c-r>"<esc>k

hello world
hello world
<blank line>

@q

Expected:

hello world
hello world
hello world
<blank line>
<blank line>

Actual

hello world
hello world
<blank line>
<blank line>
<blank line>

C-R doesn't work with visual block

Pastes :call peekaboo#peek(1, 'ctrl-r', 0) into the file.

vsplit same buffer: unpredictable paste in insert mode

I often edit the same buffer in vertical split. When I try to paste in insert mode CTRL+R, while in the right pane, the cursor jumps to left pane, and pasted word appears in random area.

Here I try to delete word del to paste()

Here my cursor in between parens: paste(|), while in insert mode I press CTRL+R+-

The result:

Open peekaboo in current window

Hi,

Firstly, just want to say that I really love this plugin, it's a great idea and seems to be very well implemented. Thank you!

The issue that I'm having is that I'd like to open the peekaboo window in the current buffer window instead of in a separate split. I've attempted to use the g:peekaboo_window variable, but couldn't figure out how to do anything with it other than split windows.

Is it possible to achieve this with the plugin as it exists?

If not, it's a feature that I'd really like, as opening a split if often not desirable on wide monitors. I understand you might not have the time / desire to do this, in which case I'd be happy to fork it and attempt to implement it myself.

Thanks

Replacing :reg with Peekaboo panel?

Is this possible? Is there a function that can be called to do this? Thanks

Folded text if foldmarkers in registers

If the any text in in the registers has fold markers, some or most of the buffer ends up folded away.

Suggestion: setlocal foldlevel to something very high, so it is always open.

How to unmap @?

I did not pay attention.

For anyone using this plugin for the first time: you have the recording in the peekaboo menu.
So, you can still use recording like you normally do.

Cheers

Bug when combined with Limelight

Thanks for these great Vim plugins.

Unfortunately when I combine Limelight as an autocmd on .txt files and then use Peekaboo, if there's something already on the line I'm pasting to, the paste goes to the start of the line (which is very impractical).

Not sure what's causing the problem.

Interferes with expression register

For instance, my vimrc contains

iabbrev ddate <C-R>=strftime(%F")<CR>

to insert the current date. Vim-peekaboo captures the and prevents this from working. Is there a good way to work around that conflict?

relativenumber needs to be disabled in the peekaboo window

Currently nonumber is set to disable line numbers, however if relativenumber is normally set then the peekaboo window will contain numbers.

Adding norelativenumber to the set of local buffer options fixes this.

Space Wasted by Leading Spaces

Like the img above, when working with lines with leading spaces much of the space would be wasted.

It would be cool to trim the leading spaces.

It is possible to disable (unmap) @ ?

canceled :)

Option to zoom window

Is there a way to temporarily maximize the view, perhaps by pressing a key that would never be used following " or @ (maybe <SPACE>)?

Error when loclist is open

Hi!

I get the following error when using peekaboo with an open loclist (opened by syntastic).

The peekaboo scratch buffer opens as expected, when pressing ", put as soon as i select a register, the cursor jumps to the loclist and i get the error in the screenshot.

Unfixable issues

Hello,
First of all thank you so much for this amazing plugins, it is one of my favorite plugins.

In different opened issues you mentioned that some issues are unfixable. Specifically you said: here #32 "I have learned from my experience that overriding the default behavior of Vim leads to many subtle issues that are very difficult or even impossible to fix".

I'm really interested in learning how you achieve this, and maybe use this popup for multiple things like commands I rarely use and can't really remember, like 'z..'. Can you explain exactly what is the problem?

For example would using floating windows in neovim help with this?

Thank you for everything

<C-r> mappings gets inserted literally with/in "Visual-block Insert" mode

When using Visual-block Insert (CTRL-V from normal mode, select a region, then I), the <C-r> mapping does not work: it enters the right hand side literally:

:call peekaboo#peek(1, 'ctrl-r',  0)

Plugin regularly (but unpredictably) crashes neovim

I'm using nvim v0.4.3 (also tested with git master), and with this plugin enabled, pressing " often (but not always) causes neovim to completely lock up. If I'm using the QT GUI, the mouse cursor changes to busy, and the application completely freezes. It doesn't respond to any keypresses or mouse clicks, and usually has to be killed with SIGKILL, as SIGTERM doesn't seem to do anything either.

(Feature) Disable labels and padding

That would add like 7 more lines on the screen, so more fits on small screens.

Looking for a suggestion when running a macro on a bunch of lines

I love using this plug-in, but sometimes I might be doing a thing like:

:'<,'>normal @q

And so as this runs on every line I have to see the peekaboo panel toggle open and closed every time it executes the @q.

Do you have any suggestions for how you might handle a thing like this? I'm thinking maybe I should just have a function that I can call to toggle peekaboo on/off.

Not sure, though.

":'<'>normal q@" hangs

1. Record a simple macro: qq0fe~q
2. Visually select a few lines: Vjjj
3. Play back the macro on the selected lines: :'<,'>normal @q

Vim version 7.4.692 hangs.

Register name gets inserted into current buffer, Neovim 0.4.2

This is a really weird thing I've started seeing lately, I'm guessing since I updated to Neovim 0.4.2. Say I have this buffer. I've selected the second "something" and I want to copy it:

When I type the ", Peekaboo appears as normal. Then if I type + to choose the system clipboard register, this happens:

It always seems to be the second word in the fourth line where this happens. The highlighted region is using the peekabooSelected highlight group. The selected item does get yanked to the correct register, but now I have an errant + in my buffer.

Any ideas would be appreciated. This is really strange!

Cmap for <Plug>(pkbcr)

Peekaboo is able to integrate with Cmd2.vim to allow Peekaboo to be called in command mode.

The only missing thing is that <Plug>(pkbcr) is not cnoremap-ped. Is it possible to put this as a default mapping to allow for a seamless integration?

Vim register is full of '../' I think it is netrw but could it be peekaboo?

Sorry I swear I am going to stop logging issues on all of your awesome plugins after this one.

Basically when I show the peekaboo register it is full of ../ and ../../ it gets worst after using netrw

Any ideas, could be related to this: kien/ctrlp.vim#648

I have disabled any lines related to my clipboard.

Cheers.
Otis.

Peekaboo breaks commandline window

If you enter the commandline window (with q: or :) and then try to paste something there, you get this series of errors:

For the time being I am fixing this by setting a delay for peekaboo, but I thought you could implement in the commandline window the same behavior it has on the commandline, namely, be inactive.

Thanks for the great plugin!

Open peekaboo window only after some timeout

When you know exactly what register to use, peekaboo gets in the way (visually, but might also "eat" some keys).

It would be nice if it could be deferred, e.g. until CursorHold or something similar is triggered - given the limited async capabilities Vim has.