Sam Steingold <sds(a)goems.com> writes:
> >> > 2. When a key is undefined or bound to an undefined function, nothing
> >> > happens. Emacs beeps, can I make XEmacs beep too?
> >> Doesn't `xemacs -vanilla' beeps ? It beeps for me in all cases (X,
> >> xterm, console ...).
> Yes, -vanilla does beep - so, what could have turned the beep off?
Well, you should examine your .emacs for suspicious things. Or, if
you really have no idea what's doing it, you can even take a
binary-search-like approach and comment out halves of your .emacs
seeing if the problem repeats.
> >> I don't understand what you are considering a bug.
> 1. getting two identical buffers
They are identical because all of the warnings you get are being shown.
*Warnings* buffer is an internal buffer with all the warnings. If you
set `display-warning-minimum-level' to something like `emergency', the
-show buffer will disappear, and the *Warnings* buffer will continue
existing in the background.
> 2. getting spurious warnings: my setup allows an emacs (that's
> generic, both Emacs and XEmacs)
We use `Emacs' as a generic name for both.
> to distinguish between bold, italic and bold-italic.
You have a point; it might be considered a bug.
> >> It's a feature. You can have several help buffers displayed at
> >> the same time with different informations in them. This doesn't
> >> really create many buffers since in XEmacs typing `q' in a Help
> >> buffer kills it by default instead of just burry it.
> sure - but why two parallel facilities?
Because there are people who still prefer doing things "the old way"
(not to mention that `M-x apropos' is faster than the hyper version),
and who would (rightfully) bitch and moan if we were to remove the old
facility. We've been bitten by such things in the past, and it's best
to have a conservative approach.
Anyway, good luck with XEmacs, and thanks for being persistent and
reporting the bugs.
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
The end of the world is coming... SAVE YOUR BUFFERS!