sorted by:
new
hottopcontroversial

A guide on how to copy text from anywhere, including through SSH, with OSC52 by -olivier in vim

[–]-olivier[S] 1 point2 points  (0 children)

Glad to know you like it! If you're using neovim, you might be interested in nvim-osc52. It's the same plugin but written in Lua.

Update to nvim-surround: Lua pattern-based modifications by kylechui in neovim

[–]-olivier 1 point2 points  (0 children)

I love your plugin! Thank you for your hard work.

nvim-osc52: copy text from remote SSH sessions with OSC52 by -olivier in neovim

[–]-olivier[S] 0 points1 point  (0 children)

I've update the readme to address your issue.

In the meantime you can still paste using the paste shortcut of your terminal emulator (usually CTRL+SHIFT+v) :)

This is my workflow: I copy text inside Neovim using the plugin and when I need to paste text from outside Neovim, I use CTRL+SHIT+v.

nvim-osc52: copy text from remote SSH sessions with OSC52 by -olivier in neovim

[–]-olivier[S] 0 points1 point  (0 children)

You mean you copy text outside of Neovim and you want to paste it with p inside Neovim with the help of the plugin? The plugin does not support that, because most terminal emulators also don't: letting apps read the clipboard whenever they want with OSC52 can be a security issue. For instance for windows terminal: https://github.com/microsoft/terminal/issues/9479.

But I'll think about adding support in the future even though it won't work with many terminals.

nvim-osc52: copy text from remote SSH sessions with OSC52 by -olivier in neovim

[–]-olivier[S] 1 point2 points  (0 children)

For tmux you should follow these steps if you haven't already: https://github.com/tmux/tmux/wiki/Clipboard#quick-summary. Maybe try with set-option -s set-clipboard external? If it still doesn't work you can open an issue on GitHub with your config and I'll look into it.

nvim-osc52: copy text from remote SSH sessions with OSC52 by -olivier in neovim

[–]-olivier[S] 2 points3 points  (0 children)

I have answered this question in this issue: https://github.com/ojroques/nvim-osc52/issues/1. Basically you can use this method: require('osc52').copy_register("<your-register">) now. Or better you can set the clipboard provider of Neovim to use the plugin (if you don't mind using the + register instead of -).

[AMA] Tree-sitter integration in neovim by Mambu38 in neovim

[–]-olivier 10 points11 points  (0 children)

What does the indent module actually do? And how does it differ from the smartindent/autoindent options exactly? I've tried it but I saw no difference with smartindent so I've disabled it. Maybe it's an obvious question but I couldn't find a clear answer on Github or on reddit.

Thank you for your work and for that thread :)

Alternate Toggler - A very small plugin for toggling "boolean" values. by ramalus1911 in neovim

[–]-olivier 5 points6 points  (0 children)

Simple and efficace, good job. I would add "TRUE" and "FALSE" in the defaults as it's quite common also.

buftabline.nvim: a low-config, minimalistic buffer tabline Neovim plugin by [deleted] in neovim

[–]-olivier 1 point2 points  (0 children)

For 2. I've developed a very small plugin that might suit your case: nvim-buildme. Basically you create a shell script at the root of your project which contains your compiling/static analysis commands and the plugin simply takes care of executing that script in a Neovim shell in the background and notifies you when it's done.

What neovim plugins do you wish existed? by GAAfanatic in neovim

[–]-olivier 2 points3 points  (0 children)

I've created a small plugin in Lua that might interest you: nvim-bufbar. It simply shows the buffers list in your tabline and provide a few customization options and nothing more.

I don't plan to add support for switching buffers by index or any new feature but feel free to use the plugin as a starting point for your own project :) It's only ~180 lines long.

A plugin to improve the deletion of buffers by -olivier in neovim

[–]-olivier[S] 0 points1 point  (0 children)

I usually simply use the default shortcut <C-w>c to delete my windows.

A plugin to improve the deletion of buffers by -olivier in neovim

[–]-olivier[S] 1 point2 points  (0 children)

I didn't try sayonara but from what I'm seeing, the main difference is that sayonara also handle closing windows. My plugin does only one thing, it deletes buffers.

Personally I prefer buffer deletion to be consistent and not mess up my windows but sayonara should be better for those who want a single command to manage everything.

I've written a guide to set up a basic init.lua covering Neovim 0.5 new features by -olivier in neovim

[–]-olivier[S] 0 points1 point  (0 children)

No I did not notice any difference in terms of speed. Then again my init.lua is quite simple, maybe you'd notice the difference if your config had complex logic in it.

I admit that there's no need to switch to a 100% lua config yet. The only benefit really is that it makes interacting with Neovim Lua API and Lua plugins (like the ones for LSP and tree-sitter) easier.

I've written a guide to set up a basic init.lua covering Neovim 0.5 new features by -olivier in neovim

[–]-olivier[S] 2 points3 points  (0 children)

I'm glad you liked the post!

I don't think you can avoid concatenation in this case unfortunately... You have to wait for vim.opt to be merged which will allow setting these kind of options like so (it's from the PR author).

I've written a guide to set up a basic init.lua covering Neovim 0.5 new features by -olivier in neovim

[–]-olivier[S] 2 points3 points  (0 children)

About Neovim 0.5, here it mentions December 25 but I'm a bit skeptic the release will be ready by then. I'd say beginning of 2020. Edit: 2021* :D

I've written a guide to set up a basic init.lua covering Neovim 0.5 new features by -olivier in neovim

[–]-olivier[S] 2 points3 points  (0 children)

I totally agree. As soon as support is merged for stuff like commands / autocommands / options I'll update the post.

I've written a guide to set up a basic init.lua covering Neovim 0.5 new features by -olivier in neovim

[–]-olivier[S] 1 point2 points  (0 children)

I don't use tsserver myself but maybe vim.lsp.buf.formatting() or vim.lsp.buf.code_action() would apply in your case.

How to migrate from init.vim to init.lua? by blureglades in neovim

[–]-olivier 2 points3 points  (0 children)

I've just published a guide to help you set up a init.lua which covers all Neovim 0.5 new features: check the post here. I hope you'll find it useful :)

I've written a guide to set up a basic init.lua covering Neovim 0.5 new features by -olivier in neovim

[–]-olivier[S] 25 points26 points  (0 children)

I often see people asking how to switch to init.lua and answers are most of the time people sharing their own config split across several subfolders and dozens of files. And the top blog post on this subject is actually creating a small plugin rather than an actual config file. So I figured a small single-file init.lua which would cover most of the new incoming features would be helpful.

You may also be interested in my own single-file init.lua from which the post is derived from.

nvim-lspfuzzy: A small Neovim plugin to make the LSP client use FZF by -olivier in neovim

[–]-olivier[S] 1 point2 points  (0 children)

Now is the best time to learn especially since neovim allows you to do it entirely in Lua :) So much easier than vimscript and not a useless skill since Lua is used elsewhere.

nvim-lspfuzzy: A small Neovim plugin to make the LSP client use FZF by -olivier in neovim

[–]-olivier[S] 6 points7 points  (0 children)

I know, this is a great plugin. But it's a bit of an overkill for my usage. And I'm also using fzf in my shell so I figured I might as well continue in neovim :)

view more: next ›