Skip to content
This repository has been archived by the owner on Aug 9, 2023. It is now read-only.

--grid is weird #4

Open
cafkafk opened this issue Jul 28, 2023 · 3 comments
Open

--grid is weird #4

cafkafk opened this issue Jul 28, 2023 · 3 comments

Comments

@cafkafk
Copy link
Collaborator

cafkafk commented Jul 28, 2023

Running --grid with the latest git version of zetta is broken on my machine.

E.g. by doing cargo run --release -- --grid, or using an installed version (see screenshot below).

2023-07-28_13-43

This is a fairly severe regression as the the default expected behavior of exa/zetta is to run --grid if nothing else is specified.

@cafkafk
Copy link
Collaborator Author

cafkafk commented Jul 28, 2023

Looking further into this I found that something happens when the terminal has around 168 columns:

2023-07-28_14-04

The behavior seems to go back to normal after 168 however.

2023-07-28_14-05

@cafkafk cafkafk changed the title --grid is broken --grid is weird Jul 28, 2023
@sbatial
Copy link
Collaborator

sbatial commented Jul 28, 2023

Note: The latest git version of exa has this already so it had to be introduced before ogham@c697d06 (most recent commit on exa)

Nevermind. I must've done something wrong.

@sbatial
Copy link
Collaborator

sbatial commented Jul 28, 2023

Ok.
I can reproduce it to an extent.

The behavior is the same.. But the breakpoint is on 104 (list) 105 (grid) columns.

So I strongly suspect something configuration/terminal specific.
(I tested in sh as well so it shouldn't depend on the shell)

Edit: I tried changing the font size which also moved the breakpoint significantly.

Also: It has to have to do something with either the command length, folder name or folder contents (maybe the prompt).
I seem to get different behaviors by changing those parameters.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants