From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#13949: 24.4.1; `fill-paragraph' should not always put the buffer as modified Date: Sun, 27 Mar 2016 20:51:35 +0300 Message-ID: <83wponyfko.fsf@gnu.org> References: <56F12360.5030301@ro.ru> <83y49a4hga.fsf@gnu.org> <56F1837D.4060300@ro.ru> <83io0e4b5r.fsf@gnu.org> <56F19203.5040501@ro.ru> <87a8lkd2bc.fsf@wanadoo.es> <83lh54ynol.fsf@gnu.org> <87io08aqhr.fsf@wanadoo.es> <83bn5zzzd3.fsf@gnu.org> <8737rbc3e7.fsf@wanadoo.es> <837fgnzyr1.fsf@gnu.org> <87r3evand5.fsf@wanadoo.es> <8337rbzwy6.fsf@gnu.org> <87a8ljakw3.fsf@wanadoo.es> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1459101203 19186 80.91.229.3 (27 Mar 2016 17:53:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 27 Mar 2016 17:53:23 +0000 (UTC) Cc: 13949@debbugs.gnu.org To: =?UTF-8?Q?=C3=93scar?= Fuentes Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Mar 27 19:53:12 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1akEsC-0007yS-8E for geb-bug-gnu-emacs@m.gmane.org; Sun, 27 Mar 2016 19:53:12 +0200 Original-Received: from localhost ([::1]:36857 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1akEsB-0000IH-Em for geb-bug-gnu-emacs@m.gmane.org; Sun, 27 Mar 2016 13:53:11 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58481) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1akEs6-0000Hh-Tx for bug-gnu-emacs@gnu.org; Sun, 27 Mar 2016 13:53:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1akEs2-00032o-4l for bug-gnu-emacs@gnu.org; Sun, 27 Mar 2016 13:53:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43264) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1akEs2-00032a-0z for bug-gnu-emacs@gnu.org; Sun, 27 Mar 2016 13:53:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1akEs1-0000lu-Pl for bug-gnu-emacs@gnu.org; Sun, 27 Mar 2016 13:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 27 Mar 2016 17:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 13949 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 13949-submit@debbugs.gnu.org id=B13949.14591011282902 (code B ref 13949); Sun, 27 Mar 2016 17:53:01 +0000 Original-Received: (at 13949) by debbugs.gnu.org; 27 Mar 2016 17:52:08 +0000 Original-Received: from localhost ([127.0.0.1]:40391 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1akErA-0000kj-Bn for submit@debbugs.gnu.org; Sun, 27 Mar 2016 13:52:08 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:39174) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1akEr9-0000kY-C7 for 13949@debbugs.gnu.org; Sun, 27 Mar 2016 13:52:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1akEqz-0002fh-Vr for 13949@debbugs.gnu.org; Sun, 27 Mar 2016 13:52:01 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:58787) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1akEqz-0002fd-SS; Sun, 27 Mar 2016 13:51:57 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3435 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1akEqz-00080p-7u; Sun, 27 Mar 2016 13:51:57 -0400 In-reply-to: <87a8ljakw3.fsf@wanadoo.es> (message from =?UTF-8?Q?=C3=93scar?= Fuentes on Sun, 27 Mar 2016 19:30:36 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:115600 Archived-At: > From: Óscar Fuentes > Cc: 13949@debbugs.gnu.org > Date: Sun, 27 Mar 2016 19:30:36 +0200 > > It occurred to me at least two times to use M-q on comments on some C++ > header, see no changes, proceed with other edits elsewhere on the > project, and much later do `C-x s ! M-x compile' and see how the build > compiled files that shouldn't be affected by my edits, which, apart from > the waste of time on the extended build, caused more time to be wasted > on investigating the cause. Since I aware of the problem, if I use M-q > on a source file, I need to use `C-x s d' to see a diff and, if the diff > is empty, use undo to restore the modified flag. You are describing what I consider to be a minor annoyance. I agree it's an annoyance, and I agree it would be good to have an option to prevent that, I'm just saying the annoyance is minor. > >> And so far there is zero evidence that this change could cause > >> undesired effects. > > > > That's irrelevant. It would be irresponsible for us to change such > > basic aspects of Emacs operation at this point in Emacs history. We > > have been burnt with much less significant backward-incompatible > > changes. > > This is a recipe for changing *nothing* that is older than some > threshold, isn't it? No, only those aspects that are very basic, like text properties being an integral part of buffer text. > And we are talking about fill-paragraph here, not about some core > data structure. I wasn't talking about fill-paragraph, I was talking about deciding that changes in text properties aren't considered buffer modifications. > Apart from the fact that marking the buffer as modified when text > properties are changed is wrong in principle (otherwise, why don't > mark as modified the file-visiting buffers as soon as some text > properties are applied when the major/minor modes are enabled?) I think you are only considering face properties. But text properties can be something entirely different. I gave 2 examples before, here's another, perhaps more relevant one: the 'fill-space' and 'hard' properties that are directly involved in text filling.