From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 'Kevin Rodgers' <kevin.d.rodgers@gmail.com>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: new buffer - should its mode reflect its name when the name matches auto-mode-alist?
Date: Fri, 25 Sep 2009 12:04:05 +0300 [thread overview]
Message-ID: <87fxabmk8d.fsf@mail.jurta.org> (raw)
In-Reply-To: <jwveipvkgqr.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 24 Sep 2009 20:38:23 -0400")
> I'm not opposed to such a change but I think it would need to come
> together with a cleanup of the "default-major-mode" thingy: currently,
> the major-mode of a buffer is either set (in set-buffer-major-mode) as
> (default-value 'major-mode) or (if that's nil) is inherited from the
> major-mode of the current-buffer (unless that major-mode has the
> `mode-class' property set to `special').
>
> In practice, for 99% of the users, (default-value 'major-mode) is
> fundamental-mode, so the rest is very rarely used, which can lead to
> corner-case bugs, of course.
Using (setq-default major-mode 'normal-mode) would be a good default.
Currently this runs into an infinite recursion. However, the following
succeeds:
(setq-default major-mode
(lambda () (let ((buffer-file-name (buffer-name)))
(set-auto-mode))))
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-09-25 9:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 14:31 new buffer - should its mode reflect its name when the name matches auto-mode-alist? Drew Adams
2009-09-22 14:47 ` Deniz Dogan
2009-09-22 15:07 ` Drew Adams
2009-09-23 20:50 ` Mathias Dahl
2009-09-24 21:07 ` Juri Linkov
2009-09-24 2:31 ` Kevin Rodgers
2009-09-24 3:14 ` Drew Adams
2009-09-24 21:32 ` Juri Linkov
2009-09-24 22:01 ` Drew Adams
2009-09-25 0:38 ` Stefan Monnier
2009-09-25 9:04 ` Juri Linkov [this message]
2009-09-25 14:16 ` Stefan Monnier
2009-09-29 23:11 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fxabmk8d.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=kevin.d.rodgers@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.