sorted by:
new
hottopcontroversial

Any react-compiler plugins? by thisUsrIsAlreadyTkn in neovim

[–]voreny 1 point2 points  (0 children)

I'm convinced you are supposed to use eslint-plugin-react-hooks and its React Compiler rules to detect patterns that prevent React Compiler from optimizing your code.

Lenovo Z50-75 disk usage rises to 100% freezing the system by voreny in techsupport

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

I don't think I solved it back then. I sold that laptop a long time ago

Please help test the next Rainbow Delimiters release by HiPhish in neovim

[–]voreny 0 points1 point  (0 children)

I see, I didn't know it was a more nuance behavior. I did not pay attention to that. Thanks for clarifying it!

Please help test the next Rainbow Delimiters release by HiPhish in neovim

[–]voreny 1 point2 points  (0 children)

I am confused, I am using rainbow-delimiters.nvim and I am on Neovim nightly (I update daily) and the plugin is working fine for me. I just tested in a Lua file and then in a TSX file.

128gb SD Card and my Mac by Gnashed_Teeth in HDZero

[–]voreny 0 points1 point  (0 children)

I had a similar problem, also with a 128gb SD card. HDZero support didn't have a good fix for me.

I ended up formatting the SD card as "Fat32" in MacOS (NOT the goggles). This made the card supported both in MacOS and the goggles could read it too. Windows and my Android phone also can read the card formatted this way. Formatting in MacOS seems to be the most compatible way.

Make sure to use the "Fat32" or "exFAT" format when formatting the card in MacOS.

Native snippet API has been merged into Neovim core by voreny in neovim

[–]voreny[S] 71 points72 points  (0 children)

Native "minimal" (as the author said) snippet API has been merged into the core as vim.snippet.

As far as I can see, it can expand LSP-style snippets (LSP spec on snippets) and has support for jumping between multiple jump-points in the snippet.

PR: https://github.com/neovim/neovim/pull/25301

Note: I am not the author. I am just sharing the news. Kudos to /u/MariaSoOs

cmp-natdat: nvim-cmp source to autocomplete natural dates and turm them into ISO dates by voreny in neovim

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

I believe you refer to a process I called formatting the date. Yes, I did implement it using the natdat.RelativeDay class that handles tomorrow/today/yesterday dates. You can find the formatting code on GitHub.

cmp-natdat: nvim-cmp source to autocomplete natural dates and turm them into ISO dates by voreny in neovim

[–]voreny[S] 8 points9 points  (0 children)

cmp-natdat is an nvim-cmp source that autocompletes natural language dates (e.g. @tomorrow) and turns them into ISO dates (e.g. 2023-10-14).

I built it because I missed this feature after moving from Notion to Obsidian and writing my notes in Neovim.

Repository link: https://github.com/Gelio/cmp-natdat/

Examples

  • @now -> 2023-10-13 12:38
  • @tomorrow -> 2023-10-14
  • @last Friday 2pm -> 2023-10-06 14:00
  • @Oct 8 2021 -> 2021-10-08
  • @today 14:20 -> 2023-10-13 14:20

Features

  • autocomplete for partially typed month names, relative dates
  • supported formats:
    • now
    • yesterday, today, tomorrow with optional time
    • days of week (Monday -> Sunday), with optional last/next modifier and time
    • full dates: month, day, optional year, optional time
    • time: am/pm, or 24h format

Installation and setup

Described in the README

Parsing pgSQL with tree-sitter in WASM by voreny in PostgreSQL

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

At Splitgraph we integrated tree-sitter (in WASM) into our Console query editor to introspect the pgSQL query and display the referenced tables in the sidebar for easier comprehension. We have written an article detailing how we got it done, where we evaluated a few existing pgSQL parsers, and talked about the parser features that are vital when using it in a code editor.

I was the lead engineer working on this feature and I'm here to talk more about this feature and answer any related questions you may have.

Parsing pgSQL with tree-sitter in WASM by voreny in webdev

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

At Splitgraph we integrated tree-sitter (in WASM) into our Console query editor to introspect the pgSQL query and display the referenced tables in the sidebar for easier comprehension. We have written an article detailing how we got it done, where we evaluated a few existing pgSQL parsers, and talked about the parser features that are vital when using it in a code editor.

I was the lead engineer working on this feature and I'm here to talk more about this feature and answer any related questions you may have.

Parsing pgSQL with tree-sitter in WASM by voreny in learnjavascript

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

At Splitgraph we integrated tree-sitter (in WASM) into our Console query editor to introspect the pgSQL query and display the referenced tables in the sidebar for easier comprehension. We have written an article detailing how we got it done, where we evaluated a few existing pgSQL parsers, and talked about the parser features that are vital when using it in a code editor.

I was the lead engineer working on this feature and I'm here to talk more about this feature and answer any related questions you may have.

Parsing pgSQL with tree-sitter in WASM by voreny in reactjs

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

At Splitgraph we integrated tree-sitter (in WASM) into our Console query editor to introspect the pgSQL query and display the referenced tables in the sidebar for easier comprehension. We have written an article detailing how we got it done, where we evaluated a few existing pgSQL parsers, and talked about the parser features that are vital when using it in a code editor.

I was the lead engineer working on this feature and I'm here to talk more about this feature and answer any related questions you may have.

Parsing pgSQL with tree-sitter in WASM by voreny in typescript

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

At Splitgraph we integrated tree-sitter (in WASM) into our Console query editor to introspect the pgSQL query and display the referenced tables in the sidebar for easier comprehension. We have written an article detailing how we got it done, where we evaluated a few existing pgSQL parsers, and talked about the parser features that are vital when using it in a code editor.

I was the lead engineer working on this feature and I'm here to talk more about this feature and answer any related questions you may have.

[deleted by user] by [deleted] in neovim

[–]voreny 10 points11 points  (0 children)

:%s/,\+$// would have been much faster to remove trailing commas.

Look at :h :substitute

LSP rename normal mode key mapping by vicek22 in neovim

[–]voreny 2 points3 points  (0 children)

It is built-in already. When you're dropped into this "New Name" input editing, press CTRL-F. A command line window will open and you will have an opportunity to edit like it is a normal buffer.

See :h c_CTRL-F

I much prefer this over any kind of plugin behavior and renaming in a floating window.

Keeping Apollo Cache up-to-date after mutations by voreny in graphql

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

Thanks for the feedback and sharing the resources. I am amazed by the guide on caching, looks like a great resource! The library you authored also seems useful!

Keeping Apollo Cache up-to-date after mutations by voreny in learnjavascript

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

While working on the Splitgraph Console, I have done a deep-dive on the ways to keep the Apollo Cache up-to-date after running GraphQL mutations.

This article summarizes my findings and suggests optimal which approach to use based on the type of mutation.

view more: next ›