From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: [gnus 5.2.7] custom.el
Date: 05 Jun 1996 11:17:54 +0200 [thread overview]
Message-ID: <rjennuwqwt.fsf@kleene.dina.kvl.dk> (raw)
In-Reply-To: =?ISO-2022-JP?B?GyRCPGkyLBsoQiAbJEJDTkknGyhC?= / MORIOKA Tomohiko's message of Wed, 05 Jun 1996 17:37:14 JST
>>>>> MORIOKA Tomohiko writes:
> In my environment, /dev/null is readable so check code of custom.el
> does not work. So I write following code. Do you think about it?
"/dev/null" is supposed to be readable, but empty. Loading an empty
file is a no-op on Emacs. Is it different with MULE?
If "/dev/null" causes problems, just use a bogus file name, like
"/DOES NOT EXIST!".
next prev parent reply other threads:[~1996-06-05 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-05 8:37 守岡 知彦 / MORIOKA Tomohiko
1996-06-05 9:17 ` Per Abrahamsen [this message]
1996-06-05 10:23 ` 守岡 知彦 / MORIOKA Tomohiko
1996-06-05 10:52 ` Lars Magne Ingebrigtsen
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=rjennuwqwt.fsf@kleene.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).