Re: mcedit

Am 20.01.23 um 09:47 schrieb Alexander Oberhuber via mc:
> mi via mc wrote at 22:09 18.01.2023 :
> 
>> It seems a root shell invoked with e.g. sudo -s takes $HOME of the
>> admin calling it, and generally takes the admin env (but reducing it):
>>
>> From the net,
>>
>> $ sudo -s
>> Password:
>> # whoami
>> root
>> # echo $HOME
>> /Users/armin
> 
> Then the cause of your problems are clear: Some of mc's config
> file(s) can only be properly read when you are root.
> That means these config files have the wrong owner or the wrong 
> permissions.
> Solution: use "chown" and "chmod" as root to properly own your config 
> files.
> (chown -R armin folder_with_config_files and chmod -R 777
> folder_with_config_files)
> 
> 

Hi

AFAIR the primary problem was the errornous macro definition, which 
can't be found ... i think MacOS has a strange method of interpreting 
"sudo", although it has administrator account[s], you do not land there 
using sudo command but in some "hidden place".
M$ has (at least Win7pro had) a same thing: You could log in as an 
"Admin" but that was not the same than to log in as "Administrator" 
literally, the Account "Administrator" was fully hidden but existed 
anyway...
In such a accounts homedir lies the mc.macros file Ben wants to 
correct/delete, but it's hidden.
In some linux installations you don't have a "root" account as well 
(some ubuntu AFAIR) and have to do all admin things using sudo.
I never tried to find out, where the configs of mc and other commands 
called by sudo lie. Maybe MacOS has secured these places somehow, so one 
can't change them by normal systems commands... Steve Jobs cannot tell 
about this anymore ;-(

-- 
cu

jth

-- 
mc mailing list
[email protected]
https://lists.midnight-commander.org/mailman/listinfo/mc