Typing `C-s M-%' or `C-s C-M-%' gives the error:
isearch-query-replace: Wrong type argument: number-or-marker-p, nil
Here's a patch:
Thanks. Installed.
--
Juri Linkov
http://www.jurta.org/emacs/
___
emacs-pretest-bug mailing list
There are some quoted lambda expressions in the manuals:
find . -type f -print0 | xargs -0 -e grep -nH -e '(lambda
./custom.texi:905: '(lambda ()
./custom.texi:1392: '(lambda ()
./custom.texi:: '(lambda () (auto-fill-mode 1)))
./emacs-xtra.texi:215: #'(lambda (optional
I have a local fix that displays Hi in the mode line only when the
list of regexps to highlight is not empty in the current buffer.
This means it is displayed only when hi-lock has something to highlight.
Do you think it would be useful to use this logic by default in
hi-lock.el?
As a user,
hi-lock-mode breaks existing highlighting when its regexps cover
areas highlighted by standard font-lock keywords (non-syntactic).
This is especially undesirable on large highlighted areas like
outline headings etc.
A good solution for this problem is to append new hi-lock keywords
at the end of
After this change:
2005-12-12 Stefan Monnier [EMAIL PROTECTED]
* descr-text.el (describe-char): Rework last fix to solve the problem
is the same way it's solved for everything else in that function
(i.e. by extracting the info before setting up the *Help* buffer).
the
This bug report will be sent to the Free Software Foundation, not
to your local site managers! Please write in English if possible,
because the Emacs maintainers usually do not have translators to
read other languages for them. Your bug report will be posted to
the emacs-pretest-bug@gnu.org
Symptoms:
An error is signalled when I use smerge-mode to select one of the
alternatives of a CVS conflict. A stack trace looks like this:
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-
p nil)
delete-region(nil 20191)
smerge-keep-n(3)
smerge-keep-current()
Juri Linkov [EMAIL PROTECTED] writes:
hi-lock-mode breaks existing highlighting when its regexps cover
areas highlighted by standard font-lock keywords (non-syntactic).
This is especially undesirable on large highlighted areas like
outline headings etc.
...
A patch below...
Was this patch
Richard M. Stallman [EMAIL PROTECTED] writes:
I appreciate your work.
I'm afraid I couldn't have guessed so, and experimentally I couldn't
get fixes made, even being thick-skinned about the response.
If you send a useful and clear bug fix, we
will certainly use it.
I can't be any clearer
I haven't used the menu or tool bars to visit files before, but I just
tried it and visiting worked, but modifying the directory list under
Browse for other folders didn't work. I started emacs -q and
clicked on the file icon in the toolbar or the corresponding menu bar
entry. At first I was
I realize that apart from anything else, TODO gets treated as a list
of things to avoid. However, could you at least reference existing
work on the topics, even if it gets re-done, to avoid more wasted
hacker time? Here are items I know about, though I can't necessarily
remember what I did long
11 matches
Mail list logo