vim-grepper VS httm

I'm curious, what specifically works better about their IDE for you in the case of many files? Do they now have good global refactoring tools, like you can change a class name in library A and have it automatically be updated in library B and application C that depend on and use it? And without the actual files for such being open? (I'm reduced to what's essentially mass search-replace with https://github.com/mhinz/vim-grepper/ but it does the job and importantly helps update files I might not have open buffers for. Still a step down from what's available in JavaLand. I remember someone was working on a library to build some modern refactoring tools for Lisp but I don't know how far that's gotten.)

J'aime bien https://github.com/mhinz/vim-grepper Et https://github.com/kevinhwang91/nvim-bqf Pour ce travail.

I had a look at your planned modules and thought I could swamp you with some more ideas, to possibly inspire you to do a few of them: - since you are thinking about making mini.quickfix: - vim-grepper: eases configuration of grep tools like rg and integration with quickfix - recipe.nvim: instead of defining 'makeprg', making a build step, which can send errors to the quickfix and a run step which runs in a floating terminal - qf.nvim: adds some additional stuff to quickfix, on top of bqf, like a proper quickfix toggle command, which I never want to live without again

use a grep tool plugin, I like https://github.com/mhinz/vim-grepper for this.

This is great when you want to jump to a specific place.

I also use vim-grepper (mapped to leader-g) for finding in files and populating the quickfix list.

https://github.com/mhinz/vim-grepper

Why not just using vim-grepper? :p

Not an answer to your question but vim-grepper allows you to use ag already (if you are using it from grepping).

This wouldn’t be a direct replacement for searching, but could you create/find a tool which uses perl regex to fill the location window? e.g you can use vim-grepper and modify the rg command with --pcre to use the pcre2 engine.

Could you expand on how this differs from vim-grepper?

My projects and many projects include a THIRD-PARTY-LICENSES.html file when I distribute binaries. See: https://github.com/kimono-koans/httm/blob/master/third_party/LICENSES_THIRD_PARTY.html

The only real advantage I can think of with nested ZFS is that the files in the KVM would obviously be individual inodes in the nested ZFS filesystem and datasets, in addition to the one inode per virtual volume on the hypervisor (or zvol). This would allow for granular file management on the kvm and the use of tools like https://github.com/kimono-koans/httm which is like a command line time machine for ZFS.

> It's worth noting that copy_file_range is used by a lot of things.

Yes, but the trigger feature, block cloning, only landed in the latest 2.2 release. If you immediately hopped on 2.2, and used a system with lots copy_file_range and FICLONE use, yes, you may have a problem (like, as you note, on Gentoo, where this problem surfaced).

Most people were just hopping on the bandwagon. My distro ships 2.1.5, so I have a 6 month wait until this feature lands, so I was just building copy_file_range support into my ZFS apps, right before news of this bug hit.[0]

> There are other things required to trigger the bug that are a lot less common though.

Exactly. My guess is the incidence of this will exceedingly rare for the common user/small NAS user/etc. I've run a corruption detector[0], and what I've found mostly indicates false positives. Some are build artifact fingerprints, which I don't care about, and which were deleted with the next build. The ones with an extant file on another system, I confirmed were a diff match with the origin using `rsync -rincv` and whats on snapshots with `httm --map-aliases`. So far no positive matches.

[0]: https://github.com/kimono-koans/httm

cargo install --git https://github.com/kimono-koans/httm --branch clones strace -f -o stderr.txt -e ioctl -- httm -r -R ~/.zshenv

httm prints the size, date and corresponding locations of available unique versions (deduplicated by modify time and size) of files residing on snapshots, but can also be used interactively to select and restore files, even snapshot mounts by file! httm might change the way you use snapshots (because ZFS/BTRFS/NILFS2 aren't designed for finding for unique file versions) or the Time Machine concept (because httm is very fast!).

All btrfs snapshot tools can have different layouts. It's mostly a nightmare for any one tool to support. Although its not the tool you're looking for, FYI AFAIK httm supports all/most btrfs layouts, but it took more work than necessary to get there.

ZFS only option which requires super user privileges.

[0]: https://github.com/kimono-koans/httm/blob/master/httm.1

httm - Interactive, file-level Time Machine-like tool for ZFS/btrfs/nilfs2