From: Timothy <firstname.lastname@example.org> To: org-mode-email <email@example.com> Subject: [PATCH] avoid loading major modes when exporting to file Date: Wed, 31 Mar 2021 23:25:51 +0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) [-- Attachment #1: Type: text/plain, Size: 201 bytes --] Hello, Another little patch, this time a one-liner. 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. -- Timothy [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #2: 0001-ox-don-t-load-a-major-mode-when-exporting-to-file.patch --] [-- Type: text/x-patch, Size: 1406 bytes --] From eb9d7c038dbb9e7a4b89edf61db83a31dda27170 Mon Sep 17 00:00:00 2001 From: TEC <email@example.com> Date: Wed, 31 Mar 2021 23:16:58 +0800 Subject: [PATCH] ox: don't load a major-mode when exporting to file * lisp/ox.el (org-export-to-file): Prior to this, when `org-export-to-file' was 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. --- lisp/ox.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/ox.el b/lisp/ox.el index f705bc83a..96d2866dd 100644 --- a/lisp/ox.el +++ b/lisp/ox.el @@ -6388,7 +6388,8 @@ (defun org-latex-export-to-latex (declare (indent 2)) (if (not (file-writable-p file)) (error "Output file not writable") (let ((ext-plist (org-combine-plists `(:output-file ,file) ext-plist)) - (encoding (or org-export-coding-system buffer-file-coding-system))) + (encoding (or org-export-coding-system buffer-file-coding-system)) + (auto-mode-alist nil)) (if async (org-export-async-start `(lambda (file) -- 2.30.1
next reply other threads:[~2021-03-31 15:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 15:25 Timothy [this message] 2021-05-01 16:52 ` Bastien 2021-05-01 17:26 ` Timothy 2021-05-03 17:25 ` Bastien
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] avoid loading major modes when exporting to file' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).