NRK

I'd honestly avoid large scale cosmetic changes (unless there's some solid benefit to it). They make it harder to understand the history of a specific snippet via `git blame`. Also...

> Fixing this is yet another step away from people rightfully cringing when they look at our source tree. For me at least, what's cringe worthy is the fact that...

> I also don't want to read the function definitions themselves bottom to top The problem here is that, unlike written language, code isn't something that's strictly linear (top to...

> Declarations at the top are a nice summary of what's in the file Most code editors support code folding. E.g with vim `foldmethod=syntax foldnestmax=1`:  You can easily unfold...

> ram disk (like they already are afaik) Not all distros have `/tmp` set to ram-disk by default (gentoo openrc, for example does not). Also thumbfast allows user to configure...

Since https://github.com/jarun/nnn/commit/57882ffab713e66690d29714a7fbea2cb2e61a5f `nnn` already shell escapes the filename. So I suspect that `fnameescape` call might not be correct anymore as well.

> I expect to see warnings that are relevant to my code without adding _CRT_SECURE_NO_WARNINGS to my build. > If I did add it I would not see Warnings for...

> guessContentType will return NULL if it can determine a ContentType Pretty sure you meant "__can't__" here instead of "can".

> [0]: ***@***.*** github will censor out any mail address if you reply by mail FYI.

I feel like it's been over a week already :rabbit: