>>>> "Tobias" == Tobias Kunze Briseño
<t(a)fictive.com> writes:
Tobias> in lisp-mode, there is a problem with the syntactic highlighting
Tobias> ( <- single open paren at beginning of line
"That's not a bug, that's a feature." Throughout the syntactic
parsing code underlying fontlock, the assumption is made that an open
delimiter in column 1 indicates the start of a defun (ie, a top-level
construct). This was necessary to avoid recursive backtracking to the
beginning of the file, and is deeply embedded (ie, AFAIK it would be
quite painful to fix) in the the code.
Extremely unlikely that this can be fixed in 21.4, and getting it
fixed in 21.5 probably requires a volunteer with a pretty big chunk of
time/effort/expertise to contribute.
The workaround is to quote open delimiters that occur at the start of
a line. So in Emacs Lisp, you will often see
(defun foo ()
"A function that does nothing, and whose only purpose is to have a
\(typically parenthesized at the beginning of line) docstring."
nil)
(replace-string "\n(" "\n\\(") is the only workaround I can suggest.
Maybe somebody who knows the code better than I do can be more
optimistic, but that's my current assessment.
--
Institute of Policy and Planning Sciences
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.