Improve the way software is listed

[felicianotech]

The amount of software that this project supports is already fairly large. The majority of open issues are requests to add more. At this pace, the software list will become unmanageable quickly. This issue is for future planning.

1. Readme - this could possibly me moved to its own markdown file. Perhaps with headings for categories so that they can easily be linked over from the readme.
2. deb-get list - this is long and depending on screen size, quite a scroll. Perhaps, when an interactive shell is detected, the output is passed through less? If categories are implemented as mentioned above, perhaps this can be passed via a flag and only show packages in that category.

[github-actions[bot]]

Hello there 👋 Thanks for submitting your first issue to the deb-get project 🐛 We'll try and take a look at your issue soon ⏲

In the meantime you might want to join the Wimpys World Discord 🗣 where we have a large community of Linux 🐧 enthusiasts and passionate open source developers 🧑‍💻

You might also be interested in following Wimpys World Twitch 📡 channel where Wimpy streams let's code video, including this project, several times a week. A back catalog of past live stream and other Linux related content is available on Wimpys World YouTube 📺 channel.

[flexiondotorg]

Looks like #275 goes some way to addressing this :+1:

[bayazidbh]

I think for the deb-get usage command and the software list in the readme file can use a <detail> tag like in Ferdium's Screenshot section.

Test

Test.

Though, as the list of package grows, maybe it can also be broken up by alphabet to make searching and browsing easier while keeping it looking clean.

[Xmetalfanx]

I have to admit i am not sure how this would (just started using it as per the instructions) effect cog and how it works with this project but I was thinking with the software list ballooning up ... would it be a good idea (if possible at all) to separate the deb_NAME functions into a different file, "include" that file in the main script and still have say everything work as it is now (say add a "DEB_function" to that file instead for just basically organization reasons

Also it'd be nice to (even if my idea i just said isn't a good idea) to have some script or something run on "deb-get" that would organize the "deb_*" functions in alphabetical order after the "_" ... say you add a new addition to the bottom of the list, you run this script that (where ever the deb functions are) would reorder them for organization alphabetically and then you'd run cog as the instructions already state.

The one question I'd have with that re-order part, is would that have to be done on the other end ... like if people have different PR's for different software ... merging with main when it's done may return things "out of order" since different PR's wouldn't have additions that are inside other PRs

[natanjunges]

• #313 already tries to solve this issue and more.
• This is already what happens in https://github.com/wimpysworld/deb-get/blob/ae104c8560d0f56c42cc0708b6785fbc0c772782/deb-get#L2432. As a result of this line, the outputs of list, prettylist and csvlist are always ordered.