A practical application is if I have been using the
built-in elisp mode for .el files and then implement
xah-elisp-mode, even if I code
(add-to-list 'auto-mode-alist '("\\.el$" . xah-elisp-mode))
You keep track of what's already there? Maybe it's
the first hit that gets executed. But I suppose one
don't tell that .el files should be
`emacs-lisp-mode'. What mode do they turn up in?
If you just create a test.el, I mean?
I do this, it is more clear IMO:
;;; -*- lexical-binding: t -*-
;;;
;;; this file:
;;; http://user.it.uu.se/~embe8573/emacs-init/mode-by-filename.el
;;; https://dataswamp.org/~incal/emacs-init/mode-by-filename.el
(let ((modes (list
'("\\.bal\\'" . balance-mode)
'("\\.gpi\\'" . gnuplot-mode)
'("\\.lu\\'" . lua-mode)
'("\\.nqp\\'" . perl-mode)
'("\\.php\\'" . html-mode)
'("\\.pic\\'" . nroff-mode)
'("\\.pl\\'" . prolog-mode)
'("\\.tex\\'" . latex-mode)
'("\\.xr\\'" . conf-xdefaults-mode)
'("*" . text-mode) )))
(setf auto-mode-alist (nconc modes auto-mode-alist)) )
in my init.el, the previously visited buffers that
are automatically opened when I start emacs will
still be in elisp-mode. The fix, of course is to
invoke xah-elisp-mode from the minibuffer. This is
certainly doable, even with multiple elisp buffers
opened, but I'm always looking to
eliminate redundancies.
No, that stinks, that should be automated.
I'm unfamiliar with this automatically opened
principle tho and if I have it (I don't think so)
I would like it inhibited, pretty please?