New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Group the list of currently supported filetypes by categories #123
Comments
Hello!
Preview:
I'm currently doing tests for preview functions with the "file" command. This week, I want to finish the preview branch, tests, and documentation. |
In first place, I am noticing that our current list could probably fit in a standard 80x24 screen, using 2 or 3 additional columns. Now... Your idea seems to point in the right direction, but I would insist in the idea of extension groups. The message could include the list of categories or groups and then the options to view a group ( Currently I am on a full time job, but I will try to get some time at night or weekend to review any pull requests, translate documentation changes and do some testing. We are not in a hurry to release this, since the current version seems to be pretty stable (not that many complaints, right? 🙂). So we may take the necessary time to make sure everything is properly put together. |
The number of columns may depend on the size of the terminal window. |
"a", "all", "v", "text" - can be names of extensions. I suggest using upper case for group names and lower case for extension names. Groups: |
to view a group (upper case): search for extension (lower case): search for extensions (lower case): display all (upper case): |
It is an open source project. We can take our time. We can stretch the work until the end of the year. September Autumn Winter Is this option right for you? |
Do you mean using the entered text's case to implicitly indicate which action should be performed? If so, I disagree. It's an unnecessarily unconventional behaviour. With regards to the timing, it's ok. We will continue doing it at our own pace. |
I understand. All the current versions had
Then, some new commands 1. View a specific supported types/extensions group:
2. Search the supported types list for one or more extensions, like
|
In this case, a different case is needed to distinguish the keyword from the extension name. It seems to me that this is the simplest option. We have already organized the help search by the similar principle of entering arguments/keywords (
If I understand correctly, are you suggesting adding new arguments to the parser? Something like that:
|
Another option is to categorize the supported types for now. Just divide the extensions into categories in this version, and that's it. |
Having more commands registered in the parser is not a big issue, I believe. The only problem is the help page getting a bit longer. That's why I am still convinced that we should not change the behaviour of
It is a good idea, since it would be less work to do before the next release. It's basically number 4 as stated above:
We can keep the old alphabetical view ( |
The list is growing and is starting to need some sort of organisation. Currently, it displays 4 columns and 29 lines, with items being sorted alphabetically first by line, them by column. It would be a little more readable if it was sorted alphabetically by column instead.
But grouping by filetypes would probably be a great help, even if it makes the list a bit longer.
The text was updated successfully, but these errors were encountered: