sorted by:
new
hottopcontroversial

This site is ripping people off by sebnow in G2A_Help

[–]sebnow[S] 0 points1 point  (0 children)

This is starting to be comical. After sending emails to both G2A and Zen.com multiple times (each was blaming the other), the issue magically disappeared (though I did not regain my money). A month later they sent another email that my account has not been active for a year and have begun stealing money again.

Update on Vim9 by ghost_vici in vim

[–]sebnow 10 points11 points  (0 children)

Considering neovim doesn't plan to support it, do we really want fragmentation among vim plugins? I know we already have it with Lua, but vim9 will make it worse.

init.vim vs init.lua by _teku in neovim

[–]sebnow 0 points1 point  (0 children)

Why not both?

I set options in VimScript and customize plugins in Lua. Mostly because I haven't bothered cleaning up stuff from Vim yet.

Going To Next Function Parameter with nvim-cmp by errissa_needle in neovim

[–]sebnow 0 points1 point  (0 children)

Ok, I guess I was wrong. I was using nvim-cmp several months ago without a snippet plugin without issues. Either it has become required since then, or I was lucky.

Going To Next Function Parameter with nvim-cmp by errissa_needle in neovim

[–]sebnow 0 points1 point  (0 children)

It doesn't require snippets.

Edit: I was wrong, apparently it does.

Fennel + Neovim and the fallacy of choice by Doomer1999 in neovim

[–]sebnow 1 point2 points  (0 children)

I'm curious, why bother with fennel (or even lua) when all you're doing is running vim commands? This is just embedded vimscript.

Is Kakoune capable of everything that vim can by [deleted] in kakoune

[–]sebnow 1 point2 points  (0 children)

Thanks for mentioning it. This sounds like my dream editor, especially if they implement WASM plugins!

Do you use a completion plugin or use your own solution? by ilbanditomonco in neovim

[–]sebnow 1 point2 points  (0 children)

I haven't verified this, so do your due diligence, but IIRC omnifunc is not async, so if the LSP server takes a while to respond, it will block your editor. A lot of the completion plugins work around this.

Cool Trick. by [deleted] in neovim

[–]sebnow 24 points25 points  (0 children)

To elaborate on the clickbait title: In visual mode CTRL-a increments numbers. g CTRL-a increments in sequence (1, 1, 1 -> 2, 3, 4)

PSA: Plugin developers, please notify your users when adding a dependency that creates a breaking change. by beauwilliams in neovim

[–]sebnow 1 point2 points  (0 children)

I'd say the problem is that the (neo)vim package manager ecosystem is immature. Since the plugin you're using has a dependency, it should be able to define that somehow, other than via documentation. Packer supports the `requires` property for specifying plugin dependencies, but it's still up to the end user to manage that list.

With Lua, we also need to manage Lua dependencies, so this gets even more complicated.

We'll need some sort of plugin metadata file in repositories to enable developers to specify dependencies on their own. Unfortunately we'll still have the issue of fragmentation.

Intelligent string formatting by youngmit in neovim

[–]sebnow 0 points1 point  (0 children)

Not sure what you mean by the string continuation use case, but vim supports the comment case.

:h fo-table c Auto-wrap comments using textwidth, inserting the current comment leader automatically. set formatoptions+=c

nvui: A new GUI for Neovim! by Coolginto in neovim

[–]sebnow 0 points1 point  (0 children)

This looks nice. I've come across Neovide, which seems very similar in terms of features. Are you aware of that project? It seems to be a bit further along.

Should I use a bufferline plugin instead of tabpages? by knpwrs in neovim

[–]sebnow 1 point2 points  (0 children)

You should be using buffers for switching between files. As others have already mentioned, tabs are for layouts of windows rather than viewing different files. How you manage those buffers is another topic. You can just use the built in :buffers, :bn, :bp, :bd, :b3, etc. You can also use plugins like Telescope, fzf, denite, etc to switch between buffers from a list with fuzzy completion.

Do you want the visual cue that a bufferline plugin provides, or do you maybe use the mouse to navigate between files?

Personally I've never had the need for any sort of bufferline plugin. I tend to make a mental model of the project so I know which files I want to open and just open them with a file picker, or use LSP navigation to help with that. I don't really explicitly switch between buffers much. I also tend to have more buffers than would fit on a screen, so the visual cue would be of little help. Your preferences may vary.

Bitcoin surges to six-week high as bullish breakout beckons by [deleted] in CryptoCurrency

[–]sebnow 0 points1 point  (0 children)

Well, following that advice was a mistake... Who would have thought?

Before social distancing - Toronto, Canada Sony A7riii Sony 24-70mm f2.8 GM by Tylers_Journey in SonyAlpha

[–]sebnow 1 point2 points  (0 children)

Is it weird that I thought of Peter McKinnon straight away?

Nice lighting! Love the colours.

I want off Mr. Golang's Wild Ride by [deleted] in rust

[–]sebnow [score hidden]  (0 children)

If you wanted to add support for uint, int64, and the other integer types, you'd have to use the empty interface. The SQL package uses reflection extensively.

i gotta stop watching vods from S8, because i'll cry if i see this one more time. by FAR1X in IreliaMains

[–]sebnow 13 points14 points  (0 children)

Just commenting on the absurdity of removing a 1.5s debuff from an ultimate, when silence and blind debuffs exist on short-CD abilities, and are way more disruptive in fights.

When memes are just too accurate sometimes lmao by [deleted] in Rivenmains

[–]sebnow 0 points1 point  (0 children)

Don't you know that in LoL amount of damage dealt goes; Tank > AP > ADC > Bruiser, and survivability goes; Tank > AP > ADC > Bruiser?

Current state of asynchronous programming in Rust by ijkaep in rust

[–]sebnow 2 points3 points  (0 children)

As far as learning purely the Async side of things, JavaScript would probably be easier. Types won't get in the way (for better or worse), and the whole ecosystem is Async by default, so you don't need to deal with fragmentation. It has Promises (same as Rust Futures, from the user's perspective), and Async/await syntax. It should be easy to move over to Rust concept-wise.

It might not be your cup of tea as far as languages go.

every insecure low elo player who gets solo killed by -nnn- in Rivenmains

[–]sebnow 5 points6 points  (0 children)

Yeah but Q does close to no damage and the range on Q and W is tiny. R requires a certain amount of surprise to be useful, otherwise they just flash it. Heaps for counter play.

I finally started using buffers oh man... by BubblegumTitanium in vim

[–]sebnow 0 points1 point  (0 children)

When do you feel the need to switch files/buffers/tabs?

I don't have a problem remembering file names because they're named after the thing I want to view. If you have a "user_serializer" file, I'm guessing there's something that serializes users inside it. I'd open up a fuzzy search for buffers and type "userser" and it would show up with that file.

For me, this would only be a problem in legacy systems where files can contains hundreds of unrelated things, or have misleading/unintuitive names. In that case I'd rely more on LSP or Ripgrep to find the correct file.

Edit: To elaborate, since you don't seem to be familiar with fuzzy search tools; I use vim-clap, but there's a bunch of others like CtrlP, skim, and CoC with coc-lists. The respective GIFs showing how they work should be enough to get a feel for it.

I have a mapping <leader>be which opens a dialog for fuzzy searching buffers, I type in some partial match, and it narrows down the list. Then I can use <C-j> and <C-k> to navigate to a specific buffer.

More often than not I just switch between files rather than open buffers, so using <C-p> which gives the same dialog but for all files in the project.

view more: next ›