"Richard M. Stallman" <[EMAIL PROTECTED]> writes:
> Does this make it work?
Yes, it now correctly signals that the buffer is read-only even when
kill-read-only-ok is set to t. Which is the right fix, I guess...
--
Romain Francoise <[EMAIL PROTECTED]> | All of the planet's dead, so
it's a mirac
Does this make it work?
*** whitespace.el 10 Jun 2005 09:28:20 -0400 1.36
--- whitespace.el 04 Jul 2005 09:37:22 -0400
***
*** 608,624
(defun whitespace-buffer-leading-cleanup ()
"Remove any empty lines at the top of the file."
(save-excursion
!
Whoops, sorry, control characters in my previous message truncated the
backtrace. Here's the full version:
Debugger entered--Lisp error: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
x-set-cut-buffer("\n" t)
x-select-text("\n" t)
kill-new("\n")
copy-region-as-kill(3 4)
byte-code
