Column width not adjusted appropriately according to used character

[godfuture]

Hi,
I noticed that often the name of folder or files are cut because lack of space. But in the same time, other columns that do not need the space (owner, mode, date) have too much space reserved. It would be better, if short columns only reserve the space they need and spent more space to name column.

[coderaiser]

Hi, is it relates to Cloud Commander? What screen size do you have?

[godfuture]

is it relates to Cloud Commander?

Yes.

What screen size do you have?

Few days ago 22 inch. Now trying it out on 32 inch. Both sizes have this issue. Bad readability even enough pixels available.

[coderaiser]

Could you please tell me resolution you are using in pixels, or better add screenshot.

[godfuture]

Could you please tell me resolution you are using in pixels

22 inch = 1680x1050, 32 inch = 2560x1440

-> Screenshot attached, too.

[coderaiser]

I see, this looks like a bug, and it is a good idea for a Pull Request :).

[coderaiser]

Fixed with 76e0eab, landed in v15.0.1 🎉 .
Is it works for you?

[godfuture]

Can´t wait, really great!
Is there already a docker build? If not, I would setup virtualbox with Linux. But it would take a bit.

[coderaiser]

Yep, on dockerhub :).

[godfuture]

Yep, on dockerhub :).

Is it downloading the latest assets? Because the image wasn´t updated since months...

Edit: just saw it was updated. Thanks, I will test it.

[godfuture]

When trying to replace my container, I get the following error:
OCI runtime create failed: container_linux.go:370: starting container process caused: exec: "/usr/src/app/bin/cloudcmd.js": stat /usr/src/app/bin/cloudcmd.js: no such file or directory: unknown

Is this related to V15 release? I have not adjusted ENV variables from previous container...

Edit: The issue here was that I have not wiped my container, but to replace it in portainer. Portainer than preserved old settings (e.g. ENTRYPOINT). After starting from scratch, container creation was fine.

[godfuture]

I have tested the issue with new container and it looks much better, as the name section is not cut or in other words I can properly read folder and file names again. Thanks a lot!