bash doesn't understand '\' as path delimiter, so wouldn't offer completion if paths are typed with '\', also '\' would have to be quoted or escaped since otherwise bash would treat them as escape sequences but '\' would have to be used from time to time, since some Windows tools support only '\' paths. Tab!), how to deal with that? Then, how can Far intercept it's internal commands which shouldn't be executed by bash, but by Far itself (lm:load, far:config etc.)? There probably will be some extra difficulties to use some Windows-specific commands - e.g. It would give bash completion and hotkeys, but some bash's hotkeys already have some usage in Far (e.g. I guess this is easier to implement, but doesn't give bash's completion or hotkeys.ģ) Completely replace the command entry with bash, I can see some extra difficulties in implementing this. If the command is not an internal Far command, execute it using an arbitrary configured shell (e.g. lm:load, far:config etc.), if so - handle it appropriately. When pressing enter to execute command, Far can check if the command is actually an internal Far command (e.g. This can be already implemented quite easily as a macro (I think).Ģ) Far takes care of command entry. AltEnter) which would execute the current command line using a specified shell. The question here is:ġ) Simplest addition - add an extra hotkey (e.g.
0 kommentar(er)
