Icons And Image Previews In Vifm, Plus Xterm Is Great! DistroTube
video description
Date: 2022-03-30
Related videos
Comments and reviews: 10
Kevin
Whether a program is bloat shouldn't be defined by the binary installation size but rather the runtime resource characteristics. CPU and RAM usage for normal but also contextual operations. although I can't think of many contexts a terminal application would want to test to functionally prove much. maybe high scrollback usage to see if RAM spikes. multiple terminals and shared memory. which is further subjectified by using rxvtd for a terminal daemon if that use case matters.
Package instalation size could vary on not just compile time directives for the specific maintainers choices but also how well or wether at all it uses various dynamic linking contexts to system libraries. Lines of code is also subjective to compile directives but also compiler optimization of the specific coding methodology.
Just saying. Proper comparison.
Personally, I'm stuck on Sakura since urxvt borked on unicode/powerline/fontawesome issues for me. I'm going to resolve it better at some point by figuring out the known topica obscura on urxvt's developers philosophy on unicode handling domain of responsibility. or shift to st. either way. meh. terminal programs.
reply
Whether a program is bloat shouldn't be defined by the binary installation size but rather the runtime resource characteristics. CPU and RAM usage for normal but also contextual operations. although I can't think of many contexts a terminal application would want to test to functionally prove much. maybe high scrollback usage to see if RAM spikes. multiple terminals and shared memory. which is further subjectified by using rxvtd for a terminal daemon if that use case matters.
Package instalation size could vary on not just compile time directives for the specific maintainers choices but also how well or wether at all it uses various dynamic linking contexts to system libraries. Lines of code is also subjective to compile directives but also compiler optimization of the specific coding methodology.
Just saying. Proper comparison.
Personally, I'm stuck on Sakura since urxvt borked on unicode/powerline/fontawesome issues for me. I'm going to resolve it better at some point by figuring out the known topica obscura on urxvt's developers philosophy on unicode handling domain of responsibility. or shift to st. either way. meh. terminal programs.
reply
Chulito
Hey Distrohuggers,
I inserted an new shiny SSD in my machine and pulled out my beloved SSD with Tumbleweed. I just installed the Developmental Stable Edition of Neon. That was probably the easiest install I have ever had. Anyways, my machine is now sporting KDE Plasma 5. 14. 5, KDE Applications 18. 12. 1, and KDE Frameworks 5. 54. Underneath all that is Ubuntu 18. 04. This is probably just a temporary thing for me, as it may be 3 or 4 weeks before those KDE features are in Tumbleweed.
Only been using it a few minutes, but resources seem similar to Plasma 5. 14. 4 on Tumbleweed.
I wanted to test my new scanner and laserprinter and my new faxing app ( XenFax ) in a different distro ( other than Tumbleweed, before throwing in the towel and purchasing Windows 10. I need to purchase a new laptop anyways, so I might have to settle for one with Windows. Leaning towards a Dell G3 17.
reply
Hey Distrohuggers,
I inserted an new shiny SSD in my machine and pulled out my beloved SSD with Tumbleweed. I just installed the Developmental Stable Edition of Neon. That was probably the easiest install I have ever had. Anyways, my machine is now sporting KDE Plasma 5. 14. 5, KDE Applications 18. 12. 1, and KDE Frameworks 5. 54. Underneath all that is Ubuntu 18. 04. This is probably just a temporary thing for me, as it may be 3 or 4 weeks before those KDE features are in Tumbleweed.
Only been using it a few minutes, but resources seem similar to Plasma 5. 14. 4 on Tumbleweed.
I wanted to test my new scanner and laserprinter and my new faxing app ( XenFax ) in a different distro ( other than Tumbleweed, before throwing in the towel and purchasing Windows 10. I need to purchase a new laptop anyways, so I might have to settle for one with Windows. Leaning towards a Dell G3 17.
reply
distroverse
Stop using old ass w3m-img: P! Ueberzug is a lot better and also works really with any terminal. I tested it on st, termite and gnome-terminal, lxterminal, xterm, urxvt, konsole, alacritty and all of them worked perfectly on ranger (you need to get ranger from git, as they didn't done new version which contains support for it) using this method. It is possible to use it with any program, so someone can make script to use it in vifm.
Xterms README:
Abandon All Hope, Ye Who Enter Here
This is undoubtedly the most ugly program in the distribution. It was one of the first -serious- programs ported, and still has a lot of historical baggage. Ideally, there would be a general tty widget and then vt102 and tek4014 subwidgets so that they could be used in other programs. We are trying to clean things up as we go, but there is still a lot of work to do.
And nothing changed: D
reply
Stop using old ass w3m-img: P! Ueberzug is a lot better and also works really with any terminal. I tested it on st, termite and gnome-terminal, lxterminal, xterm, urxvt, konsole, alacritty and all of them worked perfectly on ranger (you need to get ranger from git, as they didn't done new version which contains support for it) using this method. It is possible to use it with any program, so someone can make script to use it in vifm.
Xterms README:
Abandon All Hope, Ye Who Enter Here
This is undoubtedly the most ugly program in the distribution. It was one of the first -serious- programs ported, and still has a lot of historical baggage. Ideally, there would be a general tty widget and then vt102 and tek4014 subwidgets so that they could be used in other programs. We are trying to clean things up as we go, but there is still a lot of work to do.
And nothing changed: D
reply
leonardo
xterm is bloat, in the same sense as when some ppl using neovim say vim is bloat. It's not the usual 'python is slow, and look how many LOC that project has' kinda bloat(which xterm has some of that as well, it's more like 'that program has SO much legacy code that doesnt do anything for me'. That's vim case, and that's xterm case. if you want another opinion, read the README in the xterm repo and, as the developers themselves put it 'Abandon All Hope, Ye Who Enter Here' The only surprise after running tokei on all 5 cases you showed (plus xfce4-terminal) is that lxterm is smaller by all accounts than upstream st, that was indeed surprising. I'll probably read the code and test both to see why's that. but yeah, TL; DR, xterm is bloat because of all the 'historical baggage' it has collected over the years.
reply
xterm is bloat, in the same sense as when some ppl using neovim say vim is bloat. It's not the usual 'python is slow, and look how many LOC that project has' kinda bloat(which xterm has some of that as well, it's more like 'that program has SO much legacy code that doesnt do anything for me'. That's vim case, and that's xterm case. if you want another opinion, read the README in the xterm repo and, as the developers themselves put it 'Abandon All Hope, Ye Who Enter Here' The only surprise after running tokei on all 5 cases you showed (plus xfce4-terminal) is that lxterm is smaller by all accounts than upstream st, that was indeed surprising. I'll probably read the code and test both to see why's that. but yeah, TL; DR, xterm is bloat because of all the 'historical baggage' it has collected over the years.
reply
Andrew
-- UPDATE -- I use xterm, but in my setup I had to use both imgt and imgc scripts as per the vifm wiki. Also, to get the images into the right pane I had to increase the FONTW value from 7 to 11. (Hey, they are both lucky numbers) With those adjustments the preview feature is now working well. Perhaps this might help in the uxrvt case, as well?
Another advantage to xterm is very low latency compared to other terminals. Plus it works well with ranger and vifm without extensions or modifications. I've been using sxiv as my image viewer in vifm via a keybind (using the sxiv thumbnail mode, but I'll have to give that imgt script a try. Thanks for another helpful video Derek!
reply
-- UPDATE -- I use xterm, but in my setup I had to use both imgt and imgc scripts as per the vifm wiki. Also, to get the images into the right pane I had to increase the FONTW value from 7 to 11. (Hey, they are both lucky numbers) With those adjustments the preview feature is now working well. Perhaps this might help in the uxrvt case, as well?
Another advantage to xterm is very low latency compared to other terminals. Plus it works well with ranger and vifm without extensions or modifications. I've been using sxiv as my image viewer in vifm via a keybind (using the sxiv thumbnail mode, but I'll have to give that imgt script a try. Thanks for another helpful video Derek!
reply
Rob
Quick tip: bind -! sxiv -t %d & - to a key in vifm and you can go to a folder of images and open them as thumbnails in sxiv. The ampersand at the end of the command sets sxiv as a background process so you can still browse with vifm while viewing the images in sxiv. I find it a better, faster way of going through images than doing it with the viewer script. Sxiv also uses Vim keybindings so it's like you're still working in vifm, just with a separate viewer.
Great show as always DT. :-)
reply
Quick tip: bind -! sxiv -t %d & - to a key in vifm and you can go to a folder of images and open them as thumbnails in sxiv. The ampersand at the end of the command sets sxiv as a background process so you can still browse with vifm while viewing the images in sxiv. I find it a better, faster way of going through images than doing it with the viewer script. Sxiv also uses Vim keybindings so it's like you're still working in vifm, just with a separate viewer.
Great show as always DT. :-)
reply
Chris
I'm learning so much about the extra stuff from you and the chats on Sundays. I'm from the old days when the only graphics from the terminal was ASCII art. My favorite was Spock next to a model of the Enterprize. The detail and shading from placement of ASCII characters was cool.
reply
I'm learning so much about the extra stuff from you and the chats on Sundays. I'm from the old days when the only graphics from the terminal was ASCII art. My favorite was Spock next to a model of the Enterprize. The detail and shading from placement of ASCII characters was cool.
reply
encycl07pedia
lol. I didn't think icons would be a reason people would not use vifm.
The color schemes and file extensions are all I personally use.
As for viewing images, I use fbi as fileviewer (in tty, obviously) and have a custom shortcut for Pix. It's really easy.
reply
lol. I didn't think icons would be a reason people would not use vifm.
The color schemes and file extensions are all I personally use.
As for viewing images, I use fbi as fileviewer (in tty, obviously) and have a custom shortcut for Pix. It's really easy.
reply
Sauron
The biggest complain I've heard about xterm isn't that it's big, it's that the code is a bit of a mess and hard to maintain - from an end user's perspective it probably makes little to no difference what terminal is installed as long as it has the features you need.
reply
The biggest complain I've heard about xterm isn't that it's big, it's that the code is a bit of a mess and hard to maintain - from an end user's perspective it probably makes little to no difference what terminal is installed as long as it has the features you need.
reply
Victor
fast tip for vifm (as you can read in vifm)
- Open editor to edit vifmrc and apply settings after returning to vifm
nnoremap, c: write - edit $MYVIFMRC - restart
so to edit vifmrc just type:
, c
reply
fast tip for vifm (as you can read in vifm)
- Open editor to edit vifmrc and apply settings after returning to vifm
nnoremap, c: write - edit $MYVIFMRC - restart
so to edit vifmrc just type:
, c
reply
Add a review, comment
Other channel videos
3:19
