Re: set-file-modes (XEmacs on w32)
18 years, 8 months
Reiner Steib
Reiner Steib
[ Not trimming the quotes because I added xemacs-beta.
See http://thread.gmane.org/gmane.emacs.gnus.general/62158
or http://thread.gmane.org/gmane.emacs.gnus.general/62140
for more context. ]
On Mon, Mar 06 2006, Reiner Steib wrote:
> On Sun, Mar 05 2006, Fabrice Popineau wrote:
>> * Reiner Steib <reinersteib+gmane(a)imap.cc> writes:
>>
>> Fabrice> - (set-file-modes filename nnmail-default-file-modes))) +
>> Fabrice> (gnus-set-file-modes filename nnmail-default-file-modes)))
>> Fabrice> I think it should be applied anyway. mail-source.el and
>> Fabrice> mm-decode.el also use set-file-modes.
>>
>> Reiner> I didn't investigate the callers, but maybe it *should*
>> Reiner> give an error if the modes cannot be set appropriately.
>> Reiner> (Shouldn't the respective (X)Emacs function care for those
>> Reiner> file system / operation system details?)
>>
>> The problem is that up to now, there were places where
>> #'gnus-set-file-modes was used and others where #'set-file-modes was
>> used. My point is that the same function should be used everywhere.
>
> My point is that it might be better if Gnus (at least in the default
> setup) should signal an error if it can't assure that the files or
> directories have appropriate permissions. Given that NTFS has the
> possibility to ensure that, I think it would be a mistake to set
> `gnus-ignore-set-file-modes-errors' to t by default on windows in
> general. On Windows 9x/ME and DOS -- but even there I'd think that
> (X)Emacs implementation of `set-file-modes' should deal with this
> and not Gnus.
I tried with Emacs 22 (system-type = windows-nt) on an NTFS
filesystem and with Emacs 22 on GNU/Linux on a vfat USB disk:
(require 'mail-source)
(set-file-modes "/path/to/file" mail-source-default-file-modes)
No error. Same with XEmacs 21.5.21 (+CVS-20050720) on GNU/Linux with
a file on the same vfat USB disk.
>> Reiner> *time passes* ... After reading the discussion
>> Reiner> <http://thread.gmane.org/gmane.emacs.gnus.general/57528>, I
>> Reiner> think we should change `gnus-set-file-modes' as follows...
>>
>> Seems ok to me. Your flag gnus-ignore-set-file-modes-errors should be t
>> on win32 native (don't know about cygwin).
>
> I looked at some non-Gnus occurrences of set-file-modes in XEmacs
> (21.4.17/lib/xemacs/xemacs-packages/lisp/*/*.el). (I didn't look at
> tramp and efs because those deal with remote files.)
>
> Only vm/vm-folder.el does something like `ignore-errors':
>
> vm/vm-folder.el:2675: (vm-error-free-call 'set-file-modes index-file (vm-octal 600))
>
> All other packages just call `set-file-modes' directly. Could you try
> if savehist-mode fails for you too? The version from XEmacs contains:
>
> (set-file-modes savehist-file savehist-modes)
>
> Maybe you could ask on xemacs-beta if it is intended that
> `set-file-modes' fails in your setup or if it is a bug.
Is is intended that `set-file-modes' throws an error in XEmacs in
Fabrice's setup?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
- 1 participants
- 0 comments
Re: [Patch21.5] Find a relative package root at runtime
18 years, 8 months
Michael Sperber
Michael Sperber
"Robert Pluim" <rpluim(a)gmail.com> writes:
> packages.el uses packages-find-package-hierarchies on the components of
> EMACSPACKAGEPATH, which in my case has the value
>
> ~\.xemacs;C:\Program Files\XEmacs\site-packages;C:\Program
> Files\XEmacs\xemacs-packages
>
> Unfortunately, what it's doing is looking for 'site-packages' or
> 'xemacs-packages' as subdirectories of the components of that variable,
> which obviously isn't going to work.
Yes. This changed recently (back to 21.4 behavior) with:
2005-12-30 Mike Sperber <mike(a)xemacs.org>
* packages.el (packages-find-all-package-hierarchies): Interpret
EMACSPACKAGEPATH as listing package direcories, not hierarchies.
This fixes a regression introduced in the change on 2005-01-08.
For an explanation of the difference between "hierarchies" and
"directories", see the top of packages.el:
;;; A *package hierarchy* is a directory that contains a collection of
;;; packages; it has lisp/, info/, etc/ etc. subdirectories that
;;; contain the files constituting the packages.
;;; A *package directory* contains package hierarchies---the package
;;; hierarchies are typically in directories "xemacs-packages",
;;; "mule-packages", and so on. A package hierarchy might only be
;;; applicable for specific variants of XEmacs.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
- 1 participants
- 0 comments
Re: [Patch21.5] Find a relative package root at runtime
18 years, 8 months
Vin Shelton
Vin Shelton
On 3/9/06, Robert Pluim <rpluim(a)gmail.com> wrote:
> I can delete the registry key easily enough, but what about those people who
> will be installing 21.5 on windows with an installer? Will we remove the
> key for them, or do we need to change the packages.el logic?
The InnoSetup-based setup kit does not mess with the EMACSPACKAGEPATH
key in the registry. I will modify the InnoSetup kit to warn users
about this problem, but I don't think I want to unconditionally delete
the registry key during installation, although I'm open to discussion
on this point.
- Vin
- 1 participants
- 0 comments
Re: [Patch21.5] Find a relative package root at runtime
18 years, 8 months
Vin Shelton
Vin Shelton
On 3/1/06, Michael Sperber <sperber(a)informatik.uni-tuebingen.de> wrote:
>
> Hi Vin,
>
> the Lisp part of the patch looks fine---I can do my work on top of
> that.
>
> Now, I see there's quite a bit of logic around the setting of
> PACKAGE_PATH. This really needs to go. PACKAGE_PATH itself is
> deprecated, and the settings in nt/xemacs.mak are just plain wrong for
> some configurations. Similarly for PACKAGE_PREFIX. If anything like
> PACKAGE_PREFIX needs to be set, it should be the value of
> PATH_LATE_PACKAGE_DIRECTORIES.
Hi Michael,
Is the following a minimalist version of what you mean? (This patch
should be applied on top of my earlier patches.)
--- xemacs.mak.~2~ 2006-02-27 22:33:08.142511900 -0500
+++ xemacs.mak 2006-03-09 09:27:18.031578800 -0500
＠＠ -812,7 +812,7 ＠＠
-DXEMACS_EXTRA_NAME=\"$(xemacs_extra_name:"=)\" \
!endif
!if defined(PATH_PACKAGEPATH)
- -DPATH_PACKAGEPATH=\"$(PATH_PACKAGEPATH)\" \
+ -DPATH_LATE_PACKAGE_DIRECTORIES=\"$(PATH_PACKAGEPATH)\" \
!endif
-DEMACS_CONFIGURATION=\"$(EMACS_CONFIGURATION)\"
TEMACS_CPP_FLAGS=$(CFLAGS) $(TEMACS_CPP_FLAGS_NO_CFLAGS)
＠＠ -1077,7 +1077,7 ＠＠
!endif
!if defined(PATH_PACKAGEPATH)
# PATH_PACKAGEPATH is already a quoted string.
-! if [echo PACKAGE_PATH>>$(CONFIG_VALUES) && echo
$(PATH_PACKAGEPATH)>>$(CONFIG_VALUES)]
+! if [echo PATH_LATE_PACKAGE_DIRECTORIES>>$(CONFIG_VALUES) && echo
$(PATH_PACKAGEPATH)>>$(CONFIG_VALUES)]
! endif
!endif
I don't understand under what configurations "the settings in
nt/xemacs.mak are just plain wrong".
If my proposal is on the wrong track or doesn't go far enough, please
send me a sample patch. I'm happy to do the scut work of making sure
all the i's are dotted and the t's are crossed and working the bare
bones of your changes into a patch that's ready for prime time.
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
- 1 participants
- 0 comments
Re: crash with xft under Asian locale
18 years, 8 months
Jens Petersen
Jens Petersen
Stephen J. Turnbull wrote:
> It's funny that it's only you big-name distro developers who are
> reporting this. Did you get a bug report which you're forwarding, or
> is this basically your own experience?
It is just my experience from personal testing of 21.5.
>>>>>> "Jens" == Jens Petersen <petersen(a)redhat.com> writes:
>
>> Jens> Not particularly AFAIK, but I can send you the system
>> Jens> fonts.conf from my Fedora Core 4 installation if you like.
>
> The fonts.conf you sent me is very different from what I get from
> Debian "sid".
Ok.
> I wonder if XEmacs is somehow getting confused about something because
> of Red Hat extensions.
Dunno, but xemacs isn't parsing the fonts.conf itself, is it?
Jens
- 2 participants
- 1 comments
Re: [Patch21.5] Find a relative package root at runtime
18 years, 8 months
Robert Pluim
Robert Pluim
OK, what the heck is an EMACSPACKAGEPATH key doing in my registry? And why
does (getenv "EMACSPACKAGEPATH") return its value. <sigh> I knew running
windows was going to be painful again.
Anyway, if I comment out the code in
packages.el:packages-find-all-package-hierarchies that parses the
EMACSPACKAGEPATH env var, then configure-package-path is used and it is
parsed correctly (this is in vanilla beta, without Vin's patch), and all the
packages are found.
I'm going to try again with Vin's patch in a second.
Robert
On 3/9/06, Robert Pluim <rpluim(a)gmail.com> wrote:
>
>
>
> On 3/8/06, Michael Sperber <sperber(a)informatik.uni-tuebingen.de> wrote:
> >
> >
> > > configure-package-path: ("~\\.xemacs" "" "c:\\Program
> > > Files\\XEmacs\\site-packag
> > > es" "c:\\Program Files\\XEmacs\\xemacs-packages")
> >
> > Are you really using an up-to-date version here? The semantics of
> > `configure-package-path' changed recently, back to the 21.4 version.
> > But you really should have this unset.
>
>
> With Vin's patch it's set by nt/xemacs.mak if PACKAGE_PREFIX is set, which
> it is in this case (in nt/config.inc). Unsetting it has no effect.
>
> What is the new way of telling emacs where the packages are?
>
> Robert
>
> --
>
>
> Cheers =8-} Mike
> Friede, Völkerverständigung und überhaupt blabla
>
>
- 1 participants
- 1 comments
Re: [Patch21.5] Find a relative package root at runtime
18 years, 8 months
Vin Shelton
Vin Shelton
(Re-directed to beta)
On 3/7/06, Robert Pluim <rpluim(a)gmail.com> wrote:
>
>
>
> On 3/6/06, Vin Shelton <acs(a)xemacs.org> wrote:
> > On 3/6/06, Robert Pluim <rpluim(a)gmail.com> wrote:
> > >
> > >
> > >
> > > On 2/28/06, Vin Shelton <acs(a)xemacs.org> wrote:
> > > > Attached is a patch which allows 21.5 to find a package tree in
> > > > ../xemacs-packages. This is similar to the patch I applied to 21.4 -
> > > >
> > >
> http://list-archive.xemacs.org/xemacs-patches/200512/msg00137.html
> > >
> > >
> > >
> > > Vin, the patch on its own works fine for me, except that XEmacs only
> finds
> > > packages in ~/.xemacs for me, not in c:\program file\xemacs. Is that
> > > currently expected behaviour?
> > >
> >
> > Hi Robert,
> >
> > Thanks for testing out the patch.
> >
> > Are you specifying a package path in your config.inc file? If you
> > are, that one should be respected. If you are not, then c:\program
> > files\XEmacs is no longer automatically searched.
>
>
>
> I wasn't, but putting one in seems to make no difference.
>
> > Please include a copy of your Installation file if you follow-up.
>
>
> Here it is:
>
> Building XEmacs using "NMAKE".
> Building XEmacs using make flags " ".
> Building XEmacs in source tree
> "C:\\cygwin\\home\\rpluim\\xemacs-21.5".
> For src, using compiler "cl -nologo -W3 -DSTRICT -Zi -Od -MDd -c -TP
> -IC:\cygwin\home\rpluim\xemacs-21.5\nt\inc -IC:\cygwin\home\rpluim\xemacs-
> 21.5\src -I"c:\cygwin\home\rpluim\xemacs-libs\xpm-3.4k"
> -I"c:\cygwin\home\rpluim\xemacs-libs\xpm-3.4k\lib"
> -I"c:\cygwin\home\rpluim\xemacs-libs\compface-1.5.1"
> -DHAVE_MS_WINDOWS -DHAVE_MENUBARS -DHAVE_SCROLLBARS -DHAVE_TOOLBARS
> -DHAVE_WIDGETS -DHAVE_DIALOGS -DHAVE_XPM -DFOR_MSW -DHAVE_GIF -DHAVE_XFACE
> -DHAVE_NATIVE_SOUND -DERROR_CHECK_ALL -DPDUMP -DUSE_KKCC -DSYSTEM_MALLOC
> -DDEBUG_XEMACS -D_DEBUG -DWIN32_LEAN_AND_MEAN -DWIN32_NATIVE -Demacs
> -DHAVE_CONFIG_H -DPATH_VERSION=\" 21.5-b25\"
> -DPATH_PROGNAME=\"xemacs\" -DEMACS_VERSION=\"21.5-b25\"
> -DEMACS_PROGNAME=\"xemacs\"
> -DSTACK_TRACE_EYE_CATCHER=xemacs_21_5_b25_i586_pc_win32
> -DPATH_PREFIX=\"..\" -DEMACS_MAJOR_VERSION=21 -DEMACS_MINOR_VERSION=5
> -DEMACS_BETA_VERSION=25 -DXEMACS_CODENAME=\""eggplant"\"
> -DXEMACS_EXTRA_NAME=\"(+CVS-20060305)\"
> -DPATH_PACKAGEPATH=\""~\\.xemacs;;c:\\Program
> Files\\XEmacs\\site-packages;c:\\Program
> Files\\XEmacs\\xemacs-packages"\"
> -DEMACS_CONFIGURATION=\"i586-pc-win32\"".
> For lib-src, using compiler "cl -nologo -W3 -DSTRICT -Zi -Od -MDd
> -IC:\cygwin\home\rpluim\xemacs-21.5\lib-src
> -IC:\cygwin\home\rpluim\xemacs-21.5\src -DHAVE_CONFIG_H -DWIN32_NATIVE".
> Compiling as C++.
> Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b25".
> Package path is "~\\.xemacs;;c:\\Program
> Files\\XEmacs\\site-packages;c:\\Program
> Files\\XEmacs\\xemacs-packages".
> Compiling in support for Microsoft Windows native GUI.
> Compiling in support for XPM images.
> Compiling in support for GIF images.
>
> --------------------------------------------------------------------
> NOTE: Compiling without PNG image support.
> NOTE: You should strongly consider installing the PNG libraries.
> NOTE: Otherwise certain images and glyphs may not display.
> NOTE: (a copy may be found in
> ftp://ftp.xemacs.org/pub/xemacs/aux
>
> --------------------------------------------------------------------
> Compiling in support for X-Face message headers.
> Compiling in support for toolbars.
> Compiling in support for dialogs.
> Compiling in support for widgets.
> Compiling in support for native sounds.
> Using portable dumper.
> Using system malloc.
> Using DLL version of C runtime library.
> Compiling in extra internal error-checking.
> NOTE:
> ---------------------------------------------------------
> NOTE: Compiling in support for runtime error-checking.
> NOTE: XEmacs will run noticeably more slowly as a result.
> NOTE: Error-checking is on by default for XEmacs beta releases.
> NOTE:
> ---------------------------------------------------------
> Compiling in debugging support (no slowdown).
> Using new experimental GC mark algorithms.
>
>
>
Are you saying you have packages installed in C:\Program
Files\XEmacs\xemacs-packages and they are not found? I guess I have 2
questions:
1. What are the contents of c:\Program Files\XEmacs\xemacs-packages?
Is there a pkginfo directory? What's in it?
2. Can you please start up XEmacs with the environment variable
EMACSDEBUGPATHS=t and send along the output?
Thank you,
Vin
PS. Did you run 'nmake -f xemacs.mak clean' after applying the patch?
- 3 participants
- 3 comments
[Success with Dynarr_add Workaround] XEmacs 21.5-b25 "eggplant" (+CVS-20060308) i586-pc-win32
18 years, 8 months
Adrian Aichner
Adrian Aichner
Still with UNION_TYPE, but with -GX- disabled again.
Adrian
> XEmacs Build Report generated by emacs-version
> 21.5 (beta24) "dandelion" (+CVS-20051218) XEmacs Lucid
> with system-configuration
> i586-pc-win32
> follows:
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\Installation:
> (Output from most recent run of ./configure)
OS version:
Microsoft Windows XP [Version 5.1.2600]
OS: Windows_NT
XEmacs 21.5-b25 "eggplant" (+CVS-20060308) configured for `i586-pc-win32'.
Building XEmacs using "NMAKE".
Building XEmacs using make flags " ".
Building XEmacs in source tree "c:\\Hacking\\cvs.xemacs.org\\XEmacs\\xemacs-21.5-clean".
For src, using compiler "cl -nologo -W3 -DSTRICT -Zi -O2 -G5 -Ob2 -MDd -c -TP -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\inc -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src -I"c:\Hacking\libs4xemacs\xpm-3.4k" -I"c:\Hacking\libs4xemacs\xpm-3.4k\lib" -I"c:\Hacking\libs4xemacs\libpng-1.0.2" -I"c:\Hacking\libs4xemacs\zlib" -I"c:\Hacking\libs4xemacs\tiff-v3.4\libtiff" -I"c:\Hacking\libs4xemacs\jpeg-6b" -I"c:\Hacking\libs4xemacs\compface" -I"c:\Hacking\libs4xemacs\zlib" -DHAVE_MS_WINDOWS -DHAVE_MENUBARS -DHAVE_SCROLLBARS -DHAVE_TOOLBARS -DHAVE_WIDGETS -DHAVE_DIALOGS -DHAVE_XPM -DFOR_MSW -DHAVE_GIF -DHAVE_PNG -DHAVE_TIFF -DHAVE_JPEG -DHAVE_XFACE -DHAVE_ZLIB -DHAVE_NATIVE_SOUND -DMULE -DUSE_UNION_TYPE -DPDUMP -DNEW_GC -DUSE_KKCC -DSYSTEM_MALLOC -DDEBUG_XEMACS -D_DEBUG -DWIN32_LEAN_AND_MEAN -DWIN32_NATIVE -Demacs -DHAVE_CONFIG_H -DPATH_VERSION=\"21.5-b25\" -DPATH_PROGNAME=\"xemacs\" -DEMACS_VERSION=\"21.5-b25\" -DEMACS_PROGNAME=\"xemacs\" -DSTACK!
_TRACE_EYE_CATCHER=xemacs_21_5_b25_i586_pc_win32 -DPATH_PREFIX=\"..\" -DEMACS_MAJOR_VERSION=21 -DEMACS_MINOR_VERSION=5 -DEMACS_BETA_VERSION=25 -DXEMACS_CODENAME=\""eggplant"\" -DXEMACS_EXTRA_NAME=\"(+CVS-20060308)\" -DEMACS_CONFIGURATION=\"i586-pc-win32\" -DPATH_PACKAGEPATH=\""~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages"\"".
For lib-src, using compiler "cl -nologo -W3 -DSTRICT -Zi -O2 -G5 -Ob2 -MDd -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lib-src -Ic:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src -DHAVE_CONFIG_H -DWIN32_NATIVE".
Compiling as C++.
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b25".
Package path is "~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages".
Compiling in support for Microsoft Windows native GUI.
Compiling in international (MULE) support.
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 X-Face message headers.
Compiling in support for GZIP compression/decompression.
Compiling in support for toolbars.
Compiling in support for dialogs.
Compiling in support for widgets.
Compiling in support for native sounds.
Using union type for Lisp object storage.
NOTE: ---------------------------------------------------------
NOTE: This tends to trigger compiler bugs, especially when combined
NOTE: with MULE and ERROR_CHECKING. Crashes in pdump have recently
NOTE: been observed using Visual C++ in combination with union type,
NOTE: MULE, and ERROR_CHECKING.
NOTE: ---------------------------------------------------------
Using portable dumper.
Using system malloc.
Using DLL version of C runtime library.
Compiling in debugging support (no slowdown).
Compiling with optimization.
Using new experimental GC mark algorithms.
Using new experimental incremental garbage collector and new allocator.
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\xemacs-21.5-clean-cvs-update.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\
Compilation started at Thu Mar 09 08:37:28 2006 +0100 (W. Europe Standard Time)
? gunzip-error.txt
? man/lispref/errors.texi.new
? nt/xemacs-21.5-clean-make-all-internal-compiler-error-not-cpp.err
? nt/xemacs-21.5-clean-make-all-internal-compiler-error.err
? nt/xemacs-21.5-clean-make-all-texinfo-error.err
M src/frame-msw.c
M src/lisp.h
cvs server: Updating tests
cvs server: Updating tests/DLL
M tests/automated/region-tests.el
Compilation finished at Thu Mar 09 08:38:41
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-all.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\
nmake /f xemacs.mak all
Compilation started at Thu Mar 09 08:40:17 2006 +0100 (W. Europe Standard Time)
Installing XEmacs in "c:\\Program Files\\XEmacs\\XEmacs-21.5-b25".
1 file(s) copied.
1 File(s) copied
1 File(s) copied
c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\src\text.c(2177) : warning C4390: ';' : empty controlled statement found; is this the intent?
Using load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\)
Using module-load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\modules)
Generating autoloads for lisp/next-error.el...
While compiling describe-register-1 in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\register.el:
** reference to free variable yank-excluded-properties
While compiling the end of the data:
** the function remove-list-of-text-properties is not known to be defined.
While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\diagnose.el:
** The following functions are not known to be defined:
sort-numeric-fields, gc-stats
While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\mule\mule-cmds.el:
** the function set-console-tty-coding-system is not known to be defined.
While compiling forward-paragraph in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\paragraphs.el:
** variable multiple-lines bound but not referenced
While compiling the end of the data:
** the function constrain-to-field is not known to be defined.
Using load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\)
Using module-load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\modules)
While compiling x-win-init-xfree86 in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\x-win-xfree86.el:
** assignment to free variable x-us-keymap-first-keycode
** assignment to free variable x-us-keymap-description
While compiling x-win-init-sun in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\x-win-sun.el:
** assignment to free variable x-us-keymap-first-keycode
** assignment to free variable x-us-keymap-description
While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\x-init.el:
** the function x-keysym-hash-table is not known to be defined.
While compiling x-font-menu-load-font-xft in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\x-font-menu.el:
** reference to free variable fc-font-name-property-family
** reference to free variable fc-font-name-property-weight
** reference to free variable fc-font-name-property-size
** reference to free variable fc-font-name-property-slant
While compiling the end of the data:
** The following functions are not known to be defined:
fc-find-available-weights-for-family,
fc-find-available-font-families, xlfd-font-name-p,
fc-font-real-pattern, fc-pattern-get-family,
fc-pattern-get-successp, fc-pattern-get-weight,
fc-pattern-get-size, fc-pattern-get-slant,
fc-font-weight-translate-to-string,
fc-font-slant-translate-to-string, make-fc-pattern,
fc-pattern-add, fc-font-weight-translate-from-string,
fc-font-slant-translate-from-string, fc-name-unparse
While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\x-faces.el:
** The following functions are not known to be defined:
fc-font-real-pattern, default-x-device, fc-pattern-get,
fc-pattern-del, fc-pattern-duplicate, fc-pattern-add,
fc-name-unparse
Requiring next-error...
While compiling multi-occur in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\occur.el:
** variable ido-ignore-item-temp-list bound but not referenced
** misplaced interactive spec: (interactive (cons (let* ((bufs (list (read-buffer "First buffer to search: " (current-buffer) t))) (buf nil) (ido-ignore-item-temp-list bufs)) (while (not (string-equal (setq buf (read-buffer (if (and-boundp (quote read-buffer-function) (quote (eq read-buffer-function (quote ido-read-buffer)))) "Next buffer to search (C-j to end): " "Next buffer to search (RET to end): ") nil t)) "")) (add-to-list (quote bufs) buf) (setq ido-ignore-item-temp-list bufs)) (nreverse (mapcar (function get-buffer) bufs))) (occur-read-primary-args)))
While compiling occur-engine:
** reference to free variable jit-lock-mode
While compiling the end of the data:
** the function jit-lock-fontify-now is not known to be defined.
Compiling c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\next-error.el...
Wrote c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\next-error.elc
While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\gtk.el:
** the function gtk-import-function is not known to be defined.
While compiling toplevel forms in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\gtk-iso8859-1.el:
** assignment to free variable character-set-property
While compiling the end of the data in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\fontconfig.el:
** The following functions are not known to be defined:
fc-pattern-get, fc-pattern-add, fc-list-fonts-pattern-objects,
default-x-device, fc-pattern-p, fc-name-parse
While compiling toplevel forms in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\font.el:
** reference to free variable xft-font-regexp
While compiling the end of the data:
** The following functions are not known to be defined:
default-x-device, fc-font-real-pattern, fc-pattern-get,
fc-pattern-add, fc-name-unparse
While compiling toplevel forms in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\mule\thai-util.el:
** define-category called with 3 arguments, but accepts only 2
** define-category called with 3 arguments, but accepts only 2
** define-category called with 3 arguments, but accepts only 2
While compiling the end of the data:
** the function make-category-table is not known to be defined.
While compiling toplevel forms in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\mule\lao-util.el:
** define-category called with 3 arguments, but accepts only 2
** define-category called with 3 arguments, but accepts only 2
** define-category called with 3 arguments, but accepts only 2
** define-category called with 3 arguments, but accepts only 2
While compiling the end of the data:
** the function make-category-table is not known to be defined.
While compiling ethio-modify-vowel in file c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\mule\ethio-util.el:
** decompose-composite-char is an obsolete function; use char-to-string instead.
Computing custom-loads for next-error...
Compilation finished at Thu Mar 09 08:44:04
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-check-temacs.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\
nmake /f xemacs.mak check-temacs
Compilation started at Thu Mar 09 08:48:13 2006 +0100 (W. Europe Standard Time)
Using load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\lisp\)
Using module-load-path (c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\modules)
base64-tests.el: 1234 of 1234 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
byte-compiler-tests.el: 66 of 66 tests successful (100%).
38 tests skipped because can't defadvice.
0 errors that should have been generated, but weren't
0 wrong-error failures
c-tests.el: 4 of 4 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
case-tests.el: 1148 of 1148 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
ccl-tests.el: 4570 of 4570 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
database-tests.el: No tests run.
0 errors that should have been generated, but weren't
0 wrong-error failures
extent-tests.el: 194 of 194 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
hash-table-tests.el: 9866 of 9866 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
lisp-tests.el: 3672 of 3672 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
md5-tests.el: 56 of 56 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
mule-tests.el: 232 of 236 tests successful ( 98%).
0 errors that should have been generated, but weren't
0 wrong-error failures
Unexpected error (void-function executable-find) while executing interpreted code.
Unexpected error (void-function executable-find) while executing byte-compiled code.
os-tests.el: No tests run.
Unexpected error (void-function executable-find) while executing interpreted code
Unexpected error (void-function executable-find) while executing byte-compiled code
0 errors that should have been generated, but weren't
0 wrong-error failures
regexp-tests.el: 350 of 350 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests-1-1.el: 28 of 28 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests.el: 38 of 38 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
symbol-tests.el: 246 of 246 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
syntax-tests.el: 66 of 72 tests successful ( 91%).
2 tests skipped because c-mode unavailable.
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
0 errors that should have been generated, but weren't
0 wrong-error failures
tag-tests.el: 6 of 6 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
weak-tests.el: 140 of 140 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
base64-tests.el: 1234 of 1234 tests successful (100%).
byte-compiler-tests.el: 66 of 66 tests successful (100%).
c-tests.el: 4 of 4 tests successful (100%).
case-tests.el: 1148 of 1148 tests successful (100%).
ccl-tests.el: 4570 of 4570 tests successful (100%).
database-tests.el: No tests run.
extent-tests.el: 194 of 194 tests successful (100%).
hash-table-tests.el: 9866 of 9866 tests successful (100%).
lisp-tests.el: 3672 of 3672 tests successful (100%).
md5-tests.el: 56 of 56 tests successful (100%).
mule-tests.el: 232 of 236 tests successful ( 98%).
os-tests.el: No tests run.
regexp-tests.el: 350 of 350 tests successful (100%).
region-tests-1-1.el: 28 of 28 tests successful (100%).
region-tests.el: 38 of 38 tests successful (100%).
symbol-tests.el: 246 of 246 tests successful (100%).
syntax-tests.el: 66 of 72 tests successful ( 91%).
tag-tests.el: 6 of 6 tests successful (100%).
weak-tests.el: 140 of 140 tests successful (100%).
Compilation finished at Thu Mar 09 08:48:42
> Contents of c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\xemacs-21.5-clean-make-check.err
> keeping lines matching
> "^--\[\[\|\]\]$\|^\(cd\|n?make\)\s-\|errors?\|warnings?\|pure.*\(space\|size\)\|hides\b\|strange\|shadowings\|^Compil\(ing\s-+in\|ation\)\|^Using\|not\s-+found\|^While\s-+compiling.*\(
\s-+.+\)*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+\|^[A-Z] [^ ]+$\|^Wrong number of arguments:\|^ \*\* "
> and then deleting lines matching
> "confl.*with.*auto-inlining\|^Formatting:"
cd c:\Hacking\cvs.xemacs.org\XEmacs\xemacs-21.5-clean\nt\
nmake /f xemacs.mak check
Compilation started at Thu Mar 09 08:51:30 2006 +0100 (W. Europe Standard Time)
base64-tests.el: 1234 of 1234 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
byte-compiler-tests.el: 104 of 104 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
c-tests.el: 4 of 4 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
case-tests.el: 1148 of 1148 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
ccl-tests.el: 4570 of 4570 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
database-tests.el: No tests run.
0 errors that should have been generated, but weren't
0 wrong-error failures
extent-tests.el: 194 of 194 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
hash-table-tests.el: 9866 of 9866 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
lisp-tests.el: 3672 of 3672 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
md5-tests.el: 56 of 56 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
mule-tests.el: 232 of 236 tests successful ( 98%).
0 errors that should have been generated, but weren't
0 wrong-error failures
os-tests.el: 20 of 20 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
regexp-tests.el: 350 of 350 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests-1-1.el: 28 of 28 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
region-tests.el: 38 of 38 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
symbol-tests.el: 246 of 246 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
syntax-tests.el: 70 of 76 tests successful ( 92%).
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
KNOWN BUG: (backward-up-list-moves-point-from-to 23 3) ==> error: (syntax-error "Unbalanced parentheses")
0 errors that should have been generated, but weren't
0 wrong-error failures
tag-tests.el: 6 of 6 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
weak-tests.el: 140 of 140 tests successful (100%).
0 errors that should have been generated, but weren't
0 wrong-error failures
base64-tests.el: 1234 of 1234 tests successful (100%).
byte-compiler-tests.el: 104 of 104 tests successful (100%).
c-tests.el: 4 of 4 tests successful (100%).
case-tests.el: 1148 of 1148 tests successful (100%).
ccl-tests.el: 4570 of 4570 tests successful (100%).
database-tests.el: No tests run.
extent-tests.el: 194 of 194 tests successful (100%).
hash-table-tests.el: 9866 of 9866 tests successful (100%).
lisp-tests.el: 3672 of 3672 tests successful (100%).
md5-tests.el: 56 of 56 tests successful (100%).
mule-tests.el: 232 of 236 tests successful ( 98%).
os-tests.el: 20 of 20 tests successful (100%).
regexp-tests.el: 350 of 350 tests successful (100%).
region-tests-1-1.el: 28 of 28 tests successful (100%).
region-tests.el: 38 of 38 tests successful (100%).
symbol-tests.el: 246 of 246 tests successful (100%).
syntax-tests.el: 70 of 76 tests successful ( 92%).
tag-tests.el: 6 of 6 tests successful (100%).
weak-tests.el: 140 of 140 tests successful (100%).
Compilation finished at Thu Mar 09 08:51:59
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
- 1 participants
- 0 comments
Simply Fantastic Results
18 years, 8 months
Philip Niles
Philip Niles
Hey it works :-)
All you have to do is click the link below
and you will see why I'm excited for the first time
in months in promoting my programs.
I save time with this because I don't have to e-mail
up to ten different programs. I do it once and I just saved
3 hours of Internet work. Try it. It works!
http://www.eMarketingForYou.com/?tim
Comes with residual commission. :-)
Let me know what you think!
Phillip Niles,
phillipniles(a)Safe-mail.net
If you do not want me to email you again just email me back with
remove in the subject link at: phillipniles(a)Safe-mail.net
To unsubscribe:
http://www.newdaysuccess.com/cgi-bin/list/swmlist.cgi?mode=r&a=second&e=x...
- 1 participants
- 0 comments
Simply Fantastic Results
18 years, 8 months
Philip Niles
Philip Niles
Hey it works :-)
All you have to do is click the link below
and you will see why I'm excited for the first time
in months in promoting my programs.
I save time with this because I don't have to e-mail
up to ten different programs. I do it once and I just saved
3 hours of Internet work. Try it. It works!
http://www.eMarketingForYou.com/?tim
Comes with residual commission. :-)
Let me know what you think!
Phillip Niles,
phillipniles(a)Safe-mail.net
If you do not want me to email you again just email me back with
remove in the subject link at: phillipniles(a)Safe-mail.net
To unsubscribe:
http://www.newdaysuccess.com/cgi-bin/list/swmlist.cgi?mode=r&a=first&e=xe...
- 1 participants
- 0 comments