YAMAMOTO Mitsuharu skrev:
On Fri, 01 Jun 2007 18:42:57 -0400, Chong Yidong [EMAIL PROTECTED]
said:
I looked at the GTK+ sources. Apparently, if we don't set
WM_ICON_NAME ourselves, gtk_window_set_icon_name sets WM_ICON_NAME
for us. So I think we are perfectly safe.
No, I don't think
mode: font-lock
font-lock-defaults: ((^\\S-.*:$))
I must say that I don't know why this has changed.
Does the patch below fix your problem?
No, nothing changed. If I use font-lock-keywords I get the message:
Toggling font-lock-mode off; better pass an explicit argument.
That looks correct:
So I propose undoing the latest change for x_set_name_internal for
now.
If my change broke something, then please undo it; but in that case,
please put in whatever GCPROs are needed for x_encode_text.
___
emacs-pretest-bug mailing list
Richard Stallman [EMAIL PROTECTED] writes:
So I propose undoing the latest change for x_set_name_internal for
now.
If my change broke something, then please undo it; but in that case,
please put in whatever GCPROs are needed for x_encode_text.
The GCPRO you added in x_encode_text
This is the definition of `add-to-invisibility-spec':
(defun add-to-invisibility-spec (element)
...
(if (eq buffer-invisibility-spec t)
(setq buffer-invisibility-spec (list t)))
(setq buffer-invisibility-spec
(cons element buffer-invisibility-spec)))
This is what it should
