You have two options in general.
Changing MC keybindings through editing `$HOME/.config/mc/mc.keymap`
Changing Nano keybindings through editing `$HOME/.nanorc`
Both are well documented in their respective "Info" entry and also their
"manpages".
For example:
```
$ info nano
$ info mc
$ man nano
$
Hi,
take a look atman nano REBINDING KEYS .
Disclaimer, I didn't read it, so I don't know what exactly you can do.
I'm using a ~/.nanorc for a customized universal light-on-dark syntax
highlighting, not to modify shortcuts.
Regards,
Ralf
--
mc mailing list
On Sat, 27 Jan 2024, Alexander Oberhuber via mc wrote:
So how do I handle the mc to work with nano as editor and avoid the
triggering of CTRL+O ?
You should be able to unbind or change "Shell" keymap shortcut:
https://github.com/MidnightCommander/mc/blob/master/misc/mc.default.keymap#L32
--
Hello,
I have a tiny little stupid question: I never use CTRL+O, and I don't
intend to.
But when I use "nano" as an editor, CTRL+O is assigned the "save
file" function, which is essential.
So how do I handle the mc to work with nano as editor and avoid the
triggering of CTRL+O ?
--
mc mailing
> A. Should mc give that rule up and maintain two independent shells ?
Isn't an independent shell already accessible by many other means?
* In _Linux console_, it's accessible through `Alt+Fn(s)` or `Alt-Right/Left`
arrows to switch between other TTY(s). They each have an independent shell.
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I'm glad to be finally able to announce the immediate availability of
mc-4.8.31, a maintenance and bugfix release of Midnight Commander!
There are no significant changes in this release other than bugfixes. Most
notably, we have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I'm glad to be finally able to announce the immediate availability of
mc-4.8.31, a maintenance and bugfix release of Midnight Commander!
There are no significant changes in this release other than bugfixes. Most
notably, we have
I have to review myself.
Jan 25, 2024, 14:54 by arash@tuta.io:
> Furthermore, I invoke MC in WezTerm with `TERM=xterm-256color mc`. To make
> mouse working properly.
One can use `mc -x` instead of `TERM=xterm-256color mc` to invoke midnight
commander with mouse support in terminals that
So, so sorry for the delay.
Jan 25, 2024, 21:43 by mc@lists.midnight-commander.org:
> Did you test the cd's while a command is _still running_ in the subshell ?
I do NOT confirm this one! If a command is _still running_ in the subshell in
the background, navigating between directories in MC
