Bastien <b...@gnu.org> writes:
> This even be "auto-mode-alist" instead of "(auto-mode-alist nil)". Ah, it can indeed. > I'm still unsure the patch is correct: what if people *need* major > mode initialization before any contents is exported to a file? I haven't responded to this concern, because I haven't been able to conceive of a single situation where loading the normal-mode for the exported file could be desirable. >> I think the commit description is pretty thorough, so give that a look. >> TLDR; it makes `org-export-to-file' behave a bit more nicely. > > I find it useful to have a small description of the change and why it > is needed in the body of the email, when a patch is attached. I think I may have been become overly used to how convenient mu4e is for showing patches inline 😅. For the sake of anyone just looking at the Email body, here's what I considered to be an informative commit message, subtly reworded: Currently, when `org-export-to-file' is called it activated the major mode for that file type based on `auto-mode-alist'. This can be mildly annoying in various ways as loading the major mode: 1. makes the export take longer 2. can produce unwanted "noise" while initialising, namely warnings and errors related to the mode itself 3. can produce spurious files like an .auctex-auto folder By locally binding `auctex-auto' to nil all of these undesirable behaviours can be avoided. -- Timothy
