From: Kai T. <kai...@we...> - 2011-11-25 08:29:35
|
Hello Alan, > Yes. Sorry I didn't answer you at the time. No worries. >> I have tried to narrow down the source of the problem and found that the >> following patch against cc-mode CVS fixes it (it might have some >> unwanted side-effects, but i'm using this patch since quite a while >> without problems): > > Wow! Thanks for this tip. This patch more or less just reverts this part of cc-mode back to the state it was in before the problem started. No rocket science involved :-). >> diff -r c8c4f1bd6913 lisp/cc-mode/cc-cmds.el >> --- a/lisp/cc-mode/cc-cmds.el Tue Aug 23 08:22:34 2011 +0200 >> +++ b/lisp/cc-mode/cc-cmds.el Tue Aug 23 08:20:42 2011 +0200 >> @@ -4373,11 +4373,8 @@ >> (let ((fill-paragraph-function >> ;; Avoid infinite recursion. >> (if (not (eq fill-paragraph-function 'c-fill-paragraph)) >> - fill-paragraph-function)) >> - (start-point (point-marker))) >> - (c-mask-paragraph >> - t nil (lambda () (fill-region-as-paragraph (point-min) (point-max) arg))) >> - (goto-char start-point)) >> + fill-paragraph-function))) >> + (c-mask-paragraph t nil 'fill-paragraph arg)) >> ;; Always return t. This has the effect that if filling isn't done >> ;; above, it isn't done at all, and it's therefore effectively >> ;; disabled in normal code. > > I'll look into this. It may take me quite a few days. Thanks, that would be great! There's no hurry. BR, Kai |