feat: Order of the columns about eza HOT 8 OPEN

Just to drop one more feedback point: currently in the -l output the permission and ownership info is separated by the size info – while it feels like the permission and ownership info are much more closely related to each other, than size related to either one of them.

To be fair, it's the same with ls -l output too, but with hard-link counts instead of size (which I find slightly less distracting, though).

Therefore, the idea of configurable output column order sounds awesome! 👍

Perhaps it's worth considering to use full words for the name of environment variable: EZA_COLUMN_ORDER instead of EZA_COLUMN_ORD

from eza.

I'm going to go the ENV route and see if I can put something together. Can you assign this to me?

although it could also perhaps allow full names as well EZA_COLUMN_ORD="time;user;permissions;git;name" and such?

Agreed that looks much better

from eza.

I guess I should look at this again. I think I stopped after realizing there's no way to change the order of the file/dir names, but there still might be some use for this feature

from eza.

This does indeed look tricky. Not using clap for arg parsing is something to get used to for sure. You think this belongs in the command line arguments at all?

Individually specifying the order of the columns sounds like an ENV_VAR "gi=42;2" type deal, where

EZA_COLUMN_ORD="t;u;p;g;n" (Time, user, permissions, git, name)

Thoughts? Or is this maybe something to revisit in #139 ? When users can be more expressive

from eza.

Thoughts? Or is this maybe something to revisit in #139 ? When users can be more expressive

The feature could be really cool, EZA_COLUMN_ORD="t;u;p;g;n" makes sense to me, although it could also perhaps allow full names as well EZA_COLUMN_ORD="time;user;permissions;git;name" and such?

Not using clap for arg parsing is something to get used to for sure.

Yeop...

from eza.

This issue is stale because it has been open for 30 days with no activity.

from eza.

This issue was closed because it has been inactive for 14 days since being marked as stale.

from eza.

14 days of inactivity is pretty short, why even close?
Looks like it's only waiting for an implementation here, no rush imo

from eza.