Gnus development mailing list
 help / color / mirror / Atom feed
From: "守岡 知彦 / MORIOKA Tomohiko" <morioka@jaist.ac.jp>
Subject: [gnus 5.2.7] custom.el
Date: Wed, 05 Jun 1996 17:37:14 JST	[thread overview]
Message-ID: <199606050837.RAA26913@mikan.jaist.ac.jp> (raw)

[-- Attachment #1: Type: text/plain, Size: 239 bytes --]

  Default setting of dgnushack.el occurs errors because variable
`custom-file' indicates "/dev/null".

  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?


[-- Attachment #2: custom.el.diff --]
[-- Type: application/octet-stream, Size: 592 bytes --]

*** custom.el~	Wed Jun  5 03:10:19 1996
--- custom.el	Wed Jun  5 17:24:29 1996
***************
*** 2461,2467 ****
  		     (not (string-match "XEmacs" emacs-version)))
  (custom-category-put 'custom-hidden-properties intangible t)
  
! (if (file-readable-p custom-file)
      (load-file custom-file))
  
  (provide 'custom)
--- 2461,2468 ----
  		     (not (string-match "XEmacs" emacs-version)))
  (custom-category-put 'custom-hidden-properties intangible t)
  
! (if (and (file-readable-p custom-file)
! 	 (file-regular-p custom-file))
      (load-file custom-file))
  
  (provide 'custom)

[-- Attachment #3: Type: text/plain, Size: 335 bytes --]


  Thanks,
----------------------------------------------------------------------
MORIOKA Tomohiko <morioka@jaist.ac.jp>
        Japan advanced Institute of Science and Technology, Hokuriku
                Asahi-dai, Tatsu-no-kuchi chô, Nomi, Ishikawa, Japan
----------------------------------------- Frisch, Frei, Freöhlich! ---

             reply	other threads:[~1996-06-05  8:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-05  8:37 守岡 知彦 / MORIOKA Tomohiko [this message]
1996-06-05  9:17 ` Per Abrahamsen
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=199606050837.RAA26913@mikan.jaist.ac.jp \
    --to=morioka@jaist.ac.jp \
    /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).