Re: mcedit has failed

Ben via mc <[email protected]> Tue, 17 Jan 2023 11:09:34 -0700
Newsgroups gmane.comp.gnome.apps.mc.general
Message-ID <CANv=BrpfqH4voVQKFPrJ7c487kWzWHTBCv7S9-paQPJFuMuE=A@mail.gmail.com>
On Tue, Jan 17, 2023 at 10:28 AM tgott via mc <
[email protected]> wrote:

> You can access the file by running the command in terminal :
>
> nano ~/.mc/mcedit.ini
>
> If the file doesn't exist, you can create it.
>

It doesn't exist now.

There's a macro that runs resulting from RETURN being pressed in the
sudo-driven instance of mcedit; it hasn't been saved in a file that does
not exist, right?


> It's also worth mentioning that some versions of mcedit may not use a
> configuration file and instead rely on environment variables or
> command-line options to set their settings.
>

There's nothing in ENV that is storing mcedit macros. My ENV is pretty
simple, so it's easy to tell.

Likewise, there are no aliases hiding command line options that would
confuse matters.

I checked both as me, and via sudo to make sure that was the case across
the board.

It's also worth noting that this macro is not happening in the normal user
mode. Unfortunately, many of the files I edit are higher security. I've
been moving them back and forth and chmod'ing them in both directions to
work around this, but it's annoying as heck, even script-driven.

--Ben



>
> On Mon, Jan 16, 2023, 23:16 tgott <[email protected]> wrote:
>
>> Have you tried:
>> nano ~/.mc/mcedit.ini
>>
>>
>> On Mon, Jan 16, 2023, 22:55 Ben via mc <[email protected]>
>> wrote:
>>
>>> I was editing a text file, and at one point I defined a macro for q,
>>> which worked;
>>>
>>> But I may have hit something else, I don't know, and mcedit fell into a
>>> round of assertions so fast I couldn't read them go by.
>>>
>>> I killed the shell (mcedit wasn't responding to control-c), restarted
>>> mcedit to edit the file again and...
>>>
>>> (1) it said there was a lock on the file and I could not save, nor could
>>> I find a way to remove the lock;
>>>
>>> (2) pressing return appears to run the Q macro, which is "move down a
>>> line and delete about 20 characters."
>>>
>>> I can't find where mcedit has its settings; I'm running MacOS Ventura
>>> 13.0.1 and mcedit 4.8.28
>>>
>>> I've looked in:
>>>
>>> ~/.config/mc/mcedit  (empty)
>>> ~/.local/share/mc/mcedit  (empty)
>>>
>>> Can anyone help me get mcedit back to its initial state?
>>>
>>> TIA
>>>
>>> --Ben
>>>
>>>
>>>
>>>
>>> --
>>> mc mailing list
>>> [email protected]
>>> https://lists.midnight-commander.org/mailman/listinfo/mc
>>>
>> --
> mc mailing list
> [email protected]
> https://lists.midnight-commander.org/mailman/listinfo/mc
>

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