elfmz
MobaXTerm + subj == incompatible pair?
Yes, in the description (https://github.com/elfmz/far2l?tab=readme-ov-file#compatible-terminals-and-ssh-clients), I saw a list of Windows-based (i need it only) terminals that supposedly declare full support for this combination: a File manager and a terminal/ssh-client. However, the only fresh and updated product is Windows Terminal. However, there is a problem with this as well, as not all Windows installations have this product. And this is IF! this product can be installed or updated... However, it is often not possible to do so. Additionally, it is not portable.
As a result, the only option is to use SSH-client=PuTTY... However, there is also a problem with updates! Currently, the latest version is 0.83, but the links only provide information about 0.76. As a result, it is actually impossible to use any of these products. This is where MobaXTerm comes in. Unlike all the others - it is well maintained and updated. BUT! for some reason in it Far2l looks completely different in colors and it slows down wildly even for the simplest action, such as moving the selection cursor down in the file panel!
This is how the subject is displayed in this terminal, which is completely incorrect in terms of colors. It is faded and completely unreadable.
This raises the question of what and how it suddenly became so incompatible that even the colors were incorrect? Maybe it is worth writing to the authors of MobaXTerm and offering collaboration? Or at least informing them about the errors that may be causing this behavior.
For the colors -- please read https://superuser.com/questions/721964/mobaxterm-colors-are-washed-out-how-to-configure-the-scheme
For the slow cursor movement -- please clarify your use case. Are you on Windows and accessing remote linux host via ssh? Or maybe you are trying to "just" access to WSL? You not always need terminal to do it.
Please try to remove color settings files
rm ~/.config/far2l/settings/colors.ini ~/.config/far2l/settings/farcolors.ini ~/.config/far2l/palette.ini
and restart far2l
Are you on Windows and accessing remote linux host via ssh?
exactly.
Please try to remove color settings files
from MobaXTerm Point of View - no diff. From regular PuTTY PoV - as it was normal and it still is normal: as before deleting so and after.
~~> For the colors -- please read~~
~~this suggestion is properly changing a color of terminal itself. But NOT the color of the Far2l' panels and GUI.~~
Ouch, sorry - in fact it does work, but... But I don't understand what exactly needs to be changed so that the colors are just exactly what the developer programmed. That is, when I changed the terminal colors in the session settings via MobaXterm, yes, I got a color change both in the terminal panel and in the Far2l panels. It seems like it's good... BUT! if we compare the color codes from the PuTTY and MobaXterm terminals, they have become close and similar, but they are still not equal. That is HOW should I set up the session? It seems like PuTTY doesn't set colors in a some special way.
P.S.
Basically, I'm saying that if there really is a specific setting for color rendering in the PuTTY terminal window, then maybe we should contact the MobaXTerm developers and suggest to them a fix of a color mapping of their internal "colors" so that after applying it, we could get the exact same panel in Far2l/MC as it's drawn in PuTTY?
For example - no matter what I choose in the available settings within MobaXTerm - I can't get the same brightness of colors. Everything is constantly rendered in very dirty dark tones. As if another light filter has been applied.
@Dazzar56 looks like something about windows terminal app, can you look at it pls?
If Putty's terminal palette is the measure of normality -- one can always replicate exactly this palette in mobaxterm, tool like "Autohotkey Window Spy" will give the exact color value of the favorite area of the screen. Only 16 colors are to be picked, like maybe 15 minutes of work. OR There are dozens of pre-defined palettes for MobaXterm (https://github.com/mbadolato/iTerm2-Color-Schemes/tree/master/mobaxterm)
Just a moment... do you mean that the color is determined solely by the user? And the fact that PuTTY has some predefined 16 colors is just a coincidence, that the colors match those provided by Windows itself? Because if I run FAR under Windows and compare the panel colors with those that will be used in FAR through PuTTY - they match. And they could have not matched? And they could have been completely different???
Well, then the question arises - where do I get those 16 color squares from PuTTY? To get (set myself?) exactly the same ones in MobaXTerm? PuTTY is a portable one!
Okay, regarding the color issue - we've probably almost sorted it out. Or I'll sort it out in the near future.
BUT the problem with the interface/interaction slowdowns with Far2l inside the MobaXTerm terminal - this question hasn't been mentioned at all yet. Were you able to simply install this program - and make sure that the slowdowns of the subj are present in it? I'm currently observing this on the Ubuntu 24.04.3 LTS distribution.
Okay, regarding the color issue - we've probably almost sorted it out. Or I'll sort it out in the near future.
BUT the problem with the interface/interaction slowdowns with Far2l inside the MobaXTerm terminal - this question hasn't been mentioned at all yet. Were you able to simply install this program - and make sure that the slowdowns of the subj are present in it? I'm currently observing this on the Ubuntu 24.04.3 LTS distribution.
Installed mobaxterm with all defaults. colors are fine by the way Interface responsiveness is also fine with remote host in the same lan. Will try to attach the video
If remote pc is far away interface lag will certainly be observable. That's why I personally always run far2l locally and go to remotes via netrocks
https://github.com/user-attachments/assets/4d409046-bd71-47b4-b9db-dceb5816892b
Yes - everything looks more than worthy and pleasing to the eye. And from this the situation only worsens on my side - because I did not do anything with the installation of MobaXTerm - but for some reason the colors are completely different.
About the slowdown. I understand that the distance can certainly play its role. BUT it then should affect ALL programs running on the remote host. And this is not the case with me - the same MC running there - will simply be displayed instantly. But only FAR will slow down...
And IF i will connect through the recommended but outdated putty4far2l - both programs will work instantly.
P.S. the last clarification: far2l is in TTY X/Xi backend running. NO gui.
Yes - everything looks more than worthy and pleasing to the eye. And from this the situation only worsens on my side - because I did not do anything with the installation of MobaXTerm - but for some reason the colors are completely different.
About the slowdown. I understand that the distance can certainly play its role. BUT it then should affect ALL programs running on the remote host. And this is not the case with me - the same MC running there - will simply be displayed instantly. But only FAR will slow down...
And IF i will connect through the recommended but outdated putty4far2l - both programs will work instantly.
P.S. the last clarification: far2l is in TTY X/Xi backend running. NO gui.
No idea from my side then. I can only provide versions of software from above video and suggest to reset mobaxterm configuration (saw this option in its interface). So. My far2l version is: 2.6.5-2025-10-19-c35f8e4-beta on Ubuntu 24.04.3 LTS (xubuntu) Mobaxterm version I downloaded and installed: Personal Edition v25.3 Build 5384 on Win11
Cursor movement issues frankly sound like a very old version of far2l, did you install far2l from Ubuntu repos or from ppa? I strongly suggest the latter option
of course from Ubuntu repo. If we are talking about a product that has become a full-fledged component of freely distributed OS distributions, then of course installation should only take place using their official repositories. Have you stopped posting up-to-date product development codes in them? IS the official Ubuntu repo Far2l is outdated now? for how long?
OK, this is what I've got: yep , some garbage data was present inside the main INI file for MobaXTerm. After reset conf - I could replicate smooth cursor movement and interaction with FAR's file panels. So here my problems were solved. But even with a new conf I could not get these proper colors, which were shown in a video above. So yes - here I had to make some additional steps in order to import a proper color scheme, and so now FAR is looking good as it should.
And basically this issue can be closed. Yep, strange things happens...... Well, thank you all for your helpful solutions to my problems, and good luck with your own problems and tasks!
OK, this is what I've got: yep , some garbage data was present inside the main INI file for MobaXTerm. After reset conf - I could replicate smooth cursor movement and interaction with FAR's file panels. So here my problems were solved. But even with a new conf I could not get these proper colors, which were shown in a video above. So yes - here I had to make some additional steps in order to import a proper color scheme, and so now FAR is looking good as it should.
And basically this issue can be closed. Yep, strange things happens...... Well, thank you all for your helpful solutions to my problems, and good luck with your own problems and tasks!
IS the official Ubuntu repo Far2l is outdated now? for how long?
Official Debian and Ubuntu repos is not rolling and has version of package, which is fixed at the time of the distribution's release and during the life of the distribution all packages in official non-rolling distribs obtain only security bug-fixes (see https://github.com/elfmz/far2l/#debian ) .
If you want the latest far2l you should completely remove current version far2l from your system (sudo apt remove far2l*) and install from community PPA: see tips in popup block in https://github.com/elfmz/far2l/#community_bins
Note: The official Ubuntu 24.04 LTS has far2l 2.6.0, but fully RGB support since far2l 2.6.2 (changelog).
Note: far2l reinstall don't update user far2l configuration, you should manually remove outdated configs from ~/.config/far2l (for colors simple delete 3 files: ~/.config/far2l/palette.ini, ~/.config/far2l/settings/colors.ini and ~/.config/far2l/settings/farcolors.ini and re-open far2l).
OK thanks again for a such productive notes! I appreciate this !
And please don't forget to close the issue.
There's no need to multiply entities.
And please don't forget to close the issue.
@gh-Destiny Please close the issue yourself.