I agree. Would be very nice if this was an option at least (that could be turned on by configuration). On the design considerations [1] they state:
> Previewing large files on selection is a wastage of processing power and time. A slow/faulty disk or over the network access makes the experience very painful.
You only need the first lines of the file, not the whole file, so this argument is not valid.
> It's also a risk to privacy and confidentiality. Users should see only what they explicitly want to see.
Not valid if preview is off by default. A hotkey could toggle preview mode.
Yes, you can open each file in a pager. Exit the pager, go to the next file and repeat. That is slow and painful. Being able to browse a code repository with file preview is the main reason I will probably not use this and stick with ranger. It's a deal breaker for me.
I really like that it's fast (I've tried using ranger on the USB Armory – it was very slow), and if preview was added as an option I would seriously reconsider.
Not necessarily if you turn off your computer or use hibernation instead of sleep, AND you use full disk encryption. This will stop short-term attacks, like cold boot attacks and the like.
Of course, if they "borrow" your laptop for a while, opens it up, installing key loggers, modifying the firmware/hardware, and you do not notice this: you are f*ed.
I mean: even if you believe that "if someone has physical access to your computer, it's pretty much game over" you don't necessarily drop encryption and user password on the laptop and always put it in sleep mode.
Shameless plug: If you want to organize your content with files and directories without any configuration files and all that fuzz, I created PLY[1] this summer.
All it does is convert .md files to .html and optionally uses nested Golang templates. There are some tricks behind the scenes, like support for tags and meta data (just like regular static site generators). Flexibility is concentrated into the templates, so no other files are needed.
I think the content (files) should reflect the structure of the webpage as close as possible when using a static site generator. When reducing complexity, we can go all the way down to the filesystem, where files and directories are the main building blocks. Content and design must be separated as much as possible.
I have not tested all static site generators out there, but the few that I tried did not satisfy my demands. So I just made my own (for fun and learning).
Some CS students even made a game based on the hilarious video, where you play as the moose and must eat apples while defending against incoming lawnmowers: https://joelspeanuts.itch.io/elgspillet
I just happened to deliver an assignment today about The Barabási-Albert Model. We use this book in class (you can read it online): http://networksciencebook.com
Putting personal preference (taste, price, etc.) aside, I'm curious what other reasoning is behind your position of being "all for eating meat" (if any)?
I'm assuming here that by mentioning it in the same sentence as you say beef is bad for the environment, you are talking about being for meat production on a global scale, and not just for your personal preference.
> you want to use "fix" instead of "on" to prevent an attacker from just turning it off again.
An attacker also must know you admin PIN (required to change this setting), so there is really no need to use "fix" instead of "on". To be able to toggle this off, you must reset your yubikey (paraphrasing the docs).
> Previewing large files on selection is a wastage of processing power and time. A slow/faulty disk or over the network access makes the experience very painful.
You only need the first lines of the file, not the whole file, so this argument is not valid.
> It's also a risk to privacy and confidentiality. Users should see only what they explicitly want to see.
Not valid if preview is off by default. A hotkey could toggle preview mode.
Yes, you can open each file in a pager. Exit the pager, go to the next file and repeat. That is slow and painful. Being able to browse a code repository with file preview is the main reason I will probably not use this and stick with ranger. It's a deal breaker for me.
I really like that it's fast (I've tried using ranger on the USB Armory – it was very slow), and if preview was added as an option I would seriously reconsider.
[1]: https://github.com/jarun/nnn/wiki/nnn-design-considerations