unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lektu@terra.es>
Subject: Checking for nnheader-file-name-translation-alist on gnus-ems.el
Date: Fri, 14 Jun 2002 12:54:02 +0200	[thread overview]
Message-ID: <20020614124350.C03B.LEKTU@terra.es> (raw)

It is OK to install this patch?

The motivation is that in some systems (windows and os/2, basically),
the eval-and-compile block tries to append to a variable that is not yet
defined. That causes an error, so gnus-ems.el is not compiled on those
systems (the same happens in the EMACS_21_1_RC branch, BTW).

I thought of require'ing nnheader.el, but it seems overkill for just a
variable. Also, I didn't use bound-and-true-p because gnus-ems.el should
work in several Emacs and XEmacs releases.



                                                           /L/e/k/t/u





2002-06-14  Juanma Barranquero  <lektu@terra.es>

	* gnus-ems.el: Check that `nnheader-file-name-translation-alist'
	is bound before getting its value.


Index: gnus-ems.el
===================================================================
RCS file: /cvs/emacs/lisp/gnus/gnus-ems.el,v
retrieving revision 1.15
diff -u -3 -r1.15 gnus-ems.el
--- gnus-ems.el	12 Apr 2002 08:46:59 -0000	1.15
+++ gnus-ems.el	14 Jun 2002 10:47:06 -0000
@@ -82,7 +82,8 @@
      ((string-match "windows-nt\\|os/2\\|emx\\|cygwin32"
 		    (symbol-name system-type))
       (setq nnheader-file-name-translation-alist
-	    (append nnheader-file-name-translation-alist
+	    (append (and (boundp 'nnheader-file-name-translation-alist)
+                         nnheader-file-name-translation-alist)
 		    (mapcar (lambda (c) (cons c ?_))
 			    '(?: ?* ?\" ?< ?> ??))
 		    '((?+ . ?-))))))))

             reply	other threads:[~2002-06-14 10:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14 10:54 Juanma Barranquero [this message]
2002-06-14 13:32 ` Checking for nnheader-file-name-translation-alist on gnus-ems.el Simon Josefsson
2002-06-14 15:51   ` Juanma Barranquero

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=20020614124350.C03B.LEKTU@terra.es \
    --to=lektu@terra.es \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).