3 ms·
""" You need to take some steps to make MC to exit in the current directory visible on the screen. One way is to use alias such as alias mc='mc -P "/tmp/mc-$US
by cassepipe 5y ago
"""
You need to take some steps to make MC to exit in the current directory visible on the screen. One way is to use alias such as
alias mc='mc -P "/tmp/mc-$USER/mc.pwd.$$"; cd `cat /tmp/mc-$USER/mc.pwd.$$`; rm /tmp/mc-$USER/*'
The other is to use a supplied with mc more generic script
alias mc='. /usr/libexec/mc/mc-wrapper.sh'
One of the most common problems with mc is incorrect display of pseudo-graphical characters, which spoils borders on the panels and while this defect does not affect functionality, is very unpleasant aesthetically. See Midnight commander does not display pseudo-graphic characters properly for more information. You can use option -a to use regular characters instead and in most cases this is an adequate solution.
"""
Hell, no. I am glad I learned vim and I am still using it a lot but I am not going down another rabbit hole where easy and simple things are ... contorted. And I don't want to take care about another configuration file in order to feel at home. I just want sane defaults, simple things made easy and complex task possible.
What I like about vim is that the modal editing paradigm. All the rest could be better and whenever Neovim or Helix or Amp or Onivim or any other terminal editor/ide is 1.0, I'll jump ship. Navigating files with the command line is not that complicated imho.
I don't blame Vim, maybe it was not meant to be an IDE. Maybe we need a terminal IDE.
- unilynx 5y agoYou don't need to set up that alias. I'm guessing it's a holdover from the DOS days with Norton commander where you would launch nc just to quickly navigate to a directory and then quit it, which can't easily be done on Unix. (the current drive/directory was global state in DOS - it even recorded the current directory per drive, but that may only have been command.com doing that)
- tinus_hn 5y agoNote that this kind of scripts is a security issue if the system does not implement per-user tmp directories, especially if it regularly cleans the /tmp directory. Which this script appears to expect.