-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
add image name to container frame #144
Comments
Update issue: jesseduffield#144
Have you also tried looking at it in a small terminal window? The problem with these wide lines is that not everyone has there terminal maximized and for those these these changes look wrong.
|
@mjarkk It works well if window's width is greater than 1150. CPU is indeed important. So another way is to place the image name behind the CPU. Or more sophisticated, decide wether to show the image name depend on the window's size, but it will bring complexity. But I do think the image name is very important. I always use the terminal in max window size mode, and I think most of users do this. |
I've got no issue with showing the image name after the cpu. Although, it seems that there is a strong use case for being able to see a lot of things related to a panel list item in the side panel. Perhaps we should consider having a toggle-able expanded side panel view for when you want to see extra information about all your e.g. containers at once. At any rate for this issue I'm happy for the image name to go after the cpu. |
@jesseduffield I think I can change my codes and fix this one: show the image name after the CPU. |
Update issue: jesseduffield#144
Update issue: jesseduffield#144 Co-Authored-By: Jesse Duffield <jessedduffield@gmail.com>
I think the image name should be added to the container frame because it's a really important thing especially when I haven't named the container such as the
nice_cartwright
andangry_chatterjee
in the above picture. And, I can't see the image name in any of the right pages.The text was updated successfully, but these errors were encountered: