From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r105470: Improve documentation of `special' modes. Date: Wed, 17 Aug 2011 10:02:16 -0400 Message-ID: References: <838vqttoaf.fsf@gnu.org> <831uwkttig.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1313589758 10280 80.91.229.12 (17 Aug 2011 14:02:38 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 17 Aug 2011 14:02:38 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 17 16:02:35 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QtghW-0008Iz-Pw for ged-emacs-devel@m.gmane.org; Wed, 17 Aug 2011 16:02:34 +0200 Original-Received: from localhost ([::1]:44475 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtghV-0007J2-SS for ged-emacs-devel@m.gmane.org; Wed, 17 Aug 2011 10:02:33 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:39343) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtghT-0007Ix-9a for emacs-devel@gnu.org; Wed, 17 Aug 2011 10:02:32 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QtghN-00028j-AX for emacs-devel@gnu.org; Wed, 17 Aug 2011 10:02:31 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.183]:17317 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtghI-00028R-LV; Wed, 17 Aug 2011 10:02:20 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EAJDJS05Ld+HZ/2dsb2JhbABCqGh4gUABAQQBViMFCws0EhQYDSSIA7YahkgEn2+ENQ X-IronPort-AV: E=Sophos;i="4.68,240,1312171200"; d="scan'208";a="131527540" Original-Received: from 75-119-225-217.dsl.teksavvy.com (HELO ceviche.home) ([75.119.225.217]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 17 Aug 2011 10:02:18 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 696E866329; Wed, 17 Aug 2011 10:02:16 -0400 (EDT) In-Reply-To: <831uwkttig.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 17 Aug 2011 09:57:27 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.183 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:143368 Archived-At: >> > I don't actually have a good understanding of why would a mode want to >> > behave like that. The above explanation is purely phenomenological, >> > so if I would need to determine whether my mode needs it, I'd be >> > probably stumped. I don't really see the connection between >> > "specially-prepared" and "don't use me as the default mode". >> > Can you explain the considerations for when to use this feature? I >> > will then clarify this in the manual. >> Indeed, I'm just as lost as you are :-( >> For that reason, I'd be happy to get rid of this "use as the default >> mode" thingy. I.e. we should simply never inherit the major mode of new >> buffers from the current buffer (if the global value of major-mode is >> nil, then the default major-mode when creating a new buffer will be >> fundamental-mode, and that's it). > Are we sure the nil-means-use-current-buffer-major-mode feature is not > used too much to get rid of it? I think it's very rarely used by Elisp code. It might be used by a few rare users as well. > And if we do that, how would a Lisp program specify that the major > mode of the current buffer is to be used for a newly created buffer? By calling that major mode in the new buffer? Stefan