GNU bug report logs -
#13179
24.2.90; fill-paragraph in Makefiles
Previous Next
Full log
Message #20 received at 13179-done <at> debbugs.gnu.org (full text, mbox):
> The expected behavior would be to keep looking like the first case with
> 4 space indentation.
Indeed.
> I have bisected the problem (with git) to this commit:
> Author: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Date: Wed Sep 8 18:21:23 2010 +0200
> Misc cleanups and simplifications.
The problem was kind of nasty (disappears when you step through the
code, because it gets fixed by font-lock), but even now that
I understand clearly what was the problem, I don't see how it is related
to the above changes (maybe by setting parse-sexp-lookup-properties).
In any case, I've installed the patch below which should fix the problem
(maybe it should be fixed more generally in fill.el or in
back-to-indentation).
Stefan
--- lisp/progmodes/make-mode.el 2013-01-01 09:11:05 +0000
+++ lisp/progmodes/make-mode.el 2013-01-30 20:38:09 +0000
@@ -1307,6 +1307,12 @@
(save-restriction
(narrow-to-region beginning end)
(makefile-backslash-region (point-min) (point-max) t)
+ ;; Backslashed newlines are marked as puncutations, so when
+ ;; fill-delete-newlines turns the LF into SPC, we end up with spaces
+ ;; which back-to-indentation (called via fill-newline ->
+ ;; fill-indent-to-left-margin -> indent-line-to) thinks are real code
+ ;; (bug#13179).
+ (remove-text-properties (point-min) (point-max) '(syntax-table))
(let ((fill-paragraph-function nil)
;; Adjust fill-column to allow space for the backslash.
(fill-column (- fill-column 1)))
This bug report was last modified 12 years and 117 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.