Joey Sabey
Joey Sabey
Applying the same fixes to the issues version of function things look pretty parse when you diff the two functions:: ``` func (m *Model) runCustomIssueCommand(commandTemplate string, | func (m *Model)...
I've split out common functionality as well in #362, if that is the direction you want to go.
If there's more refactoring to do, I think it depends a lot on what the future scope of the project is here. Is the plan to add screens for e.g....
> * I personally find it really helpful when cli tool facilitate the creation of a config file In the hobby project I've been mucking around with lately, I'm going...
> I don't really like dumping one at XDG_HOME | XDG_CONFIG, but I think its reasonable to check there for an existing one (if EZA_CONFIG_DIR isn't set, before falling back...
> I believe a config file shouldn’t try to do what’s already doable with shell aliases That's a pretty puzzling position to take, tbh... Shell aliases are rather a hacky...
`eza --header | tail -n +2 | fzf` ought to work.
> One way to think about it is that directories have an implicit `.dir` extension and thus any other `.` in the directory name should be ignored. I find this...
 This is how it behaves if the sorting code just short circuits out to 'equal' if either the A or B input is a directory when it is asked...
[Crude fork that fixes this.](https://github.com/Omnikron13/eza/tree/no-dir-ext)