On Tue, 14 Nov 2023 13:26:38 -0600 Ranjan Maitra via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Mon Nov13'23 11:41:28AM, George N. White III wrote: > > From: "George N. White III" <gnwiii@xxxxxxxxx> > > Date: Mon, 13 Nov 2023 11:41:28 -0400 > > To: Community support for Fedora users > > <users@xxxxxxxxxxxxxxxxxxxxxxx> Reply-To: Community support for > > Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> Subject: Re: emacs is > > hopeless > > > > On Mon, Nov 13, 2023 at 9:04 AM Ranjan Maitra via users < > > users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > > > > [...] > > > I also tried emacs-nox and have the same problem. Removing my > > > .emacs did not have any effect. > > > > > I do not mess with my system files so I am a bit confused as to how > > to > > > track this down. Is there a > > > > > verbose mode which allows me to see what to do? > > > > > > > Try running emacs as newly created user to rule out something in > > your ~/.emacs.d or some > > shell startup script creating variables that confuse emacs. Have > > you tried "emacs -nw" for text mode > > to rule out a GUI issue? > > > > It might help to have a simple example with a description of what > > happens. If emacs is failing due to > > some conflict with libraries you might see an error with > > journalctl. Make a note of the time the error > > occurs to help identify related errors. > > > > > > > > > > I have emacs-ess also installed (from Fedora 36) that has not > > > been updated and is probably obsolete or retired. > > > > > > > Probably good to remove that old package. You can reinstall from > > upstream source if Fedora 39 doesn't have a > > package. > > Indeed, the culprit appears to have been the emacs-ess package, which > was creating issues even with it not being called. > > Unfortunately, for me, emacs-ess was the main selling point of emacs, > and with that rendering emacs unusable, it appears that I will have to > move on to nvim which has a good R interface. > > What really irritates me about vi and its friends is that it throws > you out of editing (insert) mode in order to save the file, and needs > another key to come back in. I work around that by configuring hh and uu as <ESC>. Since I (almost) always finish input by pressing one of them, the command mode is available, so I just hit :w <ENTER> to save. I guess it is a matter of taste, a trade off. > I don't know if it is possible to remap a key (say C-x-C-s) that would > exit the "insert" mode, save the file, and then come back into the > "insert" mode. It is possible to record a macro, by assigning it to a key. e.g. for key r qr [record what you want to do here, whatever does what you want above] q invoke the macro with @R or @r. You can map keys to sequences of commands using the map command. :map <F2> @r Then whenever you want to invoke the file save, just hit F2. I haven't tried the above, but it should work. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
