From: Christian Gudrian <Christian.Gudrian@gmx.de>
Subject: Re: font-locking mysteries
Date: Mon, 28 Jun 2004 13:39:55 +0200 [thread overview]
Message-ID: <2kaeccF19ig3vU1@uni-berlin.de> (raw)
In-Reply-To: <x5vfhcdv9r.fsf@lola.goethe.zz>
David Kastrup wrote:
> Ugh, what?!?
Well, if I say M-x mail I get an error message saying
`Opening output file: no such file or directory,
/home/Gudrian/#*mail*#1660Va0#'
Asterisks are no good in file names that are meant to be stored on file
systems by Microsoft... Which makes me wonder whether that would work
on *nix systems. Anyway I never got an error message like that on
FreeBSD, and given the fact that CVS Emacs doesn't compile on Cygwin at
the moment it might just be the combination of Cygwin and Emacs which
causes this behaviour. Never bothered me though, since I do not use
Emacs for mailing.
> You should report that, whatever it is, as a bug.
Let me guess:
M-x report-emacs-bug
which in turn will try to open a mail buffer, right? :)
> If you have a gnus session active and mail-user-agent set to
> gnus-user-agent, then the buffer file name might be different when
> calling mail.
No, I'm sorry. Don't bother. I might dive into that some time later.
But it's not worth it at the moment. After all it's just a minor
font-locking problem I was originally dealing with.
Is there a function which formats the mail buffer name? Perhaps I can
alter it in a way that will make reporting bugs work.
Christian
next prev parent reply other threads:[~2004-06-28 11:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 13:42 font-locking mysteries Christian Gudrian
2004-06-27 9:20 ` David Kastrup
2004-06-27 17:14 ` Christian Gudrian
2004-06-27 17:21 ` Christian Gudrian
2004-06-28 6:57 ` David Kastrup
2004-06-28 11:39 ` Christian Gudrian [this message]
2004-06-28 11:50 ` Maurizio Loreti
2004-06-28 12:18 ` Christian Gudrian
2004-06-28 11:52 ` David Kastrup
2004-06-28 12:11 ` Christian Gudrian
2004-06-28 12:18 ` David Kastrup
2004-06-28 12:42 ` Christian Gudrian
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2kaeccF19ig3vU1@uni-berlin.de \
--to=christian.gudrian@gmx.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).