Bug 139315 - allow-remote-paths errors in default install xemacs 21.5.21
Summary: allow-remote-paths errors in default install xemacs 21.5.21
Status: RESOLVED DUPLICATE of bug 130200
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X11 Applications (show other bugs)
Version: Final
Hardware: x86-64 Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Mike Fabian
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-15 08:14 UTC by Samuel Isaacson
Modified: 2005-12-16 20:33 UTC (History)
1 user (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Isaacson 2005-12-15 08:14:58 UTC 
I have been encountering numerous allow-remote-paths errors in the current xemacs YaST package (21.5.21). 

For example, with no custom xemacs initialization files, when using:
Tools->Packages->List and Install
I receive the error:
Symbol's value as variable is void: allow-remote-paths

All the other "Tools->Packages" commands give similar errors.

I also get this error when trying to load the template package from
emacs-template.sourceforge.net
I have in the past used this exact package/version on a number of other xemacs installs without error. (I also receive an error when byte compiling this package under SUSE xemacs which I have never received on any other distribution/xemacs install).
Comment 1 Michael Gross 2005-12-15 12:56:43 UTC 
The maintainer should decide about the support here.
Comment 2 Mike Fabian 2005-12-16 20:16:40 UTC 
OK, I can still reprodude the problem with XEmacs 21.5.22 and
xemacs-packages-20051208 on the latest development version of SuSE
Linux.
Comment 3 Mike Fabian 2005-12-16 20:25:06 UTC 
The easiest way for me to reproduce this is

   C-x C-f /foo@bar:/tmp RET
Comment 4 Mike Fabian 2005-12-16 20:32:35 UTC 
The variable allow-remote-paths is defined in /usr/share/xemacs/xemacs-packages/lisp/efs/efs-fnh.el like this:

;;;###autoload
(defvar allow-remote-paths t
   "*Set this to nil if you don't want remote paths to access
remote files.")

I.e. it has an autoload cookie. Nevertheless it is not generated
into /usr/share/xemacs/xemacs-packages/lisp/efs/auto-autoloads.el.

This causes the problem.
Comment 5 Mike Fabian 2005-12-16 20:33:38 UTC 

*** This bug has been marked as a duplicate of 130200 ***