Re: [Emacs-diffs] comment-cache 223d16f 2/3: Apply `comment-depth' text properties when calling `back_comment'.

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > My changes might speed up back_comment, but that's not the prime reason
  > for them.  Rather, I want utterly to expunge all the nonsense about
  > parens in column 0.

You might think of this rule as a kludgy rough approximation finding
the defuns in the file.  But it is also a useful way of controlling
what count as defuns.  For instance,

(eval-when-compile
(defun foo ...)

(defun bar...)
)

treats foo and bar as defuns, whereas

(eval-when-compile
  (defun foo ...)

  (defun bar...)
)

treats the whole thing as one defun.

I always want the former.

Without the open-paren-in-column-0 feature, the whole
eval-when-compile form would have to count as one defun, and the user
would have no choice about that.

Thus, before you talk about "fixing" this, would you please
state what behavior you want to implement?

If it makes the right thing happen automatically in some cases
and doesn't make the wrong thing start to happen in other cases,
it could be an improvement.  But let's see it and verify that.


-- 
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.