[ehecatl42]

Not sure that I understand.

What's hard about `restic -r /media/ehecatl42/t14g3-backup/t14g3-restic-repo restore latest --target /home/ehecatl42/Desktop/nvim-restore/ --include /home/ehecatl42/.config/nvim/`* and just `cp`ing your missing files from that.

* From my recent .bash_history

[dewey]

If you want to make a point about something being “not hard” maybe using a less messy command would bring that point across better ;)

[viraptor]

It may look messy but this is really the minimal amount of info. You need the location of backup, operation, time for restoration, pattern to restore and the destination. If you already set up the backup part of restic, then this command shouldn't be hard to understand / reproduce at all.

You could maybe default to latest and default to restoring to ".", but that carries some risks. This is only as complex as necessary.

[dewey]

> this command shouldn't be hard to understand

I understand the command, I'm just questioning the example if they want to do some positive marketing for the tool. Something simple like the following gives the same information but is much more understandable than unnecessarily convoluted directory names.

    restic -r /backups/restic restore latest --target /home/dewey --include /home/dewey/myfile.txt

[hammyhavoc]

The real world isn't neat and tidy though.

I commend his real example "* From my recent .bash_history".

If someone is intimidated by paths in the CLI, the tool isn't for them. Appropriate solutions and their value is relative. Better to be realistic and honest than push people to adopt something they may struggle with.

Besides, this is HN.

[crossroadsguy]

Either you do not understand the meaning of hard or you have a very quirky way of trying to be sarcastic :)

[dmd]

“oh come on please it's easy just /etc/init.apt-get/frob-set-conf --arc=0 - +/lib/syn.${SETDCONPATH}.so.4.2 even my grandma can do that”