XEmacs 21.0-beta40 "Saanen" is released
26 years, 6 months
SL Baur
SL Baur
The next edition of XEmacs 21.0 has been uploaded to the ftp site.
ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/
CVS sources are at
http://cvs.xemacs.org/
Installable Lisp packages are in:
ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.0/packages/binary-packages/
[as of the time I hit C-c C-c, both areas have been fully uploaded]
The CVS tag for this beta is `r21-0b40'.
To read about the Saanen Goat please see:
http://www.ansi.okstate.edu/breeds/goats/saanen/index.htm
* Comments
We are officially in feature freeze. It's time now to start cleaning things
up. I'd like to plan on about two weeks of cooling off where a lot of time
is spent enumerating and chasing down visible problems, and have a full code
freeze (show stopping bug fixes only) for at least two weeks prior to 'net
release. With usual slippage, perhaps we can have a release after the 4th of
July.
The rate of releases will be slowing dramatically as things stabilize.
*IMPORTANT* xemacs-base has been updated since the last release. Please
download and install the new version before starting. The function `kbd' in
edmacro.el has been moved into the XEmacs core.
*IMPORTANT* pcl-cvs has a critical bug fix due to an XEmacs interface
change. If you are using pcl-cvs please upgrade to the new version.
There are lots of bug fixes but due to some of the most recent patches
integrated there may be new build problems. Please report any difficulties
to xemacs-beta(a)xemacs.org.
* Updated packages
The following packages have been updated on the FTP site. Packages marked
with the tag `[REQUIRED]' should be upgraded for this beta.
ediff-1.08
viper-1.07:
New versions from Michael Kifer
edit-utils-1.22:
edit-faces.el uses easymenu now.
lazy-shot.el has some debug messages removed
xemacs-base-1.20: [REQUIRED]
edmacro.el -- kbd function removed
thing.el -- boundary condition in thing-symbol fixed
mule-base-1.17:
Fix tty coding system setting
mail-lib-1.14:
Fix keymap initialization in mail-abbrevs.el
tm-1.07:
tm-edit/tm-view now use easymenu
vc-1.08:
Major synchage with FSF Emacs 20.2.
sh-script-1.05:
Bug fix with how extensions in shell name are dealt with
pcl-cvs-1.09: [REQUIRED]
Bug fixes (one due to an XEmacs interface change)
* Recent Changes
We've decided to push forward on Drag'n'Drop and try to get
_something_ into the 21.0 release. Hopefully it will be something
better than just wildly experimental. Please see the tests in
tests/Dnd (droptest.el and dragtest.el) and give them a spin and see
well they work or don't work.
There's a lot of new MS Windows support in this, including toolbar,
processes, and Xpm.
I'm happy with the package path/startup path stuff for the first time
in a number of betas. Hopefully, we're past the worst of the changes.
All path stuffs should work again.
The configure option --gung-ho now controls whether minimal tagbits
and indexed lrecords are used.
Please test the -elc tarball with this beta. I've generated it from a
tty-only build for testing. While this should work (and the build now
currently assumes it does work), and it seems to work for me, it needs
as much testing as possible prior to release.
Canna detection should work better.
LDAP support should build and run.
Multicast support should build and run.
The default target of `make' is to build everything. This is almost
what `make dist' used to do except that finder-inf.el (the finder
database) gets properly bytecompiled.
DLL support is now autodetected.
The configure option `--with-dlmalloc' has been added so that
gmalloc.c can still be used on systems with the Doug Lea new GNU
Malloc.
The Installation file format has changed slightly -- the version
number is now printed in the summary, old copies are not retained, so
if you wish old copies you will have to make the copy by hand. The
Installation summary is available via the command M-x describe-installation.
`XEmacs' can be used for X resources. This feature needs further
testing but appears to work.
dlmalloc now works with mmap'ping enabled for Linux Libc5 systems.
I'm very interested in reports on how XEmacs' virtual memory footprint
changes with time with dlmalloc. My own experiences with mmap
disabled (only for glibc-2.0 and Mule) show a net win over 20.4. I'm
hoping mmap improves things further.
The source-packages subdirectory on the FTP site has been abolished in
favor of distributing Lisp sources via CVS.
The minimum required packages are the following: [Only xemacs-base updated
since the last beta, the package version number is relatively unimportant]
xemacs-base-1.20-pkg.tar This package contains core
functionality not dumped into XEmacs.
It includes things like the debugger,
comint, ring, etc.
mail-lib-1.14-pkg.tar This package contains core
functionality common to mail and
newsreading.
*NOTE:* As of beta39, you must use mule-base-1.16 or later. Note
also, as of beta34, overlay.el has been moved to the fsf-compat
package. As of beta40, you must have xemacs-base-1.20 or later.
If you are building with Mule, you will need to have the mule-base
package installed *prior* to dumping XEmacs or you will lose. If you
see messages about mule-charset not found, or get a bomb immediately
after seeing a message about `loading ... dialog', then you need to
stop and install the mule-base package.
Other various packages need to be installed prior to dumping XEmacs.
They are marked with `dump t' in the package description, see
package-get-base.el and package-get.el for an interface.
** ImageMagick has gone away courtesy of Jareth Hein.
** The generalization of the XEmacs internals has continued.
Quoting Kyle Jones:
If you're feeling maximally gung, add -DUSE_MINIMAL_TAGBITS and
-DUSE_INDEXED_LRECORD_IMPLEMENTATION to your compiler flags when
you build 20.5. If all is well XEmacs should build and run
normally.
Update: These options are now enabled by specifying `--gung-ho'.
-DUSE_MINIMAL_TAGBITS will be automatically set if using dlmalloc.
NOTE: It should *never* be required to use these options for proper
operation of XEmacs (with the single exception of -DUSE_MINIMAL_TAGBITS
for dlmalloc). A failure _without_ these options set is a bug that
needs to be fixed.
** Chinese and Korean Wnn server support has been added to LEIM. Someone
familiar to cWnn and kWnn will need to test this out. I haven't heard
any reports positive or negative yet.
* Futures
** 21.0-beta41 is scheduled for Saturday, May 23.
** The highest priority is testing and bug fixing.
For those not acquainted with recent XEmacsen (things have changed
since 20.3/21.0-b11), there are 4 files in the distribution. Each file
has been PGP signed.
*** xemacs-21.0-b39-21.0-b40.patch.gz
This is a patch from the previous release. Please see the file
etc/BETA for patching instructions. As of beta13 we're through the
worst of the reorganizations and patching should be pretty smooth from
here on out.
*** xemacs-21.0-b40.tar.gz
This is the core distribution without bytecompiled lisp and without
processed texinfo manuals. If you are on a fast machine with a
possibly slow connection to the FTP site, this is all you need for
an XEmacs non-mule. Untar it, run configure, then run `make'
and `make install'.
*** xemacs-21.0-b40-info.tar.gz
This the processed texinfo manuals. If you have makeinfo installed
and your machine has any kind of decent speed, it is quicker to run
`make info' from the toplevel and rebuild it yourself than it is to
download and untar it. You will need a fairly recent version of
makeinfo in order to be able process all the info documentation. At
least `makeinfo (GNU texinfo 3.11) 1.68' is recommended. Note that
the latest version of GNU texinfo is now 3.12.
*** xemacs-21.0-b40-elc.tar.gz
This is the bytecompiled lisp. It was freshly bytecompiled from
scratch prior to distribution.
to 21.0 beta40 "Saanen"
-- Vertical divider hacking from Didier Verna and Kirill Katsnelson
-- Bind cut'n'paste keys to generic functions from Jonathan Harris
-- MS Windows toolbar size fix from Andy Piper
-- Icons from MS Windows resources from Andy Piper
-- New function `windows-text-lines-pixel-height' from Greg Klanderman
-- Window beats buffer in specifiers from Kirill Katsnelson
-- Dialog box as a dialog box from Kirill Katsnelson
-- More DnD fixes from Oliver Graf
-- NEWS updates from Hrvoje Niksic
-- More device metrics from Kirill Katsnelson
-- Miscellaneous patches from Hrvoje Niksic
-- Documentation updates from Christian Nybø
-- More vertical divider fixes from Kirill Katsnelson
-- New function zap-up-to-char, behaves like zap-to-char in Emacs 18
-- Toolbar fixes from Andy Piper
-- Miscellaneous MS Windows fixes from Kirill Katsnelson
-- vertical divider shadow thickness specifier from Didier Verna
-- More device metrics from Kirill Katsnelson
-- Minibuffer synch with FSF Emacs from Michael Sperber
-- DnD fixes from Oliver Graf
-- decode-path cleanup from Hrvoje Niksic
-- Miscellaneous patches from Hrvoje Niksic
-- clear region bg pixmap fixes from Andy Piper
-- Various cleanup patches from Martin Buchholz
-- miscellaneous code cleanup
-- with-display-help-buffer fixes from Hrvoje Niksic
-- Draggable vertical dividers from Kirill Katsnelson
-- More MS Windows DnD support from Jonathan Harris
-- Reversion to old key descriptions from Hrvoje Niksic
-- DnD updates from Oliver Graf
-- Fix mouse(-pixel)?-position from Kirill Katsnelson
-- More device metrics fixes from Kirill Katsnelson
-- background pixmaps for MS Windows from Andy Piper
-- various build fixes from SAKIYAMA Nobuo and Kirill Katsnelson
-- Fix for non-interruptible re_search from Hrvoje Niksic
-- miscellaneous fixes from Hrvoje Niksic
-- focus frame fixes from Hrvoje Niksic
-- Really apply Kyle Jones' realpath fixes (sorry).
- 1 participants
- 0 comments
describe-key on control shift r
26 years, 6 months
Daniel B. Krech
Daniel B. Krech
I am trying to rewrite the following line from my GNUEmacs .emacs file:
(global-set-key [?\C-\S-r] 'revert-buffer)
I believe the following should work:
(define-key global-map '(control R) 'revert-buffer)
When I do:
M-x describe-bindings
I get:
C-R revert-buffer
BUT WHEN I do:
M-x describe-key
And type "control-shift-r" -- I get:
C-r runs `isearch-backward'
I am running XEmacs 21.0 "Saanen-pre4" [Lucid] (i386-pc-cygwin32) of Fri
May 15 1998 on MONKEY via xemacs -q -no-site-file.
How does this behave on non windows platforms?
-Dan
- 1 participants
- 0 comments
Re: makeinfo under i386-pc-cygwin32
26 years, 6 months
SL Baur
SL Baur
Daniel B Krech <dkrech(a)eJungle.com> writes:
> I am building xemacs under i386-pc-cygwin32 with success!! But remember
> reading something about needing a certain version of makeinfo to generate
> info files. Does such a version exist somewhere?
ftp://prep.ai.mit.edu/pub/gnu/
> cd /openSource/xemacs-20/man && make --unix CC='gcc'
> CFLAGS='-g -O2 -Wall -Wno-switch' LDFLAGS='' CPPFLAGS='' info
> makeinfo cl.texi -o ../info/cl.info
> makeinfo: permission denied
If this was a Unix system, I'd say you probably don't have write
permission in the info/ directory, or perhaps do not have permission
to execute the `makeinfo' binary.
- 1 participants
- 0 comments
decode-path update
26 years, 6 months
Hrvoje Niksic
Hrvoje Niksic
This patch:
* Renames decode-path to split-path. This name is much more
consistent with other functions (e.g. split-string).
* Introduces split-string-by-char, which is analogous to split-string,
only it splits by a single character. Ben is against this, but as
split-string is very slow and and we already have the code, I think
it makes sense to export it.
split-path was supposed to be implemented in terms of
split-string-by-char, but it turns out that it is called VERY early
during XEmacs startup, so that's impossible.
src/ChangeLog:
1998-05-16 Hrvoje Niksic <hniksic(a)srce.hr>
* emacs.c (decode_path): Eliminate compiler warning.
(Fdecode_path): Renamed to Fsplit_path.
(Fsplit_string_by_char): New function.
lisp/ChangeLog:
1998-05-16 Hrvoje Niksic <hniksic(a)srce.hr>
* loadup.el (really-early-error-handler): Ditto.
* update-elc.el: Ditto.
* setup-paths.el (paths-construct-exec-path): Ditto.
* make-docfile.el: Ditto.
* find-paths.el (paths-decode-directory-path): Use split-path
instead of decode-path.
* files.el (parse-colon-path): Update docstring reference.
--- etc/NEWS.orig Sat May 16 02:00:44 1998
+++ etc/NEWS Sat May 16 02:00:47 1998
＠＠ -304,10 +304,10 ＠＠
** The new `lwarn' function, analogous to `lmessage', allows printing
a formatted warning, with a non-default CLASS or LABEL.
-** The new function `decode-path' can now be used to explode the
-components of a colon-separated search path into a list of strings.
+** The new function `split-path' can now be used to explode the
+components of a colon-separated search path into a list.
- (decode-path "foo:bar")
+ (split-path "foo:bar")
=> ("foo" "bar")
** Specifiers and symbols whose value is a specifier are now allowed
--- src/emacs.c.orig Sat May 16 00:56:40 1998
+++ src/emacs.c Sat May 16 02:02:16 1998
＠＠ -2449,56 +2449,58 ＠＠
#define SEPCHAR ':'
#endif
-/* Parse PATH as a list of strings separated by SEPCHAR, and return
- the list of Lisp strings. PATH should be in internal format. */
+/* Split STRING into a list of substrings. The substrings are the
+ parts of original STRING separated by SEPCHAR. */
static Lisp_Object
-decode_path_1 (CONST Bufbyte *path, Bytecount size, Emchar sepchar)
+split_string_by_emchar_1 (CONST Bufbyte *string, Bytecount size,
+ Emchar sepchar)
{
- Lisp_Object lpath = Qnil;
- CONST Bufbyte *end = path + size;
+ Lisp_Object result = Qnil;
+ CONST Bufbyte *end = string + size;
while (1)
{
- CONST Bufbyte *p = path;
+ CONST Bufbyte *p = string;
while (p < end)
{
if (charptr_emchar (p) == sepchar)
break;
INC_CHARPTR (p);
}
- /* #### Do dos2unix path conversion on the freshly created
- string here? I am not convinced that this function needs
- such mangling. */
- lpath = Fcons (make_string (path, p - path), lpath);
+ result = Fcons (make_string (string, p - string), result);
if (p < end)
{
- path = p;
- INC_CHARPTR (path); /* skip sepchar */
+ string = p;
+ INC_CHARPTR (string); /* skip sepchar */
}
else
break;
}
- return Fnreverse (lpath);
+ return Fnreverse (result);
}
-/* The same as the above, only PATH is an external C string (it is
- converted at FORMAT_FILENAME), and sepchar is hardcoded to SEPCHAR
+/* The same as the above, except PATH is an external C string (it is
+ converted as FORMAT_FILENAME), and sepchar is hardcoded to SEPCHAR
(':' or whatever). */
Lisp_Object
decode_path (CONST char *path)
{
int len;
+ Bufbyte *newpath;
if (!path)
return Qnil;
- /* #### Is this correct? Ben, heeelp! */
- GET_C_CHARPTR_INT_FILENAME_DATA_ALLOCA (path, path);
+ GET_C_CHARPTR_INT_FILENAME_DATA_ALLOCA (path, newpath);
- len = strlen (path);
+ len = strlen (newpath);
+ /* #### Does this make sense? It certainly does for
+ decode_env_path(), but it looks dubious here. Does any code
+ depend on decode_path("") returning nil instead of an empty
+ string? */
if (!len)
return Qnil;
- return decode_path_1 ((CONST Bufbyte *)path, (Bytecount)len, SEPCHAR);
+ return split_string_by_emchar_1 (newpath, (Bytecount)len, SEPCHAR);
}
Lisp_Object
＠＠ -2512,33 +2514,42 ＠＠
return decode_path (path);
}
-DEFUN ("decode-path", Fdecode_path, 1, 2, 0, /*
-Explode a search path separated by SEPCHAR into a list of strings.
-If omitted, SEPCHAR defaults to the character specified by
-`path-separator'.
+/* Ben thinks this function should not exist or be exported to Lisp.
+ We use it to define split-path-string in subr.el (not!). */
+
+DEFUN ("split-string-by-char", Fsplit_string_by_char, 1, 2, 0, /*
+Split STRING into a list of substrings originally separated by SEPCHAR.
*/
- (path, sepchar))
+ (string, sepchar))
+{
+ CHECK_STRING (string);
+ CHECK_CHAR (sepchar);
+ return split_string_by_emchar_1 (XSTRING_DATA (string),
+ XSTRING_LENGTH (string),
+ XCHAR (sepchar));
+}
+
+/* #### This was supposed to be in subr.el, but is used VERY early in
+ the bootstrap process, so it goes here. Damn. */
+
+DEFUN ("split-path", Fsplit_path, 1, 1, 0, /*
+Explode a search path into a list of strings.
+The path components are separated with the characters specified
+with `path-separator'.
+*/
+ (path))
{
- Emchar sepch;
-
CHECK_STRING (path);
- if (NILP (sepchar))
- {
- while (!STRINGP (Vpath_separator)
- || (XSTRING_CHAR_LENGTH (Vpath_separator) != 1))
- Vpath_separator =
- signal_simple_continuable_error
- ("`path-separator' should be set to a one-character string",
- Vpath_separator);
- sepch = charptr_emchar (XSTRING_DATA (Vpath_separator));
- }
- else
- {
- CHECK_CHAR (sepchar);
- sepch = XCHAR (sepchar);
- }
- return decode_path_1 (XSTRING_DATA (path), XSTRING_LENGTH (path), sepch);
+ while (!STRINGP (Vpath_separator)
+ || (XSTRING_CHAR_LENGTH (Vpath_separator) != 1))
+ Vpath_separator = signal_simple_continuable_error
+ ("`path-separator' should be set to a single-character string",
+ Vpath_separator);
+
+ return (split_string_by_emchar_1
+ (XSTRING_DATA (path), XSTRING_LENGTH (path),
+ charptr_emchar (XSTRING_DATA (Vpath_separator))));
}
DEFUN ("noninteractive", Fnoninteractive, 0, 0, 0, /*
＠＠ -2626,7 +2637,8 ＠＠
DEFSUBR (Fquantify_clear_data);
#endif /* QUANTIFY */
- DEFSUBR (Fdecode_path);
+ DEFSUBR (Fsplit_string_by_char);
+ DEFSUBR (Fsplit_path); /* #### */
defsymbol (&Qkill_emacs_hook, "kill-emacs-hook");
defsymbol (&Qsave_buffers_kill_emacs, "save-buffers-kill-emacs");
--- src/symbols.c.orig Sat May 16 01:02:20 1998
+++ src/symbols.c Sat May 16 01:02:58 1998
＠＠ -715,8 +715,9 ＠＠
the user level, so there is no loss of generality.
If a symbol is "unbound", then the contents of its value cell is
- Qunbound. Despite appearances, this is *not* a symbol, but is
- a symbol-value-forward object.
+ Qunbound. Despite appearances, this is *not* a symbol, but is a
+ symbol-value-forward object. This is so that printing it results
+ in "INTERNAL EMACS BUG", in case it leaks to Lisp, somehow.
Logically all of the following objects are "symbol-value-magic"
objects, and there are some games played w.r.t. this (#### this
＠＠ -889,8 +890,7 ＠＠
a symbol-value-buffer-local object, and most of the
low-level functions below do not accept them; you need
to call follow_varalias_pointers to get the actual
- symbol to operate on.
- */
+ symbol to operate on. */
static Lisp_Object
mark_symbol_value_buffer_local (Lisp_Object obj,
--- lisp/subr.el.orig Sat May 16 01:18:01 1998
+++ lisp/subr.el Sat May 16 02:03:52 1998
＠＠ -305,6 +305,19 ＠＠
start (match-end 0)))
(nreverse (cons (substring string start) parts))))
+;; #### #### #### AAaargh! Must be in C, because it is used insanely
+;; early in the bootstrap process.
+;(defun split-path (path)
+; "Explode a search path into a list of strings.
+;The path components are separated with the characters specified
+;with `path-separator'."
+; (while (or (not stringp path-separator)
+; (/= (length path-separator) 1))
+; (setq path-separator (signal 'error (list "\
+;`path-separator' should be set to a single-character string"
+; path-separator))))
+; (split-string-by-char path (aref separator 0)))
+
(defmacro with-output-to-string (&rest forms)
"Collect output to `standard-output' while evaluating FORMS and return
it as a string."
--- lisp/files.el.orig Sat May 16 01:27:24 1998
+++ lisp/files.el Sat May 16 01:29:44 1998
＠＠ -395,7 +395,7 ＠＠
If you think you want to use this, you probably don't. This function
is provided for backward compatibility. A more robust implementation
-of the same functionality is available as `decode-path', which see."
+of the same functionality is available as `split-path', which see."
(and cd-path
(let (cd-list (cd-start 0) cd-colon)
(setq cd-path (concat cd-path path-separator))
--- lisp/find-paths.el.orig Sat May 16 01:28:16 1998
+++ lisp/find-paths.el Sat May 16 01:28:27 1998
＠＠ -250,7 +250,7 ＠＠
Non-\"\" comonents are converted into directory form.
If DROP-EMPTIES is non-NIL, \"\" components are dropped from the output.
Otherwise, they are left alone."
- (let* ((components (decode-path string))
+ (let* ((components (split-path string))
(directories
(mapcar #'(lambda (component)
(if (string-equal "" component)
--- lisp/make-docfile.el.orig Sat May 16 01:28:56 1998
+++ lisp/make-docfile.el Sat May 16 01:29:09 1998
＠＠ -77,7 +77,7 ＠＠
;; Then process the list of Lisp files.
(define-function 'defalias 'define-function)
-(setq load-path (decode-path (getenv "EMACSBOOTSTRAPLOADPATH")))
+(setq load-path (split-path (getenv "EMACSBOOTSTRAPLOADPATH")))
;; Then process the autoloads
(setq autoload-file-name "auto-autoloads.elc")
＠＠ -90,7 +90,7 ＠＠
(setq
load-path
- (nconc load-path (decode-path (getenv "EMACSBOOTSTRAPLOADPATH"))))
+ (nconc load-path (split-path (getenv "EMACSBOOTSTRAPLOADPATH"))))
(let (preloaded-file-list)
(load (concat default-directory "../lisp/dumped-lisp.el"))
--- lisp/setup-paths.el.orig Sat May 16 01:29:18 1998
+++ lisp/setup-paths.el Sat May 16 01:29:20 1998
＠＠ -140,7 +140,7 ＠＠
(packages-find-package-exec-path last-packages)
(let ((emacspath-envval (getenv "EMACSPATH")))
(and emacspath-envval
- (decode-path emacspath-envval)))
+ (split-path emacspath-envval)))
(and exec-directory
(list exec-directory))))
--- lisp/update-elc.el.orig Sat May 16 01:29:28 1998
+++ lisp/update-elc.el Sat May 16 01:29:29 1998
＠＠ -64,7 +64,7 ＠＠
(define-function 'defalias 'define-function)
-(setq load-path (decode-path (getenv "EMACSBOOTSTRAPLOADPATH")))
+(setq load-path (split-path (getenv "EMACSBOOTSTRAPLOADPATH")))
(load "find-paths.el")
(load "packages.el")
--- lisp/loadup.el.orig Sat May 16 02:03:14 1998
+++ lisp/loadup.el Sat May 16 02:03:27 1998
＠＠ -47,7 +47,7 ＠＠
(call-with-condition-handler 'really-early-error-handler
#'(lambda ()
;; message not defined yet ...
- (setq load-path (decode-path (getenv "EMACSBOOTSTRAPLOADPATH")))
+ (setq load-path (split-path (getenv "EMACSBOOTSTRAPLOADPATH")))
(external-debugging-output (format "\nUsing load-path %s" load-path))
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
The meta-Turing test counts a thing as intelligent if it seeks to
devise and apply Turing tests to objects of its own creation.
- 1 participants
- 0 comments
Still having problems building for DU 4.0
26 years, 6 months
Kevin Oberman
Kevin Oberman
Still DU4.0D on an a 500au Personal Workstation built with X11R6, cc,
Motif, CDE, and xpm.
Thanks to Oliver Graf I am now trying to build b40-pre4 in which
frame-x now compiles (and several other compilation warnings
disappeared), but still no-go.
The compile (using cc) is pretty clean, only giving 5 warnings (these
are appended to this message) and no errors, but the link fails with
two unresolved symbols which seem to be from the unexalpha.c code,
"edata" and "etext".
Here is the log of the build attempt:
make[1]: Entering directory `/home/oberman/utils/xemacs-21.0-b39/src'
cc -O2 -std1 -L/usr/ccs/lib -L/usr/dt/lib -o temacs abbrev.o alloc.o blocktype.o buffer.o bytecode.o callint.o callproc.o casefiddle.o casetab.o chartab.o cmdloop.o cmds.o console.o console-stream.o data.o device.o dired.o doc.o doprnt.o dynarr.o editfns.o elhash.o emacs.o eval.o events.o debug.o unexalpha.o tooltalk.o dragdrop.o menubar.o scrollbar.o dialog.o toolbar.o gui.o menubar-x.o scrollbar-x.o dialog-x.o toolbar-x.o gui-x.o realpath.o console-tty.o device-tty.o event-tty.o frame-tty.o objects-tty.o redisplay-tty.o cm.o terminfo.o event-unixoid.o database.o sysdll.o dll.o process-unix.o event-stream.o extents.o faces.o fileio.o filemode.o floatfns.o fns.o font-lock.o frame.o general.o getloadavg.o glyphs.o glyphs-eimage.o hash.o imgproc.o indent.o insdel.o intl.o keymap.o line-number.o lread.o lstream.o macros.o marker.o md5.o minibuf.o objects.o opaque.o print.o process.o profile.o pure.o rangetab.o redisplay.o redisplay-output.o regex.o search.o signal.o sound!
.o specifier.o strftime.o symbols.o syntax.o sysdep.o undo.o balloon_help.o balloon-x.o console-x.o device-x.o event-Xt.o frame-x.o glyphs-x.o objects-x.o redisplay-x.o xgccache.o xselect.o widget.o window.o lastfile.o ralloc.o EmacsFrame.o EmacsShell.o TopLevelEmacsShell.o TransientEmacsShell.o EmacsManager.o offix.o ../lwlib/liblw.a -ldnet_stub -lXm -ltiff -lpng -ljpeg -lz -lXpm -lDtSvc -ltt -lXmu -lXt -lXext -lX11 -lSM -lICE -ldb -lcurses -lm -lbsd
ld:
Unresolved:
etext
edata
make[1]: *** [temacs] Error 1
make[1]: Leaving directory `/home/oberman/utils/xemacs-21.0-b39/src'
make: *** [src] Error 2
Thanks for any help!
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman(a)es.net Phone: +1 510 486-8634
Warings received during the build:
cc -O2 -std1 -Demacs -I../src -DHAVE_CONFIG_H -I/usr/local/include -D_BSD /usr/users/oberman/utils/xemacs-21.0-b39/lib-src/movemail.c /usr/users/oberman/utils/xemacs-21.0-b39/lib-src/pop.c -L/usr/ccs/lib -ldb -lcurses -lm -lbsd -o movemail
/usr/users/oberman/utils/xemacs-21.0-b39/lib-src/movemail.c:
cc: Warning: /usr/users/oberman/utils/xemacs-21.0-b39/lib-src/movemail.c, line 394: In this statement, the referenced type of the pointer value "&status" is "int", which is not compatible with "union wait".
wait (&status);
--^
/usr/users/oberman/utils/xemacs-21.0-b39/lib-src/pop.c:
cc -c -O2 -std1 -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -D_BSD -I/usr/dt/include cmdloop.c
cc: Warning: cmdloop.c, line 507: Non-void function "Fcommand_loop_1" does not contain a return statement.
DEFUN ("command-loop-1", Fcommand_loop_1, 0, 0, 0, /*
^
cc -c -O2 -std1 -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -D_BSD -I/usr/dt/include emacs.c
cc: Warning: emacs.c, line 1983: Strict ANSI C extension: The declaration of the "main" function has more than two parameters.
int
^
cc: Warning: emacs.c, line 2498: In this statement, the referenced type of the pointer value "gccida_ptr_out" is "unsigned char", which is not compatible with "const char".
GET_C_CHARPTR_INT_FILENAME_DATA_ALLOCA (path, path);
--^
cc -c -O2 -std1 -Demacs -I. -DHAVE_CONFIG_H -I/usr/local/include -D_BSD -I/usr/dt/include event-Xt.c
cc: Warning: event-Xt.c, line 1203: In the initializer for hurl, the referenced type of the pointer value "data" is "unsigned char", which is not compatible with "const char".
char *hurl = dnd_url_hexify_string (data, "file:");
-------------------------------^
- 1 participants
- 0 comments
Re: [Doc-bug] zap-to-char - including or up-to?
26 years, 6 months
SL Baur
SL Baur
acs <acs(a)acm.org> writes:
> How hard is it to type:
> 'M-z x' followed immediately by another 'x' if you want to restore
> the final, deleted character.
It adds cruft to the undo ring?
> I've learned to live with this, as have nearly all the other lusers
> of {FSF,X}Emacs 19. This strikes me as the kind of arbitrary change
> which always draws howls of protest.
There are some things (colors immediately come to mind) that we're
going to get flamed about no matter what we do.
- 1 participants
- 0 comments
Re: [Doc-bug] zap-to-char - including or up-to?
26 years, 6 months
Hrvoje Niksic
Hrvoje Niksic
Martin Buchholz <martin(a)xemacs.org> writes:
> Hrvoje> Not without a user poll.
>
> Speaking strictly as a user, (...)
No, I meant a full-featured official poll on comp.emacs.xemacs. We
shouldn't do such gratiotous changes unless we *really* have the
support of majority.
Someone should also ask Stallman why he made the change. Maybe there
was a good reason that we are not aware of.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Then... his face does a complete change of expression. It goes from
a "Vengeance is mine" expression, to a "What the fuck" blank look.
- 1 participants
- 0 comments
Re: NEWS update
26 years, 6 months
Hrvoje Niksic
Hrvoje Niksic
Martin Buchholz <martin(a)xemacs.org> writes:
> >>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes:
>
> Hrvoje> In fact, the best thing would be if a `gdb-highlight-mode' existed as
> Hrvoje> a minor mode, so we could simply autoload `add-minor-mode'. However,
> Hrvoje> I don't feel like changing Jamie's code right now. I don't want to
> Hrvoje> die young.
>
> Changing gdb-highlight is the correct thing to do. Also, Jamie's
> bark is worse than his bullet.
Feel free to change gdb-highlight. I'll update the NEWS entry.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Idle RAM is the Devil's playground.
- 1 participants
- 0 comments
Re: NEWS update
26 years, 6 months
Hrvoje Niksic
Hrvoje Niksic
SL Baur <steve(a)xemacs.org> writes:
> >> also, using anonymous functions in hooks is a bad idea since they
> >> are hard to remove. binding a key to an anonymous (and
> >> interactive) function is equally a bad idea.
>
> One point being you can't just evaluate the hook variable in
> *scratch*, modify something and reevalute it -- it'll puke on the
> un(lisp)readable bytecode object.
Set `print-readably' to t if you want to do such things.
> > It does, but in the specific NEWS example it looks better to use
> > the anonymous function than to cons up a new function only for
> > that purpose.
>
> Yup. Just what is gdb-highlight doing in NEWS anyway? Or do I want
> to know?
It wasn't distributed with 20.4, was it? What more explanation is
needed?
Cool features are worth nil if they are not announced. And
gdb-highlight is *way* cool.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
* Q: What is an experienced Emacs user?
* A: A person who wishes that the terminal had pedals.
- 1 participants
- 0 comments
Re: enable-clash-detection
26 years, 6 months
Hrvoje Niksic
Hrvoje Niksic
Martin Buchholz <martin(a)xemacs.org> writes:
> I vote for experimentally turning clash-detection back on by
> default, with the new FSF-Emacs-compatible implementation, early in
> the 21.1 development cycle.
Yes.
--
Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
By any chance, have you seen a summoned 9th order fire elemental
wandering around? No? Oh.. Tell me if you do.
- 1 participants
- 0 comments