Hacker Newsnew | past | comments | ask | show | jobs | submit | konfekt's commentslogin

With ever more code coming at you in growing diffs, efficiently shifting it around with Vim becomes even more valuable


Just stating the obvious that there's an entire culture around replacing mice by keyboards, starting with a Vim mode in most apps.


How about buying (and installing) two cheap laptops, say used Thinkpads (or Framework!?), and then backing up $HOME (and maybe list of installed packages) at one's convenience? These are nowadays light enough to carry around when traveling with luggage. If deemed too heavy, at least a Thinkpad likely is on sale closeby and `dd`ing an ISO image, installing the missing packages and copying $HOME should not take too long.


A bit annoying to lug around for a nomad. I'm in a similar situation where I travel a lot with my mac laptop. For me, the ease of just going to a store and buying one if my current fails me is all that matters.


They may have rendered absurd to not have TLS, but they also rendered certification absurd, in the sense that all you get is little more than encryption: if you care about identity, then the free Let's Encrypt certificate coupled to a domain owner's email address gives you little guarantee. Compare this to the extended validation certificates with personally certified credentials and browsers attesting these by, say, a green address bar (instead of today's flat padlock), that a bank customer expects before entering their login data.

Setting up an encrypted web-domain with continual Let's Encrypt certificate renewal has become tedious cargo-culting around the relicts of the idea of a certificate that establishes trust by identity verification.

The collapse of identity-based certification is not Let’s Encrypt’s fault. People naturally choose the easiest option, and Let’s Encrypt supplied it.

Entrusting a handful of commercial certificate authorities with global identity is dubious on first principles anyway, but at least they tried; yet, for all its flaws, that centralized system has proven more practical than the idealistic, decentralized "web of trust".


The classic z [0] is a shell script and thus doesn't require any installation other than loading this script in your shell's rc file. I found Navita [1] an improvement over it that works more reliably on different shells such as Bash and ZSH, though.

0: https://github.com/rupa/z 1: https://github.com/CodesOfRishi/navita/


Haigh's Mathematics in Everyday Life [0] provides modern examples.

[0] https://plus.maths.org/content/john-haigh


There's the built-in `packadd editexisting` to take care of that; On Unix https://github.com/gioele/vim-autoswap could be more convenient.


Thanks, but these only seem to work with graphical versions of Vim. Also, if you suspend your Vim session, these seem to stop working.


Try these work-arounds:

- either adding to your `:help vimrc`

if has('clientserver') && empty(v:servername) try call remote_startserver('VIM-' . getpid()) catch '^Vim\%((\a\+)\)\=:E\%(941\|240\)' endtry endif

- or, at least on Unix, calling vim by, say `$HOME/bin/vim` with `$HOME/bin` in `$PATH` and launching

/usr/bin/vim --servername vim -u ~/.vim/vimrc "$@"


Try filepicker.vim [0] to navigate these in one of the many popular millers like lf, yazi, ranger or nnn

[0] https://github.com/Konfekt/filepicker.vim


Though it promises to convert everything to Markdown, it seems to be a worse version of what the already existing tools such as PDFtotext, docx2txt, pptx2md, ... collected [here] do without even pretending to export to Markdown. Looking at its [source], it indeed seems to be a wrapper to python variants of those. Making the pool smaller can hardly improve the output.

[here] https://github.com/Konfekt/vim-office [source] htps://github.com/microsoft/markitdown/blob/main/src/markitdown/_markitdown.py


Maybe worth reminding the self-documenting Makefile [0] discussed here.

[0] https://news.ycombinator.com/item?id=30137254


I've been using this for years; love it


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: