From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: newline-and-indent vs. electric-indent-mode Date: Mon, 25 Jan 2021 21:43:20 -0500 Message-ID: References: <87wnw5yt58.fsf@hajtower> <01d07f6d-cc4c-2f54-4bae-a611bba7be93@yandex.ru> <66b7932d-4cee-9628-fae0-168ee6ebc041@yandex.ru> <801ef866-4212-5b74-350e-9942953174fe@yandex.ru> <452e56da-a92e-bb19-54d9-faabff2b7c2d@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38456"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Madhu , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 26 03:44:19 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l4EL5-0009vd-OF for ged-emacs-devel@m.gmane-mx.org; Tue, 26 Jan 2021 03:44:19 +0100 Original-Received: from localhost ([::1]:56806 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l4EL4-0004q6-R8 for ged-emacs-devel@m.gmane-mx.org; Mon, 25 Jan 2021 21:44:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47770) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l4EKE-0004Px-LP for emacs-devel@gnu.org; Mon, 25 Jan 2021 21:43:26 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:30290) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l4EKC-0006yj-TC for emacs-devel@gnu.org; Mon, 25 Jan 2021 21:43:26 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id D36E780C96; Mon, 25 Jan 2021 21:43:23 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id DD62480838; Mon, 25 Jan 2021 21:43:21 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1611629001; bh=4Ok6HVlIZgUZ7mWDk2WRqGDWM1vAn21vE3vPVk+8wjc=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=R5UObVepn51GUr/GlmV0mgHFWYEmcgFr7/kdCr1m6r+vBfL03iI29cq5xwyAKimul WqA8aaROvmrpJ7DeYef2TTiem8U7zXW1hJ5CyNVQW76XHLqWNxocx9TpqIC95sJrvL TN5hCUWteioADDvrtm+7MmrzHXP5cd34ZVXOwSJshtsF7sFhtC+aPTYonqnbwnfPfW koOYVduXVRJLIdJHDCbQ1xsJzu/tO1zP0WNOyXbMxdVuA9yF2useW+29bmnYFPPgVB tQJT+nLed85SP7sksBEQHHYjCH7KiAqE381VRjlly4OKNOL0u4Q1J5mjF0ZUzHqnaF buZmg7PdxsJKg== Original-Received: from alfajor (69-196-141-46.dsl.teksavvy.com [69.196.141.46]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 6DD59120155; Mon, 25 Jan 2021 21:43:21 -0500 (EST) In-Reply-To: <452e56da-a92e-bb19-54d9-faabff2b7c2d@yandex.ru> (Dmitry Gutov's message of "Tue, 26 Jan 2021 04:04:32 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:263433 Archived-At: > Indeed, there are a lot of hooks involved, but it seemed to work last > time I tried it. Yes, that's good enough for an optional feature, but I'd like something that has a fighting chance of being enabled by default >>> whitespace-cleanup-mode is working out just fine for me, though, because by >>> default is only cleans files that were clean previously. >> I'd like a feature that is also active in non-clean files. > > I just clean such a file manually once, and then the feature is active. Or > I don't, and use whitespace-mode to make sure I don't leave new trailing > whitespace around. > > Files like that are a minority in my experience, so it's not too big a price > to pay for being able to rely on a simple implementation. YMMV, of course. I agree for my own use. But that's not what I'm after ;-) Stefan