From: Stefan Monnier <monnier@iro.umontreal.ca>
To: TEC <tec@tecosaur.com>, Bastien <bzg@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] externals/org ec6d1df 2/2: lisp/ox.el (org-export-to-file): Don't load the major mode
Date: Mon, 03 May 2021 14:33:16 -0400 [thread overview]
Message-ID: <jwvfsz3smi2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20210503175719.483AE20D0E@vcs0.savannah.gnu.org> (ELPA Syncer's message of "Mon, 3 May 2021 13:57:19 -0400 (EDT)")
> 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 `auto-mode-alist' to nil, all of these undesirable
> behaviours can be avoided.
Hmm... modes don't set themselves unless we ask for it (e.g. by using
`file-find-noselect` instead of `insert-file-contents`), so maybe
a better option is to change the code that causes the major modes to be
set so that it doesn't happen?
Binding `auto-mode-alist` to nil is not the end of the world, but it's
a kind of ugly hack and inevitably comes with undesirable side-effects
(e.g. any ELisp package that happens to be loaded during this time and
whose initialization code adds/removes entries from `auto-mode-alist`
will be affected).
Stefan
next parent reply other threads:[~2021-05-03 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210503175717.27525.97949@vcs0.savannah.gnu.org>
[not found] ` <20210503175719.483AE20D0E@vcs0.savannah.gnu.org>
2021-05-03 18:33 ` Stefan Monnier [this message]
2021-05-03 19:38 ` [elpa] externals/org ec6d1df 2/2: lisp/ox.el (org-export-to-file): Don't load the major mode 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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvfsz3smi2.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tec@tecosaur.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.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).