Katsumi Yamaoka [EMAIL PROTECTED] writes:
Gnus uses describe-key-briefly non-interactively and causes an
error as follows:
Debugger entered--Lisp error: (wrong-type-argument arrayp nil)
aref(nil -1)
(stringp (aref untranslated (1- ...)))
(if (stringp (aref untranslated ...)) (aset
The command for the target update-authors in lisp/Makefile.in fails
because batch-update-authors isn't autoloaded. What about the
following fix?
Lute.
Index: lisp/Makefile.in
===
RCS file: /cvsroot/emacs/emacs/lisp/Makefile.in,v
In [EMAIL PROTECTED]
Lute Kamstra [EMAIL PROTECTED] wrote:
Does this patch fix it?
Thanks. It does the trick.
! (if (and ( (length untranslated) 0)
! (stringp (aref untranslated (1- (length untranslated)
BTW, is there a reason it is necessary to check the length
Katsumi Yamaoka [EMAIL PROTECTED] writes:
In [EMAIL PROTECTED]
Lute Kamstra [EMAIL PROTECTED] wrote:
Does this patch fix it?
Thanks. It does the trick.
!(if (and ( (length untranslated) 0)
! (stringp (aref untranslated (1- (length untranslated)
BTW, is there a
With GNU Emacs 22.0.50.1 (i386-mingw-windows98.3000) of 2005-04-11.
There are string/nil mismatches in the standard customization settings
of `jka-compr-compression-info-list'.
___
Emacs-pretest-bug mailing list
Emacs-pretest-bug@gnu.org
Silently using the absolute file name is a very error-prone behavior.
It is also very useful, and used frequently. I don't think I can
change this in read-file-name.
There was a bug report recently about `copy-file' and other similar
command assuming a wrong filename. This was
Luc Teirlinck [EMAIL PROTECTED] writes:
It worked for me, except that, of course, the strangeness when you try
to edit the keyboard macro with `C-x C-k e' is still there.
The strangeness I observed was that I typed C-x C-k and nothing
happened. Without reading half a megabyte of NEWS, it's
[EMAIL PROTECTED] (Kim F. Storm) writes:
Has this problem been solved with the fix I installed?
I assume so, but the diagnosis seems to be wrong, which may be
relevant if you think C-s has introduced a bug.
___
Emacs-pretest-bug mailing list
Lute Kamstra [EMAIL PROTECTED] writes:
I've got a sneaky suspicion that something goes awry with the
interaction between font-locking and the code in
grep-mode-font-lock-keywords that removes the escape sequences.
Unless it's something to do with undefined behaviour leaking from the
C level,
Kenichi Handa [EMAIL PROTECTED] writes:
Unicode doesn't say which syntax a character should have in
Emacs.
I know it doesn't in detail -- the Emacs syntax codes don't actually
map directly to the Unicode properties. Categories can do that if
appropriate.
Even if we give guillemets generic
I obviously don't understand it too well if I messed it up in the
first place. Can't you just revert the change?
OK I've done this now. Please supply a better doc string if you want one.
Nick
___
Emacs-pretest-bug mailing list
11 matches
Mail list logo
