Thanks for the tip!
Kevin == Kevin Rodgers [EMAIL PROTECTED] writes:
Kevin Stefan Monnier wrote:
1) In using reflection, it ends up loading tpu-extras.el
(even though I have no intention of using tpu)
This is a problem in Emacspeak: it should not itself load
raman [EMAIL PROTECTED] writes:
I observe that file-remote-p gets called *lots* of times while
doing things like expand-file-name --- though it doesn't appear
to have a performance hit on today's machines, it still feels
excessive --- at least when watching things in the debugger to
see
But here is the problem though:
How do I find out after having called (functionp sym)
and getting back T if the function is already loaded? I was using
symbol-function as a guard to make sure I only called
(interactive-form on true functions
Kevin == Kevin Rodgers [EMAIL PROTECTED] writes:
Tom Tromey wrote:
2. Visit a patch file; make sure it is in diff-mode
3. C-h b
4. Move your mouse around the *Help* buffer.
Note that diff-unified-context and diff-context-unified
do not highlight -- you cannot click on these to go to the
appropriate help text.
Thanks; I think I
I think I finally got this right (I hope) someone please confirm
--
(I check (functionp (indirect-function sym))
before I do anything like calling interactive-form --
incidentally calling interactive-form was also automatically
loading files.
While debugging this, I also noticed that there is a
On several manpages (one of them is attached) WoMan complains:
Invalid search bound (wrong side of point) and leaves point at the end
of the buffer and the buffer status modified and writable. The
backtrace looks as following:
Debugger entered--Lisp error: (error Invalid search bound (wrong
On several manpages (one of them is attached) WoMan complains:
Invalid search bound (wrong side of point) and leaves point at the end
of the buffer and the buffer status modified and writable. The
backtrace looks as following:
Debugger entered--Lisp error: (error Invalid search bound (wrong
Stefan Monnier [EMAIL PROTECTED] writes:
Can you confirm that the patch below fixes the problem for you?
I've installed it in the 22 branch,
Tested with three manpages that used to trigger the error, all work
fine now.
Thank you. :-)
___
