Re: mcedit

Perhaps under /root/.mc/  ?

Cheers, brickviking

On Tue, 17 Jan 2023 at 04:52, Ben via mc <[email protected]>
wrote:

> On Mon, Jan 16, 2023 at 8:26 AM Grzegorz Szymaszek <[email protected]>
> wrote:
>
>> On Mon, Jan 16, 2023 at 07:55:15AM -0700, Ben wrote:
>> > [...] restarted mcedit to edit the file again and [...] it said there
>> > was a lock on the file and I could not save, nor could I find a way to
>> > remove the lock;
>>
>> Did it show _the_ "File locked" dialog? See the source code if not sure:
>>
>> https://repo.or.cz/midnight-commander.git/blob/55124be9bb0d9a3f5dddf16b32a3cf039d5b82d3:/lib/lock.c#l237
>>
>> https://github.com/MidnightCommander/mc/blob/55124be9bb0d9a3f5dddf16b32a3cf039d5b82d3/lib/lock.c#L237
>>
>> If your file is named "foo.txt", is there a ".#foo.txt" file in the same
>> directory?
>>
>
> Yes, deleting it took care of the lock, thank you
>
>
>> > I can't find where mcedit has its settings [...]
>>
>> Try "mc -F".
>>
>
> That worked for the normal user, but I was editing via sudo, and it
> doesn't seem to have any info on the mcedit settings for the system wide
> portion.
>
> So, further, as I said pressing return seemed to run the q macro. So I hit
> ^r, it said to enter the macro key, I pressed return, and again, MCEDIT
> entered into a raging loop of assertions I had to quit the shell (and
> therefore the mcedit) to exit.
>
> So it appears that:
>
> (a) the macro is assigned to return, and
> (b) I can't get rid of the return macro IN mcedit, and
> (c) mcedit has a crashing bug (press return in macro assignment), and
> (d) I can't locate where mcedit saved its settings when running as root
> --
> 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