Neofetch: Split neofetch into multiple files

[tudurom]

neofetch is huge with almost 3000 lines of code. It should be split into multiple files.

We can also add a script that combines all the little scripts into a single one, making possible distributing _neo_fetch in a single file.

[dawidd6]

[tudurom]

*3000

[dylanaraps]

I _really_ don't want to do this but I'll start work on it anyway.

[tudurom]

Why not?

[dylanaraps]

See #219

[konimex]

I really want to know why should we split this into many files. As @tudurom mentioned in #219 the speed is exactly the same. screenfetch has ~4000 lines in their code. IMO there's just no technical advantage to split it up.

[tudurom]

If we split neofetch in multiple files, it would be easier to contribute on it.

[dylanaraps]

It's still very easy to contribute to neofetch as the script is split up into folds which act as a break between functions/blocks. See these screenshots showing how every function is split into its own block. You may need to open the images in a new tab to see the text.

[tudurom]

iirc this kind of folds are for vim only

[dylanaraps]

The folds should work in any text editor that supports code folding, what text editor are you using?

https://en.wikipedia.org/wiki/Code_folding#Software_with_code_folding_capability

[tudurom]

i use neovim. neovim has a known issue for taking long to open long files.

[dylanaraps]

I'm also using neovim and have no issues opening the file, hm.

[tudurom]

Let's set a cap for when to split neofetch. Let's say if it exceeds 5000 lines, we split it.

[dylanaraps]

Nope.

I don't want to split the script up into multiple files and I don't see the benefit in doing
so.

I'm closing this issue now, if anybody can implement this with some clear benefits I'll
think about merging it.