mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

14K
active users

#ripgrep

0 posts0 participants0 posts today
Replied in thread

@ike ... and this stuff has been done with an approach to kanban boards (as part of an NLNet funded project, Icebreaker).

So for instance, I can use #ripgrep to search `rqr` for available tasks (or a more complex annotation featuring that as a subsets).

Because Ive been diligent regarding spacing things out and cross linking like a zettlekasten the location of a document can provide an additional context in supplement to the line(s) identified.

There are other forms like `ìq` for policies.

Acabo de descubir #ripgrep y es UNA FANTASÍA de comando ❤️

Básicamente, te permite buscar un texto en todos los archivos que haya en el directorio en el que te encuentres, y te muestra en qué archivo está y en qué línea resaltando dicho texto. Lo mejor de todo es que me lo he encontrado ya instalado, no sé si era alguna dependencia o viene de serie. Qué gran serendipia ✨
github.com/BurntSushi/ripgrep/

GitHubripgrep/GUIDE.md at master · BurntSushi/ripgrepripgrep recursively searches directories for a regex pattern while respecting your gitignore - BurntSushi/ripgrep

Hm. Is there a #CLI #Markdown renderer that can do "display foo.md beautifully in the terminal, and highlight whatever source line 123 contained (which is almost certainly not _output_ line 123)"?

I have a collection of Markdown documents and would like to run full-text search on them, e.g. using #ripgrep, but I don't want the results to be displayed as raw Markdown, but instead be rendered in the terminal, but still see where the result is. Any ideas?

Hot tip for #ripgrep `rg.el` users in #Emacs who don't know anything about default keyboard shortcuts:

You know that n/p go to next/previous item?

The key binding reveals that this is a normal compilation mode binding for `next-error`.

You can use it from the *other* buffer, the one with the content, via <C-x `>

If there's someone else out there who didn't have the stamina to set up LSP for #java on #neovim (for instance for a project you only use occasionally), maybe the plugin I wrote to get navigation (go to definition, find references) in Java projects using tree-sitter helps you too: github.com/emmanueltouzery/cod

#treesitter rocks. #astgrep rocks. #ripgrep rocks. #lsp rocks. #neovim rocks. We truly never had it this good.

GitHubGitHub - emmanueltouzery/code-compass.nvim: Neovim plugin: set of functions to navigate code without LSP.Neovim plugin: set of functions to navigate code without LSP. - emmanueltouzery/code-compass.nvim

I want to dedicate a toot to thank #Alacritty and #ripgrep, not because they are wonderful programs (they are), but because they add so many documentation comments in their source code. Many #Rust programs don't do this. Sure, libraries benefit more from them, but they still help a lot in binary crates as well. They allow new contributors to skim over the code, generate documentation using `cargo doc` and help so much when using rust-analyzer. Please add documentation.