is anybody else experiencing the same behaviour?
When I start a vanilla xemacs 21.2 (latest CVS sources), mule or
no-mule makes no difference, I get an error message
Wrong type argument: number-char-or-marker-p, nil
Now, I type, let's say, f RET in the *scratch* buffer and move the
cursor up, and off we go, right to Nirvana.
Sorry, I haven't got the backtrace and stacktrace at hand (different
file systems ...), but I can send them later, if necessary.
Funny thing is, I only see this behaviour on FBSD, not on my Linux box
which I am using now.
The crucial change must have happened between last Saturday and last
Any clues? TIA, norbert.