Yes they are wrong. A contribution may consist of “merely” a bug report. Even just asking questions may indicate that the UX or documentation is lacking.

No? This will search the logfiles (if irssi is configured to create those at all) for a pattern. This still requires that you had to have an irssi client running and connected to the server/channel in question, during the time the user is afk. Which is why others recommend e.g. setting up ZNC.

There are also mutt and neomutt.

I personally have been using the latter for years, but it requires some time to setup and tweak until it fits your purposes.

Documentation is top-notch though, and customizability a first-class concern.

I used tmsu (“tag my shit up”) for a while, but it required too much discipline and then I dropped it.

In addition, tools like fzf for fuzzy file-search (comes with shell integration to e.g. replace the default history search in bash) and ripgrep-all made this kind of organization unnecessary for me. It now suffices to have a vague idea where a thing is located and I can do a brute-force search in a few seconds.

The next-level filesystem argument is brought forward every few months, but I’m not buying it.

I should’ve done my homework before replying then :)

Although the relevant links have already been provided, the gist is

• Acme stands for some “generic” editor here, where you have to use the mouse a lot, which is perceived as slow
• Emacs is known to be very powerful (to the extend of being called an “OS with a bad editor”), but using unergonomic keyboard shortcuts
• Vim is an editor that has been designed for keyboard power users in mind, but which has the reputation of being difficult to learn