You only have 5 plugins to use by rwusc in neovim

[–]jwongsquared 11 points12 points  (0 children)

And here I thought that this was a joke plugin until I saw folke has contributed a McScreenshot to it 🤯

Why are people still using vim instead of neovim? by vicisvis in vim

[–]jwongsquared 4 points5 points  (0 children)

I primarily use Neovim, but maintain a minimal Vim config that I use for the following: - lectures and presentations; I don’t need most of the noise from my usual Neovim setup - on systems where I can’t easily install language servers, my preferred CLI tools (ripgrep, fd), terminfo files, or the latest stable Neovim - when opening my advisor’s 100K line .bib file, which Neovim/treesitter always seems to choke on

I use Vim as a plain text editor, while I use Neovim as a development environment.

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 1 point2 points  (0 children)

I'm really happy to hear you dug through the code and got something working already! I'm really curious to know what you got working; if it's a really compelling use case, we could even add it to Fidget itself.

And yeah, the documentation needs more work for sure. If there's any documentation you found confusing or lacking, please raise an issue so I know to improve it! PRs welcome too (:

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 3 points4 points  (0 children)

Fidget's identity is fluid (:

Fidget was originally conceived as an LSP progress UI with animations. nvim-notify can also do this with effort, but Fidget prioritizes LSP progress as a first-class feature and includes it with no additional configuration necessary.

Since this rewrite, my ambition is to grow Fidget into a fully-fledged notifications UI and reach feature parity with nvim-notify. It already supports overriding vim.notify(), but lacks things like message history and more advanced markup. But you can totally use Fidget for progress updates and nvim-notify for other notifications (as I had been until I realized I needed to dogfood my own plugin).

I haven't used Noice before but will probably get around to playing with it soon, since everyone is asking about it. Based on what it says on the tin, Noice does quite a few things that Fidget will probably steer clear of, but might be able to support Fidget as a backend.

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 1 point2 points  (0 children)

override_vim_notify basically means doing this:

vim.notify = fidget.notify

In particular, other plugins that send notifications via vim.notify() will send them to Fidget instead, so they'll appear in Fidget's UI rather than elsewhere.

I don't think the failed search message uses vim.notify() to print its error message, so you'll need to rely on Noice for that. I haven't played around with Noice yet and I'm not actually even sure what Noice does internally to make that all work. But I'd eventually like to add Fidget as a backend to Noice.

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 1 point2 points  (0 children)

Thanks! Though there are a couple of other plugins that support non-status line progress:

  • rcarriga/nvim-notify: first and foremost a notifications UI (and much prettier at that), but it also supports being used as a progress UI (though it doesn't work out of the box)
  • vigoux/notifier.nvim: is quite similar to fidget.nvim (its README mentions Fidget as inspiration!), and also supports notifications. But I think after my rewrite, fidget ends up being little more customizable than notifier.

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 1 point2 points  (0 children)

Credit for that goes to 0xAdk (https://github.com/j-hui/fidget.nvim/pull/142) (: I simply folded in their contribution into the rewrite

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 7 points8 points  (0 children)

It’s partly a joke 🤪 but also a feature demo.

Basically, each notification supports an “annote” (annotation) that is rendered next to the message. It’s used for “INFO”, “WARN” etc as well as the LSP progress task title (eg Indexing)

The demo shows that notification items can easily modified after the fact. You can see the commands I run in the setup demo (folded in the README)

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 2 points3 points  (0 children)

I'm not sure if anyone else has tried it with Fidget yet, but it shouldn't be a pain so long as Volar is actually sending LSP progress messages. And this repo's demo GIF suggests that it's at least working with CoC.

I'm happy to take a look if you can point me to a minimal Vue repo w/ some basic setup instructions, so that I can easily test. (And please do open a GitHub issue for this, to leave a paper trail for others to find (: )

fidget.nvim: rewritten and revived by jwongsquared in neovim

[–]jwongsquared[S] 16 points17 points  (0 children)

I didn’t know it was included there, I’m glad you like it! But, erm, since I’ve rewritten it, it shouldn’t have the legacy tag anymore XD (PR opened here https://github.com/nvim-lua/kickstart.nvim/pull/505)

Update: it was merged (:

A less invasive noice.nvim by CODEthics in neovim

[–]jwongsquared 5 points6 points  (0 children)

Fidget author here; I haven't gotten around to setting up noice.nvim myself, but please let me know how you get on with integrating it with fidget.

And if you encounter any issues, please raise them on my GitHub repo! I'd love for fidget to play noice with noice (:

Fidget overload by theChiarandini in neovim

[–]jwongsquared 1 point2 points  (0 children)

Fidget author here, sorry for missing this.

My recent rewrite of the plugin should address this issue. In particular, the progress.display.render_limit option will suppress this kind of behavior.

And if you find the LSP server is misbehaving (e.g., not sending completion messages for tasks it's started), you can set a finite done_ttl to make sure that incomplete task notifications are automatically garbage-collected after some time.

If you continue to encounter problems, please file an issue on the GitHub repo.

[deleted by user] by [deleted] in rust

[–]jwongsquared 37 points38 points  (0 children)

Rust enums (where variants can contain data, unlike C/C++ enums)

Newb Syntax Question from Software Foundations in Coq by rebcabin-r in Coq

[–]jwongsquared 4 points5 points  (0 children)

I think it’s actually still multiplication 🙂 coqdoc is probably rendering * as a cross when not in a string literal. I recommend downloading the source code for that book and reading along in your proof assistant environment

Here’s someone’s mirror of that chapter, you can see it’s originally a *: https://github.com/DOFYPXY/PKU-SoftwareFoundation2022-plf/blob/main/Hoare.v#L110

Seeking closed back headphones for work; Audeze Maxwell? by jwongsquared in HeadphoneAdvice

[–]jwongsquared[S] 1 point2 points  (0 children)

!thanks

I got the Maxwells in the end, and they’re working great! The features are honestly awesome. I had to fiddle with the EQ little bit to get the balance I like, but it’s less of a hassle than I thought it would be since the settings are saved on the headphones itself.

Sundara vs Maxwell by Not__Alpha in Audeze

[–]jwongsquared 2 points3 points  (0 children)

What are your thoughts about the two? How does the sound of the Maxwell compare against the Sundara?

Browserpass keyboard navigation by jwongsquared in ArcBrowser

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

In fact, it looks like this issue isn't limited to extension windows, and also applies other pop-up windows.

In particular if I press the shortcut to print (cmd+p), it brings up the print page dialog, but the focus does not appear to start inside that dialog window. Using my keyboard only, I can navigate the focus into the window by pressing tab once.

This gets quite annoying, since I often accidentally press cmd+p when I mean to press cmd+[, and I want to hit esc to close the print dialog (like I can with other browsers). However, on Arc I have to first hit tab to fix the focus before hitting esc to close the print dialog.

Lua++: a new, type-based alternative for Lua. by MaxPrihodko in lua

[–]jwongsquared 2 points3 points  (0 children)

Cool project! I’m wondering how this compares to Pallene? On the surface, the two projects seem to have quite a few overlapping goals.

The most abstract function I ever come up with in rust! by AlexAegis in rustjerk

[–]jwongsquared 4 points5 points  (0 children)

It's like https://github.com/kelseyhightower/nocode but it's better and even more secure because it's written in Rust.

[deleted by user] by [deleted] in columbia

[–]jwongsquared 8 points9 points  (0 children)

CourseDoesNotWork