Installation failed under Debian 9.8 (X11 needed??)

[mr-older]

The following packages have unmet dependencies:
libgl1-mesa-dev : Depends: x11proto-dri2-dev (>= 2.6)
Depends: x11proto-gl-dev (>= 1.4.14)
E: Unable to correct problems, you have held broken packages.

Does it need X11?

Far was (!) and is (!) a console program under Windows, not desktop one. So I supposed to run it as MC, with no X installed. Far is often used in administration purposes, so running in console is essentially important. Most servers don`t need X installed: it is a bad practice, causing unwanted troubles.

Such a change in the whole paradigm of the application... makes it a Total Commander or so, isn't it?

[elfmz]

Configure with -DUSEWX=no if dont want GUI mode.
Note that usual terminals have quite limited and picky support of extended keys/modifiers so usual using of far is quite inconvinient. However if you will locally run far2l in GUI mode and inside of its pseudoterminal will run remote far2l in terminal mode - they will interconnect using private escape sequences that will provide full-featured keyboard shortcuts support.

[mr-older]

Thank you very match for the answer, it was successfully compiled and works as described above: many of keyboard shortcuts are unavailable.

However if you will locally run far2l in GUI mode and inside of its pseudoterminal will run remote far2l in terminal mode - they will interconnect

Is it possible to link in a such manner Windows Far and Linux Far?

[elfmz]

Nope, but it theoretically possible to run far2l under Windows/wsl/x11: https://www.scivision.dev/x11-gui-windows-subsystem-for-linux/
PS it looks little bit pervertedly :)

[unxed]

pervertedly

Is it theoretically possible to write Far for Windows plugin that will intercept keypresses and translate them to far2l-compatible escape sequences for openssh command line client running under Far for Windows?

:)

[elfmz]

Well, its possible by adding terminal emulator (with far2l extensions) into NetBox plugin. If someone really need it - he may try to do this :)
It will also make built-in NetBox SSH commands executor more usable not only to run far2l.

[elfmz]

About pervertions. I've just managed to compile&run under cygwin far2l with Blackjack and NetRocks. And connected to Linux and ran remote far2l inside.

[elfmz]

Here is what selected in cygwin installer:

Then in cygwin's shell:

• followed normal far2l/cmake build sequence
• started X server:

export DISPLAY=:0.0
startxwin >/dev/null 2>&1 &

[unxed]

not to click by hands:

setup-x86_64.exe -P cmake,cygwin32-gcc-core,cygwin32-gcc-g++,gcc-core,gcc-g++,git,imake,libneon-devel,libneon27,libnfs-devel,libnfs8,libssh-common,libssh-devel,libwxbaseu3.0-devel,libwx_wtk2u3.0-devel,libwx_gtk3u3.0-devel,m4,mingw64-i686-gcc-core,mingw64-i686-gcc-g++,mingw64-i686-pthreads,mingw64-i686-winpthreads,mingw64-i686-wxWidgets3.0,mingw64-x86_64-pthreads,mingw64-x86_64-wxWidgets3.0,wget,xinit,xlaunch,xorg-server

If you have problems with keyboard layout switching, add something like

XKBLAYOUT us,ru
XkbOptions grp:alt_shift_toggle

to .XWinrc file in your cygwin home folder (you may need to create that file if not exists).

[unxed]

under cygwin

Can wx be tuned to use native GDI instead of x11 on windows?

[elfmz]

Issue tracker of NetBox is more suitable place to discuss this concept, I guess :)

Original FAR's folks not happy about far2l, so patching cygwin to use GDI directly looks more feasible:)

[unxed]

Issue tracker of NetBox is more suitable place to discuss this concept, I guess :)
Original FAR's folks not happy about far2l, so patching cygwin to use GDI directly looks more feasible:)

As I can see in NetBox issue, I've got a problem with explanation, that do we really need from NetBox:
michaellukashov/Far-NetBox#292 (comment)
Could you please just help with more clear wording in Russian? Maybe Far folks not treat it as reasonable, but someone else who will see the issue does? :)

patching cygwin to use GDI directly looks more feasible :)

Patching cygwin, not cygwin's wx? o_O

Anyway, windows far2l port is the thing that I predicted months ago))) Cross platform Far is more tasty thing than windows-only features like ntfs streams :) And all of those can be backported from upstream if needed by anyone. As for console emulation with wx instead of native console, it's actually not a problem on modern machines. In addition, another backend, "windows console" can also be added, like wx and tty.

Btw, how does far2l --tty behave under cygwin? Does it work inside console as needed? What about hot keys?

[elfmz]

Btw, how does far2l --tty behave under cygwin?

Badly, in overall not better that in Linux/bash, but (i didnt tested throughouly) it also looks that cygwin terminal has own special bugs :)

[unxed]

Badly, in overall not better that in Linux/bash, but (i didnt tested throughouly) it also looks that cygwin terminal has own special bugs :)

Maybe this one serves better?
https://conemu.github.io/en/CygwinMsysConnector.html

This helper tool is an attempt to create the symbiont of POSIX enabled pty and WinAPI full-featured terminal.

Btw, maybe we can rename this issue to "cygwin port" or place this comment in a wiki howto page? Using remote far2l from windows via cygwin is nice option nobody actually knows about :)

[unxed]

it theoretically possible to run far2l under Windows/wsl/x11: https://www.scivision.dev/x11-gui-windows-subsystem-for-linux/

People are already doing that actually :)

[mr-older]

Btw, should we rename this issue now? Something like "running remote far2l from windows box"?

Look... Linux servers, where terminal client access from Windows is appreciated using FAR, don't need Xs. Setup X11 (seems that cygwin much lighter, but still...), setup X11 only for FAR results in loosing resources and getting a bunch of dependencies, not worthing the goal. So... question is as is. Posts with X11 screenshots aren`t helping to solve the issue anyway. So... Netbox and SSH stay the only option for now. Not functional enough, but... the only one. Cause linux terminal isn't catching all keyboard shortcuts. That is.

The question may be closed, other discussions are far away from the main point: FAR (far2l) is not a terminal app for Linux. Here goes a big and sad smiley.

[elfmz]

FAR (far2l) is not a terminal app for Linux.

My usual usecase of far2l via SSH is

• run GUI far2l on machine
• connect to SSH server with NetRocks/SFTP (or SCP)
• run server-side far2l (built without WX) directly from NetRocks command line
  -... voila! working in remote terminal-only far2l with all shortcuts etc

Since unxed made patched putty version same experience now also possible from Windows on client-side too. Also me didn't test it well

[unxed]

-... voila! working in remote terminal-only far2l with all shortcuts etc

I'm using this method literally every day :)

Since unxed made patched putty version same experience now also possible from Windows on client-side too. Also me didn't test it well

According to habr, some people are already using it (github clone stats says the same), still no issues on github currently. I'm surprised that so rough code can do the job well enough.

[unxed]

Badly, in overall not better that in Linux/bash, but (i didnt tested throughouly) it also looks that cygwin terminal has own special bugs :)

It is interesting, of course, how the TTY|Xi backend would behave in cygwin. Would you get a normal input, or not?

[elfmz]

If start X server under cygwin - then may be it will work..
BTW it doesnt work under MacOS if start xquartz, so prebuilt dmg-s for macos dont have TTYX enabled

[unxed]

If start X server under cygwin - then may be it will work..

What is the difference between starting X server under cygwin and using windows native X server like XMing in this case?

BTW it doesnt work under MacOS if start xquartz

Very strange. Maybe DISPLAY variable should be set or something like this?