Re: mcedit has failed
tgott via mc <[email protected]> Wed, 18 Jan 2023 01:28:54 +0800
| Newsgroups | gmane.comp.gnome.apps.mc.general |
|---|---|
| Message-ID | <CAKNPZSxUohD7kVu1dGErVPcif_0zvWOyTKPmDb1-=cr36Ghn1A@mail.gmail.com> |
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'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. 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