Evgeny,
Thanks for your response. Your guess is correct--I didn't byte
compile the efs.el file after making the change, and is no doubt the
reason I didn't see the change. Thanks for the pointer to the "load"
function--I will look it up.
Chris
Chris> When I initially couldn't get customize-variable to
work, I
Chris> also grepped the efs files to find the variables in the
Chris> source code. I tried replacing "ftp" with
"usr/bin/ftp" in
Chris> the line:
Chris> (defcustom efs-ftp-program-name "ftp"
Chris> in the
Chris> /usr/local/lib/xemacs/xemacs-packages/lisp/efs/efs.el file,
Chris> then restarted emacs. However, when I tried to ftp after
Chris> restarting Xemacs, it seemed that my change hadn't had any
Chris> effect--Xemacs was still using the Kerberos ftp client:
[...]
Chris> Why didn't my change have an effect?
Probably because XEmacs was finding the (old) byte-compiled version of
the efs library in the file efs.elc and loading that instead of
efs.el. You don't mention that you have byte-compiled efs.el after
making your edits (i.e., something like "xemacs -vanilla -batch -f
batch-byte-compile efs.el" from the shell command line). Other than
that, I am not sure.
(X)Emacs will load the byte-compiled version of the file (.elc), if
the byte-compiled file exists, in preference of the source (.el). The
description of the "load" function in the "Loading->How Programs do
Loading" section of the XEmacs Lisp technical reference has the
details.
--
Evgeny
Advanced design: Upper management doesn't understand it.