From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: 5.6.9: nnml group beeps on entry
Date: 02 Jun 1998 12:24:24 +0200 [thread overview]
Message-ID: <kigpvgs85k7.fsf@jagor.srce.hr> (raw)
In-Reply-To: Steinar Bang's message of "02 Jun 1998 12:05:58 +0200"
Steinar Bang <sb@metis.no> writes:
> > Have a peek in the *Messages* buffer if you hear a beep.
[...]
> I now read mail and news in XEmacs 20.4 which I had to start using
> to get tm to work again (the alternative would have been to
> downgrade to 19.34), and XEmacs doesn't seem to have a *Messages*
> buffer.
Press `C-h l' instead. Much better than *Messages*.
If you really want a *Messages* replacement, switch to " *Message-Log*"
(note the space.)
--
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Don't hit a man when he's down -- kick him; it's easier.
next prev parent reply other threads:[~1998-06-02 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-28 10:42 Steinar Bang
1998-05-28 12:44 ` Lars Balker Rasmussen
1998-05-28 14:14 ` Steinar Bang
1998-05-29 9:11 ` Steinar Bang
1998-06-01 3:39 ` Lars Magne Ingebrigtsen
1998-06-02 10:05 ` Steinar Bang
1998-06-02 10:24 ` Hrvoje Niksic [this message]
1998-06-02 11:53 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=kigpvgs85k7.fsf@jagor.srce.hr \
--to=hniksic@srce.hr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).