Lute Kamstra [EMAIL PROTECTED] writes:
[...]
On second thought: it's probably better to solve the problem by using
define-minor-mode to implement flyspell-mode. Does anyone see any
problems with the patch below?
Committed. You may have to delete lisp/loaddefs.el to make
bootstrapping work
On second thought: it's probably better to solve the problem by using
define-minor-mode to implement flyspell-mode. Does anyone see any
problems with the patch below?
It looks good to me.
___
Emacs-pretest-bug mailing list
Symptoms:
I suspect the face name modeline-higilight is a typo for
modeline-highlight. Patch below.
Index: lisp/faces.el
===
RCS file: /cvsroot/emacs/emacs/lisp/faces.el,v
retrieving revision 1.313
diff -c -r1.313 faces.el
***
Frederik Fouvry [EMAIL PROTECTED] writes:
Symptoms:
I suspect the face name modeline-higilight is a typo for
modeline-highlight. Patch below.
Since both mode-line-inactive and mode-line-highlight are
new faces in 22.x, do we really need to have face aliases
for them?
--
Kim F. Storm
And, yes, I think the default value for
`display-buffer-reuse-frames' should
be `t'. People upgrading from versions of Emacs that don't have this
variable will expect more or less unchanged behavior
without having to explicitly set this variable to `t'.
The following line has been put in my .emacs:
(setq x-select-request-type '(UTF8_STRING COMPOUND_TEXT TEXT STRING)
When I select some text from Mozilla-firefox using left mouse
button, but without issuing cut/copy command explicitly, then I paste
in emacs with middle mouse button or C-y,
Since it doesn't seem to be going away (despite this thread where
nobody liked it:
http://lists.gnu.org/archive/html/emacs-devel/2005-05/msg00758.html;
and several poeple asked for the changes to be reverted), here is a
list of problems with the latest makefile-mode.
Font-lock bugs:
1. In
If I do (setq special-display-regexps '([ ]?[*][^*]+[*])),
then when I hit
`d' in the debugger, the debugger frame iconifies.
Doesn't it de-iconify right after (thus flashing)? That's very odd.
No; it does not deiconify.
If it did, I would consider that too to be a bug - why
If I do (setq special-display-regexps '([ ]?[*][^*]+[*])), then when I hit
`d' in the debugger, the debugger frame iconifies.
Doesn't it de-iconify right after (thus flashing)? That's very odd.
No; it does not deiconify.
Oh, I think I know what it is: that's because of Richard's new
Title: PayPal update
Dear
PayPal member,
Due to recent activity, including possible
With parse-sexp-ignore-comments t and point in between ( in
(setq foo (;))
forward-sexp gets me
forward-sexp: Scan error: Unbalanced parentheses.
Obviously, this is because scan-lists finds the semicolon and does not
check whether it's inside a string. Could someone please add the
No; it does not deiconify.
Oh, I think I know what it is: that's because of Richard's new
code which
uses just `select-window' instead of `pop-to-buffer' and thus fails to
de-iconify.
Good. Sounds like progress.
If it did, I would consider that too to be a bug - why
Richard Stallman wrote:
Indeed, the value of that argument seems to be unused.
So I guess it is a relic of something.
If you look at the change logs, you could probably tell what happened.
The only mention in the changelogs is from 1990:
1990-03-08 Joseph Arceneaux ([EMAIL
When the cursor type is `bar', putting the cursor over an image has
no visual indication. This can be considered a bug when moving the
cursor in the Face Customization buffer over rows of face attributes
vertically on the column with checkbox images has no visual feedback
on cursor motion at all.
I'm saying that in the case of `q' or `c', I don't want the keep
displaying the frame, instead I want it iconified.
In the case of `c', I definitely want to keep displaying the debugger. Why
would you want it to disappear? Using `c' doesn't mean you're done with the
debugger. I can
Richard Stallman wrote:
Indeed, the value of that argument seems to be unused.
So I guess it is a relic of something.
If you look at the change logs, you could probably tell what happened.
It appears that at one time in the past, the argument _was_ used. I
believe that one could pass
Symptoms:
I've heard tell that vim will give a warning in the form lf changing
the buffer color when a namespace is opened, but not closed in C++
mode. I've been stung a couple of times by missing the closing '}' at
the end of a file in which a namespace is opened. It is one of the
least
17 matches
Mail list logo
