6:59 p.m.
Dear Bug Team!
I have the elisp variable inhibit-site-lisp set to the default,
nil, yet site-lisp is not added to load-path. I unpacked
ESS into c:\XEmacs\Packages\site-lisp and
c:\XEmacs\Packages\site-lisp\ess\lisp was not added to
load-path which I'm pasting here:
("c:\\XEmacs\\Packages\\site-packages\\lisp\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\c-support\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\cc-mode\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\debug\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\dired\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\ecb\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\edebug\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\ediff\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\edit-utils\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\efs\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\eieio\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\fsf-compat\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\mail-lib\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\net-utils\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\os-utils\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\pc\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\perl-modes\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\prog-modes\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\semantic\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\sh-script\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\sounds-wav\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\speedbar\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\texinfo\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\text-modes\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\time\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\xemacs-base\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\xemacs-devel\\"
"c:\\XEmacs\\XEmacs-21.4.18\\lisp\\")
================================================================
System Info to help track down your bug:
---------------------------------------
OS version:
Microsoft Windows XP [Version 5.1.2600]
OS: Windows_NT
XEmacs 21.4.18 "Social Property" configured for `i586-pc-win32'.
Building XEmacs in
"E:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.4.18\\nt".
Using compiler "cl -nologo -W3 -O2 -G5 -MD".
Installing XEmacs in "c:\\XEmacs\\XEmacs-21.4.18".
Package path is
"~\\.xemacs;;c:\\XEmacs\\Packages\\site-packages;c:\\XEmacs\\Packages\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Compiling in fast dired implementation.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library
Load-Path Lisp Shadows:
----------------------
nil
Installed XEmacs Packages:
-------------------------
(xemacs-devel ver: 1.72 upstream: No-Upstream-Ver)
(xemacs-base ver: 2.0 upstream: No-Upstream-Ver)
(time ver: 1.14 upstream: 1.17)
(text-modes ver: 1.9 upstream: No-Upstream-Ver)
(texinfo ver: 1.3 upstream: No-Upstream-Ver)
(speedbar ver: 1.28 upstream: 0.14beta4)
(sounds-wav ver: 1.12 upstream: No-Upstream-Ver)
(sh-script ver: 1.21 upstream: 2.0f)
(semantic ver: 1.19 upstream: 1.4.2)
(prog-modes ver: 2.06 upstream: No-Upstream-Ver)
(perl-modes ver: 1.08 upstream: No-Upstream-Ver)
(pc ver: 1.28 upstream: No-Upstream-Ver)
(os-utils ver: 1.36 upstream: No-Upstream-Ver)
(net-utils ver: 1.48 upstream: N/A)
(mail-lib ver: 1.75 upstream: No-Upstream-Ver)
(fsf-compat ver: 1.15 upstream: No-Upstream-Ver)
(eieio ver: 1.05 upstream: 0.17)
(efs ver: 1.33 upstream: 1.23)
(edit-utils ver: 2.32 upstream: No-Upstream-Ver)
(ediff ver: 1.6 upstream: 2.75)
(edebug ver: 1.21 upstream: No-Upstream-Ver)
(ecb ver: 1.22 upstream: 2.31)
(dired ver: 1.17 upstream: 7.13)
(debug ver: 1.17 upstream: No-Upstream-Ver)
(cc-mode ver: 1.45 upstream: 5.30.10)
(c-support ver: 1.22 upstream: No-Upstream-Ver)
Features:
--------
(mail-abbrevs xemacsbug shadow sendmail rfc822 efs-cu shell comint
ring view-less view hyper-apropos cus-face xemacs-devel-autoloads
xemacs-base-autoloads time-autoloads text-modes-autoloads
texinfo-autoloads speedbar-autoloads sounds-wav-autoloads
sh-script-autoloads semantic-autoloads prog-modes-autoloads
perl-modes-autoloads pc-autoloads os-utils-autoloads
net-utils-autoloads mail-lib-autoloads fsf-compat-autoloads
eieio-autoloads efs-autoloads edit-utils-autoloads ediff-autoloads
edebug-autoloads ecb-autoloads dired-autoloads debug-autoloads
cc-mode-autoloads c-support-autoloads lisp-autoloads loadhist
auto-show fontl-hooks code-cmds gutter-items menubar-items x-menubar
dragdrop mode-motion mouse itimer auto-save lisp-mode easymenu
iso8859-1 page buff-menu lib-complete help-nomule cus-file derived
frame text-props obsolete cus-start custom widget cl-extra mini-cl cl
cl-19 packages backquote very-early-lisp file-coding
mswindows-scrollbars mswindows toolbar native-sound scrollbar
network-streams subprocesses menu-accelerator-support menubar md5
xemacs gutter png gif xpm xbm lisp-float-type windows-nt dragdrop-api
dialog devices window-system base64)
Recent keystrokes:
-----------------
l i s p SPC t ) misc-user misc-user misc-user button1
button1up f20 BS misc-user misc-user f1 v l o a d -
p a t h RET next button1 button1up C-x 1 x M-x x e
m a c s - r e p o r t - b u g RET BS BS BS BS BS BS
BS C-g f1 a r e p o r t BS BS BS BS BS BS b u g RET
button1 button1up M-x r e p o r t - x e m a c s - b
u g RET
Recent messages (most recent first):
-----------------------------------
Loading xemacsbug...done
Loading xemacsbug...
Quit
x not defined.
Wrote c:\Documents and Settings\rsparapa.HPI-MCW\.xemacs\init.el
Loading efs-cu...done
Loading efs-cu...
c:\XEmacs\XEmacs-21.4.18\i586-pc-win32\
Loading shell...done
Loading shell...
Quit
Search failed: "site-lisp"
Loading view-less...done
Loading view-less...
Loading cus-face...done
Loading cus-face...
2:41 p.m.
On 1/16/06, Rodney Sparapani <rsparapa(a)mcw.edu> wrote:
Dear Bug Team!
I have the elisp variable inhibit-site-lisp set to the default,
nil, yet site-lisp is not added to load-path. I unpacked
ESS into c:\XEmacs\Packages\site-lisp and
c:\XEmacs\Packages\site-lisp\ess\lisp was not added to
load-path which I'm pasting here:
("c:\\XEmacs\\Packages\\site-packages\\lisp\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\c-support\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\cc-mode\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\debug\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\dired\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\ecb\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\edebug\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\ediff\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\edit-utils\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\efs\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\eieio\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\fsf-compat\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\mail-lib\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\net-utils\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\os-utils\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\pc\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\perl-modes\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\prog-modes\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\semantic\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\sh-script\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\sounds-wav\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\speedbar\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\texinfo\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\text-modes\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\time\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\xemacs-base\\"
"c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\xemacs-devel\\"
"c:\\XEmacs\\XEmacs-21.4.18\\lisp\\")
================================================================
System Info to help track down your bug:
---------------------------------------
OS version:
Microsoft Windows XP [Version 5.1.2600]
OS: Windows_NT
XEmacs 21.4.18 "Social Property" configured for `i586-pc-win32'.
Building XEmacs in
"E:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.4.18\\nt".
Using compiler "cl -nologo -W3 -O2 -G5 -MD".
Installing XEmacs in "c:\\XEmacs\\XEmacs-21.4.18".
Package path is
"~\\.xemacs;;c:\\XEmacs\\Packages\\site-packages;c:\\XEmacs\\Packages\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in support for XPM images.
Compiling in support for GIF images.
Compiling in support for PNG images.
Compiling in support for TIFF images.
Compiling in support for JPEG images.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Compiling in fast dired implementation.
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library
Hi Rodney,
That is strange. I don't have an ess package to test, but I took an
fsf-compat tarball and unpacked it to e:\XEmacs\site-packages and here
is the value of load-path when I restarted XEmacs:
`load-path' is a simple built-in variable.
Value: ("e:/acs/lib/lisp/xemacs" "e:/acs/lib/lisp"
"e:\\XEmacs\\site-packages\\lisp\\"
"e:\\XEmacs\\site-packages\\lisp\\fsf-compat\\"
"e:\\XEmacs\\xemacs-packages\\lisp\\"
"e:\\XEmacs\\xemacs-packages\\lisp\\c-support\\".....
1. I'm wondering if your ess package conforms to the standard package
format; if you cd to c:/XEmacs/site-packages, what does 'ls -R' print?
2. Does the behavior change at all if you start XEmacs with the -vanilla option?
HTH,
Vin
9:48 p.m.
Vin Shelton <acs(a)xemacs.org> writes:
On 1/16/06, Rodney Sparapani <rsparapa(a)mcw.edu> wrote:
> Dear Bug Team!
>
> I have the elisp variable inhibit-site-lisp set to the default,
> nil, yet site-lisp is not added to load-path. I unpacked
Rodney, Vin, I don't think XEmacs has a notion of site-lisp.
It expects to find site-specific lisp code in
site-packages/lisp.
This is also what you both show in your load paths.
Rodney, try
mv c:\XEmacs\Packages\site-lisp\ess\lisp c:\XEmacs\Packages\site-package\lisp\ess
Adrian
> ESS into c:\XEmacs\Packages\site-lisp and
> c:\XEmacs\Packages\site-lisp\ess\lisp was not added to
> load-path which I'm pasting here:
> ("c:\\XEmacs\\Packages\\site-packages\\lisp\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\c-support\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\cc-mode\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\debug\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\dired\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\ecb\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\edebug\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\ediff\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\edit-utils\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\efs\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\eieio\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\fsf-compat\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\mail-lib\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\net-utils\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\os-utils\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\pc\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\perl-modes\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\prog-modes\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\semantic\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\sh-script\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\sounds-wav\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\speedbar\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\texinfo\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\text-modes\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\time\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\xemacs-base\\"
> "c:\\XEmacs\\Packages\\xemacs-packages\\lisp\\xemacs-devel\\"
> "c:\\XEmacs\\XEmacs-21.4.18\\lisp\\")
>
> ================================================================
>
> System Info to help track down your bug:
> ---------------------------------------
>
> OS version:
>
> Microsoft Windows XP [Version 5.1.2600]
> OS: Windows_NT
>
> XEmacs 21.4.18 "Social Property" configured for `i586-pc-win32'.
>
> Building XEmacs in
> "E:\\acs\\software\\XEmacsWindowsKit\\xemacs-21.4.18\\nt".
> Using compiler "cl -nologo -W3 -O2 -G5 -MD".
> Installing XEmacs in "c:\\XEmacs\\XEmacs-21.4.18".
> Package path is
>
"~\\.xemacs;;c:\\XEmacs\\Packages\\site-packages;c:\\XEmacs\\Packages\\xemacs-packages".
>
> Compiling in support for Microsoft Windows native GUI.
> Compiling in support for XPM images.
> Compiling in support for GIF images.
> Compiling in support for PNG images.
> Compiling in support for TIFF images.
> Compiling in support for JPEG images.
> Compiling in support for toolbars.
> Compiling in support for dialogs.
> Compiling in support for widgets.
> Compiling in support for native sounds.
> Compiling in fast dired implementation.
> Using portable dumper.
> Using system malloc.
> Using DLL version of C runtime library
>
Hi Rodney,
That is strange. I don't have an ess package to test, but I took an
fsf-compat tarball and unpacked it to e:\XEmacs\site-packages and here
is the value of load-path when I restarted XEmacs:
`load-path' is a simple built-in variable.
Value: ("e:/acs/lib/lisp/xemacs" "e:/acs/lib/lisp"
"e:\\XEmacs\\site-packages\\lisp\\"
"e:\\XEmacs\\site-packages\\lisp\\fsf-compat\\"
"e:\\XEmacs\\xemacs-packages\\lisp\\"
"e:\\XEmacs\\xemacs-packages\\lisp\\c-support\\".....
1. I'm wondering if your ess package conforms to the standard package
format; if you cd to c:/XEmacs/site-packages, what does 'ls -R' print?
2. Does the behavior change at all if you start XEmacs with the -vanilla option?
HTH,
Vin
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/
10:51 p.m.
On 1/17/06, Adrian Aichner <adrian(a)xemacs.org> wrote:
Vin Shelton <acs(a)xemacs.org> writes:
> On 1/16/06, Rodney Sparapani <rsparapa(a)mcw.edu> wrote:
>> Dear Bug Team!
>>
>> I have the elisp variable inhibit-site-lisp set to the default,
>> nil, yet site-lisp is not added to load-path. I unpacked
Rodney, Vin, I don't think XEmacs has a notion of site-lisp.
It expects to find site-specific lisp code in
site-packages/lisp.
This is also what you both show in your load paths.
Rodney, try
mv c:\XEmacs\Packages\site-lisp\ess\lisp c:\XEmacs\Packages\site-package\lisp\ess
D'oh! You're right, Adrian!
- vin
10:59 p.m.
Adrian Aichner wrote:
Vin Shelton <acs(a)xemacs.org> writes:
>On 1/16/06, Rodney Sparapani <rsparapa(a)mcw.edu> wrote:
>
>
>>Dear Bug Team!
>>
>>I have the elisp variable inhibit-site-lisp set to the default,
>>nil, yet site-lisp is not added to load-path. I unpacked
>>
>>
Rodney, Vin, I don't think XEmacs has a notion of site-lisp.
It expects to find site-specific lisp code in
site-packages/lisp.
This is also what you both show in your load paths.
Rodney, try
mv c:\XEmacs\Packages\site-lisp\ess\lisp c:\XEmacs\Packages\site-package\lisp\ess
Adrian
>>
>>
>Hi Rodney,
>
>That is strange. I don't have an ess package to test, but I took an
>fsf-compat tarball and unpacked it to e:\XEmacs\site-packages and here
>is the value of load-path when I restarted XEmacs:
>
>`load-path' is a simple built-in variable.
>
>Value: ("e:/acs/lib/lisp/xemacs" "e:/acs/lib/lisp"
>"e:\\XEmacs\\site-packages\\lisp\\"
>"e:\\XEmacs\\site-packages\\lisp\\fsf-compat\\"
>"e:\\XEmacs\\xemacs-packages\\lisp\\"
>"e:\\XEmacs\\xemacs-packages\\lisp\\c-support\\".....
>
>1. I'm wondering if your ess package conforms to the standard package
>format; if you cd to c:/XEmacs/site-packages, what does 'ls -R' print?
>2. Does the behavior change at all if you start XEmacs with the -vanilla option?
>
>HTH,
> Vin
>
>
>
>
>
Hi Guys:
Well, I unpacked ESS into site-lisp with 21.5 on OS X and it does find
it. I don't see why 21.4
on Windows should be different. And, if it was different, then what is
the purpose of the
variable inhibit-site-lisp? I think this is a bug. Oh, and I tried the
site-packages trick
and it didn't find it; only site-packages/lisp was there. But, now I
see why that wouldn't work.
You have the directory site-packages/lisp/fsf-compat. No non-xemacs
package has a directory
structure like that. A non-xemacs packages would have
site-packages/ess/lisp or some-such.
So we need to either fix site-lisp or make the search in site-packages
also find site-packages/*/lisp
Thanks,
Rodney
2:38 a.m.
Hi Rodney,
On 1/17/06, Rodney Sparapani <rsparapa(a)mcw.edu> wrote:
Well, I unpacked ESS into site-lisp with 21.5 on OS X and it does find
it. I don't see why 21.4
on Windows should be different. And, if it was different, then what is
the purpose of the
variable inhibit-site-lisp? I think this is a bug. Oh, and I tried the
site-packages trick
and it didn't find it; only site-packages/lisp was there. But, now I
see why that wouldn't work.
You have the directory site-packages/lisp/fsf-compat. No non-xemacs
package has a directory
structure like that. A non-xemacs packages would have
site-packages/ess/lisp or some-such.
So we need to either fix site-lisp or make the search in site-packages
also find site-packages/*/lisp
Here's the situation as I see it in the current 21.4 Windows native install kit.
site-lisp is supported but only to a directory depth of 1. Here's my test:
# I ran this under a cygwin shell even though my XEmacs is native
# XEmacs installed root is e:/XEmacs
cd /cygdrive/e/XEmacs
mkdir -p site-lisp/ess/lisp
cd /cygdrive/e/XEmacs/site-lisp
cat > foo1.el <<EOF
(message "foo1")
(sit-for 5)
EOF
cat >ess/lisp/foo2.el <<EOF
(message "foo2")
(sit-for 5)
EOF
xemacs -vanilla
(load-library "foo1") # this produced the expected "foo1" message
(load-library "foo2") # this produced the error: "Cannot open load file:
foo2"
Indeed, looking at the load-path reveals:
e:\\XEmacs\\site-lisp
e:\\XEmacs\\site-lisp\ess
but not site-lisp/ess/lisp
I believe the XEmacs startup code only searches site-lisp to 1 level
down for directories to add to load-path. According to my
experiments, this is the same behavior that XEmacs exhibits on Linux,
when configured --with-site-lisp.
I do not intend to change this behavior in the near-term, but as I
wrote, a patch could be considered.
Regards,
Vin
9:13 p.m.
Vin Shelton <acs <at> alumni.princeton.edu> writes:
I believe the XEmacs startup code only searches site-lisp to 1 level
down for directories to add to load-path. According to my
experiments, this is the same behavior that XEmacs exhibits on Linux,
when configured --with-site-lisp.
I do not intend to change this behavior in the near-term, but as I
wrote, a patch could be considered.
Regards,
Vin
Hi Vin:
OK, but what about the bug that still remains as described at
http://article.gmane.org/gmane.emacs.xemacs.beta/21891
This is a bug unrelated to site-lisp, but basically results
in the same incorrect behavior on Windows that is not present under unix.
Rodney
11:09 p.m.
On 1/22/06, Rodney Sparapani <rsparapa(a)mcw.edu> wrote:
Vin Shelton <acs <at> alumni.princeton.edu> writes:
>
> I believe the XEmacs startup code only searches site-lisp to 1 level
> down for directories to add to load-path. According to my
> experiments, this is the same behavior that XEmacs exhibits on Linux,
> when configured --with-site-lisp.
>
> I do not intend to change this behavior in the near-term, but as I
> wrote, a patch could be considered.
>
> Regards,
> Vin
>
>
Hi Vin:
OK, but what about the bug that still remains as described at
http://article.gmane.org/gmane.emacs.xemacs.beta/21891
This is a bug unrelated to site-lisp, but basically results
in the same incorrect behavior on Windows that is not present under unix.
Article reproduced here:
Steve Youngs <steve <at> sxemacs.org> writes:
When I posted I had misread what you wrote. I've since tested
and can
now say that XEmacs 21.4 _does_ support both site-packages/lisp/foo
and site-packages/foo/lisp.
Not on Windows: site-packages/lisp/bar are added to the load-path;
while site-packages/bar/lisp are not.
I don't see this behavior. Here's the test I ran on my 21.4 native
installation:
mkdir -p lisp/foo bar/lisp
cat >lisp/foo/foo1.el << EOF
; (message "foo1")
; (sit-for 5)
; EOF
cat >bar/lisp/foo2.el << EOF
(message "foo2")
(sit-for 5)
EOF
xemacs-21.4 -vanilla
(load-library "foo1")
(load-library "foo2")
both worked and the load-path looks like this:
`load-path' is a simple built-in variable.
Value: ("e:\\XEmacs\\site-packages\\lisp\\"
"e:\\XEmacs\\site-packages\\lisp\\foo\\"
"e:\\XEmacs\\site-packages\\bar\\lisp\\"
"e:\\XEmacs\\xemacs-packages\\lisp\\" ...
(locate-library "foo1")
"e:\\XEmacs\\site-packages\\lisp\\foo\\foo1.el"
(locate-library "foo2")
"e:\\XEmacs\\site-packages\\bar\\lisp\\foo2.el"
Can you please give me a simple recipe to reproduce the error you're seeing?
Thanks,
Vin
--
Whoever you are, no matter how lonely,
the world offers itself to your imagination,
calls to you like the wild geese, harsh and exciting--
over and over announcing your place
in the family of things. Mary Oliver
2:57 p.m.
Vin Shelton wrote:
mkdir -p lisp/foo bar/lisp
cat >lisp/foo/foo1.el << EOF
; (message "foo1")
; (sit-for 5)
; EOF
cat >bar/lisp/foo2.el << EOF
(message "foo2")
(sit-for 5)
EOF
xemacs-21.4 -vanilla
(load-library "foo1")
(load-library "foo2")
Can you please give me a simple recipe to reproduce the error you're seeing?
Hi Vin:
Following your script until the last load-library, from which I get the
error
Cannot open load file: foo2
That's because it is not in the load-path which is the site-package bug
that I'm
talking about.
Thanks,
Rodney
6:29 a.m.
>>>> "APA" == Adrian Aichner
<adrian(a)xemacs.org> writes:
APA> Rodney, Vin, I don't think XEmacs has a notion of site-lisp.
More specifically, it's deprecated. ./configure --with-site-lisp will
set up your XEmacs to look in $archlibdir/xemacs/site-lisp (or some
such, by default on Unix /usr/local/lib/xemacs/site-lisp I believe).
However, site-lisp is for _libraries_, not _packages_, and it is
simply added to the load-path, it is not searched for packages. That
means that (I conjecture, I don't do Windows so I don't remember the
specifics of the c:\XEmacs layout)
c:\XEmacs\site-lisp\ess.el
will be found, but Rodney's
c:\XEmacs\Packages\site-lisp\ess\lisp\ess.el
will not. That's why it's deprecated---it mostly doesn't do what you want.
Probably more than you wanted to know :-), but HTH.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
2:47 p.m.
Stephen J. Turnbull wrote:
More specifically, it's deprecated. ./configure --with-site-lisp will
set up your XEmacs to look in $archlibdir/xemacs/site-lisp (or some
such, by default on Unix /usr/local/lib/xemacs/site-lisp I believe).
However, site-lisp is for _libraries_, not _packages_, and it is
simply added to the load-path, it is not searched for packages. That
means that (I conjecture, I don't do Windows so I don't remember the
specifics of the c:\XEmacs layout)
c:\XEmacs\site-lisp\ess.el
will be found, but Rodney's
c:\XEmacs\Packages\site-lisp\ess\lisp\ess.el
will not. That's why it's deprecated---it mostly doesn't do what you want.
Probably more than you wanted to know :-), but HTH.
Hi Stephen:
You lost me about 3 sentences into your other post, so I won't comment
on that
one. However, I think this post is not correct: site-lisp/ess/lisp is
added to the
load-path in 21.5. What I was missing is that this is a configure
option. So,
can we get 21.4 built for the Windows installer with this option turned on?
Thanks,
Rodney
6878
days inactive
6885
days old
10 comments
5 participants
participants (5)
-
Adrian Aichner -
Rodney Sparapani -
Stephen J. Turnbull -
Vin Shelton -
Vin Shelton