GPLv3|L8R -- Status report - ready for inspection?
6 years, 10 months
Mats Lidell
Mats Lidell
Hi,
Here comes yet another status report from the project of converting to
GPLv3 or later.
There are two lists of files below. The first list contains all files
that are in an undecided state. Please inspect: Do we need to do anything
with them. If so what?
The second list contains all files that we can leave untouched and the
reason for that. Please inspect: Are all reasons OK and correct?
Are we getting close to the were an inspection of the xemacs-gplv3
repository could be performed? With the intent that it that is OK we
could merge back to trunk and go GPLv3 or later?
----------------------------------------------------------------------
"CHANGES-beta"
"ChangeLog"
"PROBLEMS"
"README"
"README.GPLv3"
"etc/ChangeLog"
"etc/Emacs.ad"
"etc/InstallGuide"
"etc/NEWS"
"etc/ONEWS"
"etc/OONEWS"
"etc/README"
"etc/editclient.sh"
"etc/emacskeys.sco"
"etc/emacsstrs.sco"
"etc/gtkrc"
"etc/package-index.LATEST.gpg"
"etc/sample.Xresources"
"etc/xemacs.1"
"lib-src/ChangeLog"
"lib-src/README"
"lisp/ChangeLog"
"lisp/README"
"lisp/mule/mule-locale.txt"
"man/ChangeLog"
"man/README"
"modules/ChangeLog"
"modules/base64/Makefile"
"modules/common/configure-post.ac"
"modules/common/configure-pre.ac"
"modules/zlib/Makefile"
"nt/ChangeLog"
"nt/Emacs.ad.h"
"nt/Installation.el"
"nt/README"
"nt/Win32.cf"
"nt/lisp.ico"
"nt/site.def"
"nt/xemacs.dsp"
"nt/xemacs.dsw"
"src/ChangeLog"
"src/README"
"src/README.kkcc"
"src/m/README"
"src/s/README"
"src/s/freebsd.h"
"src/s/irix6-0.h"
"src/s/netbsd.h"
"src/s/sol2.h"
"tests/ChangeLog"
"tests/Dnd/README"
"tests/automated/README"
"version.sh.in"
----------------------------------------------------------------------
These files below are the files that we might be able to leave as
they are. The reason for why they need not to be changed is listed
after each file: (Some reasons are taken verbatim from private
communication or the "GPL version 3 source survey")
----------------------------------------------------------------------
"INSTALL" -> old FSF Documentation license
"config.guess" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"config.sub" -> Part of config which is still GPLv2 or later. See "http://savannah.gnu.org/projects/config"
"etc/ETAGS.ChangeLog" -> BSD and GPL v2 or later
"etc/VEGETABLES" -> Not copyrightable.
"etc/XKeysymDB" -> MIT
"etc/ctags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/custom/example-themes/ex-custom-file" -> Generated(!?) or GPL V2 or later?
"etc/etags.1" -> Part of the etags distribution, which is not part of XEmacs.
"etc/gnuattach.1" -> simple man link to gnuserv.1
"etc/gnuclient.1" -> simple man link to gnuserv.1
"etc/gnudoit.1" -> simple man link to gnuserv.1
"etc/refcard.ps.gz" -> Generated from refcard..tex
"etc/sample.Xdefaults" -> It is deprecated, so it can be removed but is only a three line reference to .Xresources
"etc/xemacs-X.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"info/dir" -> Generated(?)
"install-sh" -> MIT-style "no advertising" license
"lib-src/b2m.c" -> This is the version from GNU Emacs, so should be OK.
"lib-src/config.values.in" -> Generated.
"lib-src/emacs.csh" -> I don't think this even works with XEmacs ("emacsclient"), so I believe we can just delete it.
"lib-src/insert-data-in-exec.c" -> Compatible license.
"lib-src/mmencode.c" -> Compatible license.
"lisp/dump-paths.el" -> Empty file. Not copyrightable.
"lisp/term/bobcat.el" -> Emacs version has no explicit license declaration
"lisp/term/vt102.el" -> Emacs version has no explicit license declaration
"lisp/term/vt125.el" -> Emacs version has no explicit license declaration
"lisp/term/vt200.el" -> Emacs version has no explicit license declaration
"lisp/term/vt201.el" -> Emacs version has no explicit license declaration
"lisp/term/vt220.el" -> Emacs version has no explicit license declaration
"lisp/term/vt240.el" -> Emacs version has no explicit license declaration
"lisp/term/vt300.el" -> Emacs version has no explicit license declaration
"lisp/term/vt320.el" -> Emacs version has no explicit license declaration
"lisp/term/vt400.el" -> Emacs version has no explicit license declaration
"lisp/term/vt420.el" -> Emacs version has no explicit license declaration
"lock/.precious" -> Not copyrightable.
"modules/canna/install-sh" -> MIT
"modules/ldap/install-sh" -> MIT
"modules/postgresql/install-sh" -> MIT
"modules/sample/external/install-sh" -> MIT
"modules/sample/internal/install-sh" -> MIT
"move-if-change" -> Identical to GPLv3 or later Emacs version
"nt/Xmd.patch" -> GPLv2 or later but only a few lines
"nt/file.ico" -> MIT
"nt/minitar.c" -> Public domain
"nt/paths.h" -> Generated
"nt/xemacs.ico" -> GPLv2 or later but there is not meta data for the file where this can be documented.
"src/alloca.c" -> Public domain.
"src/depend" -> Generated
"src/emacs-marshals.c" -> Generated.
"src/emacs-widget-accessors.c" -> Generated.
"src/intl-auto-encap-win32.c" -> Generated.
"src/intl-auto-encap-win32.h" -> Generated.
"src/libsst.c" -> Compatible license.
"src/libsst.h" -> Compatible license.
"src/libst.h" -> Compatible copyright.
"src/linuxplay.c" -> Compatible license. (MIT-like)
"src/miscplay.c" -> Compatible license. (MIT-like)
"src/miscplay.h" -> Compatible license. (MIT-like)
"src/nas.c" -> Compatible license. (MIT-like)
"src/paths.h.in" -> Generated.
"src/s/openbsd.h" -> Too short. (< 10 lines)
"src/s/usg5-4-2.h" -> Too short. (< 10 lines)
"src/sunplay.c" -> Compatible copyright.
"tests/gtk/UNIMPLEMENTED" -> Does notes need a license?
"tests/tooltalk/beeps.el" -> Too short. (< 10 lines)
----------------------------------------------------------------------
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 4 participants
- 3 comments
Crash running Cygwin bash shell under XEmacs
11 years, 8 months
Mike Alexander
Mike Alexander
I had a need to run something on my Windows machine today which
required a newer version of Cygwin than the ancient one that was
installed there. After I upgraded to the current version (1.7.9) I
can't start a shell in XEmacs (via M-X shell) using Cygwin's version of
bash. When I try to do so I get
Process bash.exe exited abnormally with code 35584
3 [sig] bash 1168 exception::handle: Exception:
STATUS_ACCESS_VIOLATION
1556 [sig] bash 1168 open_stackdumpfile: Dumping stack trace to
bash.exe.stackdump
The stack dump is uninteresting except that the crash happens at offset
0x169220 in cygwin1.dll. It appears that this crash happens very early
on, before it's read /etc/profile. I see that I also have similar
stack dumps from other programs (find.exe and xargs.exe) in the XEmacs
directory all exactly the same.
I installed the latest Windows version of XEmacs from the installer at
<http://ftp.xemacs.org/pub/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21...>
and tried starting it with --vanilla. This didn't make any difference.
I also did a clean install of Cygwin 1.7.9 in case there was any crud
left around from the old version. This also didn't help. I'm running
on an old Dell with Windows XP Professional SP3. Perhaps that's the
problem. I probably should install Windows on my Mac under one of the
emulators, but that's more than I want to get into right now.
I've Googled around a bit and although others have seen this problem,
none of the solutions (mostly involving changing ownership of Cygwin
files and running rebaseall) did any good. The bash shell runs fine
when I start it using the .bat file installed by Cygwin, so it's
basically working, but it won't run in an XEmacs shell window.
Has anyone else seen this or know how to fix it? This little episode
reminds me why I avoid using Windows, but sometimes it's necessary.
Mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 5 participants
- 5 comments
Re: The future of XEmacs
11 years, 8 months
steven Mitchell
steven Mitchell
I understand the need for updated packages that help people work in
different ways.
There are also things within XEmacs that need updating. I have 2 things
that poke at me when I am working within XEmacs.
First is that some features are in the documentation, but do not
actually exist when you go to program them.
An example is in dialogs, that only 1 of 4 types of dialog boxes that
are in the documentation actually exist in code.
You can call the function name from your lisp code, and it says "not
implemented".
There are other examples of this too.
Second is that features that exist in the manuals and exist in the
program, but you cannot use them in code and submit it for inclusion in
XEmacs because that feature doesn't exist in the previous stable version
(21.4) (and never will).
An example is when I tried to implement a behavior, which is in the
manual, and the code is there--it works. But is not compatible with a
10 year old previous version.
There are other places where behaviors can be implemented to good
effect, in the menu system, that would solve some usability problems
that some users report, but they cannot be used at this time. An
example: it is a way to implement (and turn off) CUA provisions (a "new"
menu item, and similarly a "close" menu item for example), while keeping
the entire rest of the menu intact, so anyone who wants the CUA items
can turn on a behavior, and the rest can leave it off, and no harm done.
The real problem is no body or no thing, except the distribution cycle
has stretched to over 10 years old now, and it forces everybody to write
code (to be submitted to XEmacs) that doesn't use the new features of
21.5. If I recall correctly, behaviors existed 10 years ago, but still
cannot be used.
What obstacles are in the way of incrementing the version number of a
stable release so we can use new features?
Steve Mitchell
Forgive me if I have some terminology of version numbers or the number
of years wrong here, I think it has actually been 11 years since
behaviors were implemented, going by the date on the file.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 10 participants
- 49 comments
another redisplay crash
11 years, 8 months
Charles Waldman
Charles Waldman
Hi XEmacs team:
I'm running
XEmacs 21.5 (beta31) "ginger" [Lucid] (x86_64-pc-linux) of Thu Mar 22 2012 on x201
I've gotten the same crash a few times in the last few days. I believe
that a patch for this exact problem has been submitted (not by me).
What would it take to get this patch applied?
Thanks,
- Charles
(gdb) where
#0 0x00007f8a58d4ebc7 in kill () from /lib64/libc.so.6
#1 0x00000000004c9c64 in fatal_error_signal (sig=6) at emacs.c:3896
#2 <signal handler called>
#3 0x00007f8a58d4ea05 in raise () from /lib64/libc.so.6
#4 0x00007f8a58d4fd05 in abort () from /lib64/libc.so.6
#5 0x00000000004c9905 in really_abort () at emacs.c:4792
#6 assert_failed (file=<optimized out>, line=<optimized out>, expr=<optimized out>) at emacs.c:4089
#7 0x0000000000689675 in Dynarr_verify_pos_atp (line=9179, file=0x794f77 "redisplay.c", pos=-1,
d=<optimized out>) at array.h:202
#8 pixel_to_glyph_translation (f=0x31a6268, x_coord=628, y_coord=504, col=0x7fff64bbebfc,
row=<optimized out>, obj_x=0x7fff64bbebf4, obj_y=0x7fff64bbebf0, w=0x7fff64bbebe8,
charpos=0x7fff64bbebe0, closest=0x7fff64bbebd8, modeline_closest=0x7fff64bbebd0, obj1=0x7fff64bbebc8,
obj2=0x7fff64bbebc0) at redisplay.c:9179
#9 0x00000000004e1544 in event_pixel_translation (event=<optimized out>, char_x=0x0, char_y=0x0, obj_x=0x0,
obj_y=0x0, w=0x7fff64bbec78, bufp=0x0, closest=0x0, modeline_closest=0x0, obj1=0x0, obj2=0x0)
at events.c:2116
#10 0x00000000004e1c44 in Fevent_window (event=<optimized out>) at events.c:2249
#11 0x00000000004d8195 in Ffuncall (nargs=2, args=<optimized out>) at eval.c:4103
#12 0x000000000047df38 in execute_optimized_program (
program=0x3989470 "\306\r!\256\003\307 \036>\310\r!\036A\311\r!\211\034\255\004\312\r!\211\030\255\005\313\314\f\"\036=\f\255\b\b?\255\004\315\r!\211\032\253\b\316\n\f\317#\256\n\b\255\a\316\b\016=\320#\036\067\321\r!\211\036?\255\t\322\016?!\255\003\016?\211\031\253\n\323\t\324\"\253\004\t\256\024\n\253\b\316\n\f\324#\256\n\b\255\a\316\b\016=\324#\211\036＠\255\f\322\016＠!\255\006\323\016＠\324\"\036$\325\r!\036\070\t\253\n\323\t\320\"\253\004\t\256\"\016\070\253\v\326\016\070!\253\005\016\070\256\024\n\253\b\316\n\f\320#\256\n\b\255\a\316\b\016=\320#\033\327\r!\253\004*1\016\067\254\004\t\253\004j"..., program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x3810010) at bytecode.c:926
#13 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#14 Ffuncall (nargs=58785809, args=<optimized out>) at eval.c:4152
#15 0x00000000004d8f1c in call1 (fn=<optimized out>, arg0=<optimized out>) at eval.c:5371
#16 0x00000000004f2704 in execute_internal_event (event=42678776) at event-stream.c:2980
#17 0x00000000004f2b6a in Fsit_for (seconds=<optimized out>, nodisplay=56658704) at event-stream.c:2888
#18 0x000000000048fb1d in Fcommand_loop_1 () at cmdloop.c:616
#19 0x000000000048fb86 in command_loop_1 (unused_dummy=<optimized out>) at cmdloop.c:528
#20 0x00000000004d4100 in condition_case_1 (handlers=<optimized out>, bfun=0x48fb50 <command_loop_1>,
barg=56658704, hfun=0x48fd10 <cmd_error>, harg=56658704) at eval.c:2114
#21 0x000000000048fce0 in command_loop_3 () at cmdloop.c:285
#22 command_loop_2 (unused_dummy=<optimized out>) at cmdloop.c:298
#23 0x0000000000490068 in call_command_loop (catch_errors=<optimized out>) at cmdloop.c:359
#24 0x0000000000642bfc in Fread_minibuffer_internal (prompt=<optimized out>) at minibuf.c:190
#25 0x00000000004d8195 in Ffuncall (nargs=2, args=<optimized out>) at eval.c:4103
#26 0x000000000047df38 in execute_optimized_program (
program=0x7fff64bbf540 "\303 \304 V\253\nI\031\030\306\n!*\207\306\n!\207",
program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x3822208) at bytecode.c:926
#27 0x0000000000480e7d in Fbyte_code (instructions=59461256, constants=58860024, stack_depth=5)
at bytecode.c:2775
#28 0x00000000004dafa9 in Feval (form=56980416) at eval.c:3849
#29 0x00000000004d1a09 in internal_catch (
tag=<error reading variable: Cannot access memory at address 0x2036>, func=0x4da410 <Feval>,
arg=56980416, threw=0x0, thrown_tag=0x0, backtrace_before_throw=0x0) at eval.c:1694
#30 0x0000000000478cb1 in execute_rare_opcode (stack_ptr=0x7fff64bbf978, stack_beg=0x7fff64bbf970,
stack_end=0x7fff64bbf9b0, unused_program_ptr=<optimized out>, opcode=<optimized out>) at bytecode.c:1504
#31 0x000000000047ed43 in execute_optimized_program (
program=0x37f07f0 "\016K\254\022\306 \307V\253\f\310 \311 a\253\005\312\313!\210\016A\253\021\016A\307V\253\v\306 \016AY\253\004\314 \210\r\253\035\r9\253\r\315\r!\254\024\312\316\r\"\210\252\r\315\r＠!\254\a\312\316\r＠\"\210\317 \253\t\320\321\322\016L!\"\210\016B\036C\310 \036D\323 \036M\311 \032\324\325\326\306 \"!\031\327\n!\211\036E\323 a?\255\005\330\016E!\036N\330 \036O\b\036PN\332\t!q\210\016C\026B\333\334!\210\335\026\034\333\336!\210\333\337!\210\333\340!\210\341\026\036\342\026\037\016F\253\025\333\343!\210\016#\254\004\344\026#\333\345!\210\346\345\347\"\210\350\n\t\"\210\351\n!"..., program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x3864010) at bytecode.c:811
#32 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#33 Ffuncall (nargs=59129873, args=<optimized out>) at eval.c:4152
#34 0x000000000047df38 in execute_optimized_program (
program=0x2808058 "\n\t\v\306a?\255\002\306É\035\030\036\n\036\v\036\f\310\016\r\016\016\v\254\005\016\017\252\003\016\020\307\016\021\307\f&\a\211\025X\253\a\f\253\004\f\252\002\r-\207",
program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x384a5b0) at bytecode.c:926
#35 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#36 Ffuncall (nargs=59024817, args=<optimized out>) at eval.c:4152
#37 0x000000000047df38 in execute_optimized_program (
program=0x3072db0 "\303\304\n\t\305\306\307\310\b&\a!\207", program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x38371c8) at bytecode.c:926
#38 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#39 Ffuncall (nargs=58945993, args=<optimized out>) at eval.c:4152
#40 0x000000000047df38 in execute_optimized_program (
program=0x32bb0c8 "\r\035\306\r\307a\253\004*H\r\311k\253\004ª＠\313\r\211\250\254\f\211\247\253\004!\252\b\210\210\252\f\210\210+\a\315\316\r\"\252$\r:\253\037\313\r＠\211\250\254\f\211\247\253\004!\252\b\210\210\252\r\210\210+\b\315\316\r＠\"\252\002\317!\024)\t\253Kt\253H\320\f!\f\032\033\321\f\314\"\210\v\255\070\b\254\023\322 \323 a\253\a\324 pa\253\006\325 \210\252\004\326 \210\327\330!\255\033\331\332\315\vA\253\004ê\002\334\n\335\v!#\"\210\327\016\037!\210\336\332!*\207\321\f\314\"\207", program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x3802560) at bytecode.c:926
#41 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#42 Ffuncall (nargs=58729825, args=<optimized out>) at eval.c:4152
#43 0x0000000000484c1e in Fcall_interactively (function=56392752, record_flag=56658704, keys=<optimized out>)
at callint.c:973
#44 0x00000000004d9a11 in Fcommand_execute (cmd=56392752, record_flag=56658704, keys=56658704) at eval.c:3307
#45 0x00000000004f2f26 in execute_command_event (command_builder=0x27ce9f8, event=94606704)
at event-stream.c:4269
#46 0x00000000004f397f in Fdispatch_event (event=<optimized out>) at event-stream.c:4652
#47 0x000000000048fa90 in Fcommand_loop_1 () at cmdloop.c:623
#48 0x000000000048fb86 in command_loop_1 (unused_dummy=<optimized out>) at cmdloop.c:528
#49 0x00000000004d4100 in condition_case_1 (handlers=<optimized out>, bfun=0x48fb50 <command_loop_1>,
barg=56658704, hfun=0x48fd10 <cmd_error>, harg=56658704) at eval.c:2114
#50 0x000000000048fce0 in command_loop_3 () at cmdloop.c:285
#51 command_loop_2 (unused_dummy=<optimized out>) at cmdloop.c:298
#52 0x0000000000490068 in call_command_loop (catch_errors=<optimized out>) at cmdloop.c:359
#53 0x0000000000642bfc in Fread_minibuffer_internal (prompt=<optimized out>) at minibuf.c:190
#54 0x00000000004d8195 in Ffuncall (nargs=2, args=<optimized out>) at eval.c:4103
#55 0x000000000047df38 in execute_optimized_program (
program=0x7fff64bc0a00 "\303 \304 V\253\nI\031\030\306\n!*\207\306\n!\207",
program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x3822208) at bytecode.c:926
#56 0x0000000000480e7d in Fbyte_code (instructions=59461256, constants=58860024, stack_depth=5)
at bytecode.c:2775
#57 0x00000000004dafa9 in Feval (form=56980416) at eval.c:3849
#58 0x00000000004d1a09 in internal_catch (
tag=<error reading variable: Cannot access memory at address 0x2036>, func=0x4da410 <Feval>,
arg=56980416, threw=0x0, thrown_tag=0x0, backtrace_before_throw=0x0) at eval.c:1694
#59 0x0000000000478cb1 in execute_rare_opcode (stack_ptr=0x7fff64bc0e38, stack_beg=0x7fff64bc0e30,
stack_end=0x7fff64bc0e70, unused_program_ptr=<optimized out>, opcode=<optimized out>) at bytecode.c:1504
#60 0x000000000047ed43 in execute_optimized_program (
program=0x37f07f0 "\016K\254\022\306 \307V\253\f\310 \311 a\253\005\312\313!\210\016A\253\021\016A\307V\253\v\306 \016AY\253\004\314 \210\r\253\035\r9\253\r\315\r!\254\024\312\316\r\"\210\252\r\315\r＠!\254\a\312\316\r＠\"\210\317 \253\t\320\321\322\016L!\"\210\016B\036C\310 \036D\323 \036M\311 \032\324\325\326\306 \"!\031\327\n!\211\036E\323 a?\255\005\330\016E!\036N\330 \036O\b\036PN\332\t!q\210\016C\026B\333\334!\210\335\026\034\333\336!\210\333\337!\210\333\340!\210\341\026\036\342\026\037\016F\253\025\333\343!\210\016#\254\004\344\026#\333\345!\210\346\345\347\"\210\350\n\t\"\210\351\n!"..., program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x3864010) at bytecode.c:811
#61 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#62 Ffuncall (nargs=59129873, args=<optimized out>) at eval.c:4152
#63 0x000000000047df38 in execute_optimized_program (
program=0x2808058 "\n\t\v\306a?\255\002\306É\035\030\036\n\036\v\036\f\310\016\r\016\016\v\254\005\016\017\252\003\016\020\307\016\021\307\f&\a\211\025X\253\a\f\253\004\f\252\002\r-\207",
program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x384a5b0) at bytecode.c:926
#64 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#65 Ffuncall (nargs=59024817, args=<optimized out>) at eval.c:4152
#66 0x000000000047df38 in execute_optimized_program (
program=0x3072db0 "\303\304\n\t\305\306\307\310\b&\a!\207", program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x38371c8) at bytecode.c:926
#67 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#68 Ffuncall (nargs=58945993, args=<optimized out>) at eval.c:4152
#69 0x000000000047df38 in execute_optimized_program (
program=0x32bb0c8 "\r\035\306\r\307a\253\004*H\r\311k\253\004ª＠\313\r\211\250\254\f\211\247\253\004!\252\b\210\210\252\f\210\210+\a\315\316\r\"\252$\r:\253\037\313\r＠\211\250\254\f\211\247\253\004!\252\b\210\210\252\r\210\210+\b\315\316\r＠\"\252\002\317!\024)\t\253Kt\253H\320\f!\f\032\033\321\f\314\"\210\v\255\070\b\254\023\322 \323 a\253\a\324 pa\253\006\325 \210\252\004\326 \210\327\330!\255\033\331\332\315\vA\253\004ê\002\334\n\335\v!#\"\210\327\016\037!\210\336\332!*\207\321\f\314\"\207", program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x3802560) at bytecode.c:926
#70 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#71 Ffuncall (nargs=58729825, args=<optimized out>) at eval.c:4152
#72 0x0000000000484c1e in Fcall_interactively (function=56392752, record_flag=56658704, keys=<optimized out>)
at callint.c:973
#73 0x00000000004d9a11 in Fcommand_execute (cmd=56392752, record_flag=56658704, keys=56658704) at eval.c:3307
#74 0x00000000004f2f26 in execute_command_event (command_builder=0x27ce9f8, event=92698664)
at event-stream.c:4269
#75 0x00000000004f397f in Fdispatch_event (event=<optimized out>) at event-stream.c:4652
#76 0x000000000048fa90 in Fcommand_loop_1 () at cmdloop.c:623
#77 0x000000000048fb86 in command_loop_1 (unused_dummy=<optimized out>) at cmdloop.c:528
#78 0x00000000004d4100 in condition_case_1 (handlers=<optimized out>, bfun=0x48fb50 <command_loop_1>,
barg=56658704, hfun=0x48fd10 <cmd_error>, harg=56658704) at eval.c:2114
#79 0x000000000048fce0 in command_loop_3 () at cmdloop.c:285
#80 command_loop_2 (unused_dummy=<optimized out>) at cmdloop.c:298
#81 0x0000000000490068 in call_command_loop (catch_errors=<optimized out>) at cmdloop.c:359
#82 0x0000000000642bfc in Fread_minibuffer_internal (prompt=<optimized out>) at minibuf.c:190
#83 0x00000000004d8195 in Ffuncall (nargs=2, args=<optimized out>) at eval.c:4103
#84 0x000000000047df38 in execute_optimized_program (
program=0x7fff64bc1ec0 "\303 \304 V\253\nI\031\030\306\n!*\207\306\n!\207",
program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x3822208) at bytecode.c:926
#85 0x0000000000480e7d in Fbyte_code (instructions=59461256, constants=58860024, stack_depth=5)
at bytecode.c:2775
#86 0x00000000004dafa9 in Feval (form=56980416) at eval.c:3849
#87 0x00000000004d1a09 in internal_catch (
tag=<error reading variable: Cannot access memory at address 0x2036>, func=0x4da410 <Feval>,
arg=56980416, threw=0x0, thrown_tag=0x0, backtrace_before_throw=0x0) at eval.c:1694
#88 0x0000000000478cb1 in execute_rare_opcode (stack_ptr=0x7fff64bc22f8, stack_beg=0x7fff64bc22f0,
stack_end=0x7fff64bc2330, unused_program_ptr=<optimized out>, opcode=<optimized out>) at bytecode.c:1504
#89 0x000000000047ed43 in execute_optimized_program (
program=0x37f07f0 "\016K\254\022\306 \307V\253\f\310 \311 a\253\005\312\313!\210\016A\253\021\016A\307V\253\v\306 \016AY\253\004\314 \210\r\253\035\r9\253\r\315\r!\254\024\312\316\r\"\210\252\r\315\r＠!\254\a\312\316\r＠\"\210\317 \253\t\320\321\322\016L!\"\210\016B\036C\310 \036D\323 \036M\311 \032\324\325\326\306 \"!\031\327\n!\211\036E\323 a?\255\005\330\016E!\036N\330 \036O\b\036PN\332\t!q\210\016C\026B\333\334!\210\335\026\034\333\336!\210\333\337!\210\333\340!\210\341\026\036\342\026\037\016F\253\025\333\343!\210\016#\254\004\344\026#\333\345!\210\346\345\347\"\210\350\n\t\"\210\351\n!"..., program_length=<optimized out>,
stack_depth=<optimized out>, constants_data=0x3864010) at bytecode.c:811
#90 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#91 Ffuncall (nargs=59129873, args=<optimized out>) at eval.c:4152
#92 0x000000000047df38 in execute_optimized_program (
program=0x308f510 "\r\254\004\016\017\025\306\r\307\"\025\016\020\254\a\v\254\004*\021\v\253\v\311\r\vP!\rGB\252\004\311\r!\034\016\021\r\b\307a?\255\002\307\312\036\022\036\023\036\024\036\025\313\016\026\f\b\254\005\016\027\252\003\016\030\312\016\031\312\n&\a,\211\031\254\006\314\315!\252\027\n\253\021\t\f:\253\005\f＠\252\002\fk\253\004\n\252\004\316\t!*\207", program_length=<optimized out>, stack_depth=<optimized out>,
constants_data=0x37f72b0) at bytecode.c:926
#93 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#94 Ffuncall (nargs=58684081, args=<optimized out>) at eval.c:4152
#95 0x000000000047df38 in execute_optimized_program (
program=0x3c75430 "\306 \253\006\307\310O\207\312\313\314\"\210\315\r\f\v\n\t\b\016\016&\a\207",
program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x385a340) at bytecode.c:926
#96 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#97 Ffuncall (nargs=59089729, args=<optimized out>) at eval.c:4152
#98 0x000000000047df38 in execute_optimized_program (
program=0x3178f60 "\306\307\v\256\002\310\n\f\t\256\025\r\253\n\311\312\r\f\"\313\"\256\t\b\255\006\311\016\r\313\"\016\016\r\314&\b\207", program_length=<optimized out>, stack_depth=<optimized out>,
constants_data=0x385a3c8) at bytecode.c:926
#99 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#100 Ffuncall (nargs=59089865, args=<optimized out>) at eval.c:4152
#101 0x000000000047df38 in execute_optimized_program (
program=0x39c64c0 "r\306 \253\005\306 q\210\307 \203", <incomplete sequence \310>,
program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x38129a0) at bytecode.c:926
#102 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#103 Ffuncall (nargs=58796449, args=<optimized out>) at eval.c:4152
#104 0x000000000047df38 in execute_optimized_program (
program=0x30874e0 "\305 \306 \307V\n\253\a\f\310a?\256\004\f\311s\032\031\211\033\253\b\f\312s\253\003\313\020\v\253\021\t\253\016\314 \253\n\315\316\317\320\314 \"\"\210\321 \210\v\255\t\f\322s\255\004É\020+\207", program_length=<optimized out>, stack_depth=<optimized out>, constants_data=0x3858550) at bytecode.c:926
#105 0x00000000004d824c in funcall_compiled_function (args=<optimized out>, nargs=<optimized out>,
fun=<optimized out>) at eval.c:3684
#106 Ffuncall (nargs=59082065, args=<optimized out>) at eval.c:4152
#107 0x0000000000484c1e in Fcall_interactively (function=56621264, record_flag=56658704,
keys=<optimized out>) at callint.c:973
#108 0x00000000004d9a11 in Fcommand_execute (cmd=56621264, record_flag=56658704, keys=56658704)
at eval.c:3307
#109 0x00000000004f2f26 in execute_command_event (command_builder=0x27ce9f8, event=69593128)
at event-stream.c:4269
#110 0x00000000004f397f in Fdispatch_event (event=<optimized out>) at event-stream.c:4652
#111 0x000000000048fa90 in Fcommand_loop_1 () at cmdloop.c:623
#112 0x000000000048fb86 in command_loop_1 (unused_dummy=<optimized out>) at cmdloop.c:528
#113 0x00000000004d4100 in condition_case_1 (handlers=<optimized out>, bfun=0x48fb50 <command_loop_1>,
barg=56658704, hfun=0x48fd10 <cmd_error>, harg=56658704) at eval.c:2114
#114 0x000000000048fce0 in command_loop_3 () at cmdloop.c:285
#115 command_loop_2 (unused_dummy=<optimized out>) at cmdloop.c:298
#116 0x00000000004d1a09 in internal_catch (
tag=<error reading variable: Cannot access memory at address 0x2036>, func=0x48fcb0 <command_loop_2>,
arg=56658704, threw=0x0, thrown_tag=0x0, backtrace_before_throw=0x0) at eval.c:1694
#117 0x0000000000490038 in initial_command_loop (load_me=<optimized out>) at cmdloop.c:336
#118 0x00000000004cd231 in xemacs_21_5_b31_x86_64_pc_linux (argc=2, argv=0x7fff64bc38e8,
unused_envp=<optimized out>, restart=0) at emacs.c:2738
#119 0x00000000004cde21 in main (argc=2, argv=0x7fff64bc38e8, unused_envp=<optimized out>) at emacs.c:3186
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 5 participants
- 7 comments
GNU Emacs function recenter-top-bottom
11 years, 8 months
The XEmacs Package Smoketest
The XEmacs Package Smoketest
Hi,
While doing an overhaul of the swedish translation of the GNU Emacs
Tutorial for the upcoming 24.1 release I spotted a thing that we don't
have but GNU Emacs has (introduced earlier than 24.1) and that is
recenter-top-bottom which is bound to C-l. It works like recenter
except that successive call place the point according to the cycling
order defined by `recenter-positions' (default being middle top
bottom)
What do you say? Should we get it? And if we do then shall we bind it
to C-l as default?
I tried to sync and the basic functionality is easy to get in
place. However that code revealed further differences. GNU Emacs has
the property "scroll-margin". When cursor gets within scroll-margin
number of lines from the top or bottom of the window will be
recentered. Interesting for us?
GNU Emacs also have the feature header-line. A line similar to
mode-line except at the top of the window. Example Info-mode creates
one for the navigation links Prev, Up etc. Should we introduce that
to?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 8 comments
GSoC 2013
11 years, 8 months
Stephen J. Turnbull
Stephen J. Turnbull
Hi all,
Is there interest having XEmacs participate in GSoC next year?
The last time this question came up, there was no real interest in
mentoring from the reviewers. This time I'm willing to serve as a
mentor or co-mentor having some experience as a co-mentor for Mailman.
Of course we need students. If anybody *is* a student, or has an
affiliation with an academic organization where likely candidates
could be recruited, please feel free to let me know.
There is some preparation we need to do at some point, in particular
we need to set up to receive funds from Google. In theory we could
incorporate as an NPO, but it's probably a better idea to affiliate
with an existing umbrella organization, such as Software in the Public
Interest, the Software Freedom Conservancy, or the Apache Software
Foundation.
Apparently this kind of thing can be done in a couple of months, since
there was just an announcement on the GSoC Mentors list for *this*
year's payments. But I figured I might as well mention it since it's
on my mind, and applications for next year's mentoring organizations
will catch us by surprise if we ignore it for the next few months.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 2 comments
xemacs-packages repo not updated for latest gnus?
11 years, 9 months
Mike Kupfer
Mike Kupfer
According to https://bitbucket.org/xemacs/xemacs-packages, the top-level
repo has not been updated to reflect my push to the gnus sub-repo. Is
this a glitch, or am I misunderstanding the workflow?
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 6 comments
Re: Future of XEmacs
11 years, 9 months
Stephen J. Turnbull
Stephen J. Turnbull
Uwe Brauer writes:
> However as far as know org-mode < vs 7 works well with
> Xemacs 21.4.X but only 21.5.X works with org-mode >vs
> 7.
This is the kind of issue that is indeed a problem for *upgrades*.
For a new package it shouldn't be a show-stopper as long as the
package is properly protected (eg, it errors when you try to load it
in 21.4 -- but this is not necessarily trivial if some other package
which requires it would break).
It would, however, be nice to provide some org-mode support for 21.4.
There are several plausible strategies.
If org-mode 8 actually works in XEmacs 21.4, but a few new commands
don't, we could simply add an org-old-xemacs.el file that is
conditionally required by loading org-mode, if XEmacs is too old.
This file would then advise those commands to throw an unimplemented
error.
If org-mode 8 generally depends on internal functions that don't work in
XEmacs 21.4, there are several options. Reimplement them compatibly
with XEmacs 21.4, implement the necessary APIs in Lisp in a separate
library, or provide a separate org-mode-7 package for use with XEmacs
21.4.
> That is why I don't know whether it makes really sense to
> provide orgmode as a xemacs pkg.
Please don't misunderstand. The "must work in stable" rule is not
intended to keep us from making progress. It's intended to prevent
regressions where a package that used to work in the stable XEmacs
breaks even though the user is using the same XEmacs they did before.
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 2 participants
- 3 comments
Future of XEmacs (was: XEmacs no longer has a Gentoo maintainer)
11 years, 9 months
Stephen J. Turnbull
Stephen J. Turnbull
I hope you don't mind me redirecting this to the list.
Mats Lidell writes:
> Hi Stephen,
>
> >>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
>
> > I disagree, but ... revisit us around Christmas. We'll see.
>
> Are you just considering what half a year with GPLv3 or later
> possibility will bring or are you sitting on some information you are
> not sharing publicly?
I know that I want to get some work done on XEmacs this summer. More
on precisely what that means shortly, once I actually start committing
some time. I suppose some others will too. For example, I know
Aidan's busy with his professional work, but obviously he has enough
time to read the list and enough interest to thank Hans. I imagine he
still has a few Common Lisp itches to scratch.
Also, I don't expect to, say, "catch up to GNU" by then, I'm just
saying I hope the project will show visible progress and activity by
then.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 10 participants
- 32 comments
Re: Future of XEmacs
11 years, 9 months
steven Mitchell
steven Mitchell
Hello,
All the talk of updating various packages: I'm trying to understand the
size of the tasks involved.
Does anybody have a list of packages that are current and which are
needing updated?
Also, what does updating a package mean?
Or maybe I should ask what is involved in updating a package?
Are we updating them to be the same as a similar emacs package or are we
updating them
by fixing known problems? or what?
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
- 3 participants
- 2 comments