RIch, More context needs to be provided to answer your question.
1. Have you recently updated the version of Emacs? If so I'd recommend reading through the change list for the new version of Emacs. I have my doubts that a new version of Emacs would suddenly invert the established paradigm. That said there was a significant sea level shift many releases ago regarding *transient mark mode*. 2. Have you recently made changes to your *init* file? Invoking Emacs with *emacs -Q* is always a good place to start in debugging unexpected behavior in Emacs. This gives you a vanilla configuration, without any of your favored customizations. If the behavior goes away it's time to review your *init* file. 3. Are you running a *server instance* of Emacs? If you're running Emacs as a persistent server, then any state changes made to the Emacs environment persist in the server. Force the server to stop via the *M-x kill-emacs* command, and restart your server instance. 4. Did you copy/paste/evaluate some ELisp from the web? Maybe the new behavior was inadvertently self-inflicted? On Thu, Jan 23, 2025 at 3:46 PM Rich Shepard <[email protected]> wrote: > On Thu, 23 Jan 2025, Rich Shepard wrote: > > > The results are all in the brave browser cache. > > Loading a new emacs seems to have resolved the temporary overwrite issue. > It > comes up in `text fill' mode. > > So far so good. > > Rich >
