Feature: Server/client architecture to manage multiple instances

[rafo]

I love Felix! Almost everything works "just like that," without much configuration. Even the Vim shortcuts are almost perfect.

What I still need is a server/client architecture and remote commands to manage multiple instances.

When I open multiple tabs or windows in Kitty or split a window, I could start two Felix instances and use Felix like the Norton Commander (or Total Commander, etc.).

to quote lf:

It is often useful to open a file manager in multiple paths at the same time to copy files between directories. Instead of implementing tabs or panes, lf uses a server/client architecture for this purpose to fit your existing workflow. A server process is automatically launched in the background when you run lf command for the first time. This process saves the names of files to be copied or moved so that you can copy files in one client and paste them in another. This feature requires no configuration and it can be used with either multiple terminals or a multiplexer such as screen or tmux:

NNN uses a different approach and implements a realy fast 1,2,3,4 tab system. But I think this is a complex solution and lacks the benefit of a better overview.

But I am aware that a server/client architecture is also complex and requires a lot of work.

Cudos!

[kyoheiu]

First of all thank you! Such words are huge to me.

And about the architecture, let me understand what to think:

• For what you'd like to run multiple instances of this app?
  • Like, to yank & put, or share PWD(i.e. when you open the second instance, it automatically opens PWD of the first)?
• IMO the client-server architecture is different from multi-tab/multi-pane, because the latter is the UI thing (client-server may enable you to open the instance in another terminal/multiplexer, which I think the quote you gave says). What would be better for you, according to what you'd like to accomplish?