July 1999 - XEmacs-Beta - XEmacs Mailing List Archives

evil behaviour for enable-multibyte-characters 25 years, 4 months

William M. Perry

This _HAS_ to be buffer-local if it is supposed to mimic the same variable under Emacs 20.x Without this, packages that (correctly) set enable-multibyte-characters can screw each other over. And individual applications should *NOT* have to make this buffer-local themselves. -bp Index: coding.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/lisp/coding.el,v retrieving revision 1.2.2.2 diff -c -w -r1.2.2.2 coding.el *** coding.el 1999/06/11 03:09:19 1.2.2.2 --- coding.el 1999/07/30 18:11:46 *************** *** 207,212 **** --- 207,213 ---- (copy-coding-system 'undecided 'automatic-conversion) (make-compatible-variable 'enable-multibyte-characters "Unimplemented") + (make-variable-buffer-local 'enable-multibyte-characters) (define-obsolete-variable-alias 'pathname-coding-system 'file-name-coding-system)

2 participants
1 comments

If you are experiencing gutter problems 25 years, 4 months

Andy Piper

.. then I advise using the 21.2.19 tag from CVS until I get back on wednesday and can take a look.... Builds from tarballs should be ok as that is vanilla 21.2.19 without the X tab support. got to go .... andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Re: gutter problem 25 years, 4 months

Andy Piper

At 03:54 PM 7/30/99 +0100, Ian MacKinnon wrote: >Hi All, >I am seeing a glitch with the gutter-items >The tabs for deleted buffers don't want to go away >ie visit a buffer, then delete that buffer, and the tab for it persists >If I create a new frame, then the new frame is correct > >this is xemacs-21.2.19 on cygwin on NT This is fixed in the latest CVS, but the latest CVS is causing many X problems. Windows may be ok. andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Where is ps-print? 25 years, 4 months

Adrian Aichner

During my update to all the latest packages I lost ps-print. I vaguely remember some discussions about it a while back. Where is ps-print? Thanks, Adrian

1 participants
0 comments

XEmacs 21.2.19 "新宿" is released 25 years, 4 months

SL Baur

Get it from the usual places: ftp://ftp.xemacs.org/pub/xemacs/beta/xemacs-21.2/ http://cvs.xemacs.org/ New XEmacs lisp packages have been uploaded as well. The new Sumos are in: ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-sumo.tar.gz ftp://ftp.xemacs.org/pub/xemacs/packages/xemacs-mule-sumo.tar.gz Everything has been rebuilt & repackaged in order to fix an installation bug. Many packages have been updated. VM is now current, BBDB is now current to name two. Lots of bug fixes, lots of new bugs to find, in other words a typical beta XEmacs. Enjoy. "Shinjuku" is the ward of Tokyo where Jareth Hein lives. It is a very cool place to visit. It is 90/90 today, 90+ degrees and 90+% humidity. Please forgive me for being terse. Happy Birthday in advance to Jason Mastaler (Saturday is his birthday). to 21.2.19 "Shinjuku" -- various fixes from Gunnar Evermann -- XIM fixes from Kazuyuki IENAGA -- keymap fix from Katsumi Yamaoka -- Microsoft build fixes from Adrian Aichner -- documentation update from Adrian Aichner -- rect.el rewrite from Didier Verna -- custom comment fields from Didier Verna -- various fixes from Karl Hegbloom -- filling fix from Yoshiki Hayashi -- miscellaneous changes from Jeff Miller and Didier Verna -- configure hacking from Steve Baur -- various fixes from Bob Weiner -- Mule synching from MORIOKA Tomohiko -- various fixes from Steve Baur -- LDAP configure changes from Gregory Neil Shapiro -- gutter implementation from Andy Piper -- tab widgets in gutter from Andy Piper -- Custom themes, API part. See etc/custom/theme-examples from Jan Vroonhof

3 participants
2 comments

[OK] 21.2 (beta19) "Shinjuku" XEmacs Lucid on i586-pc-linux 25 years, 4 months

Larry Ayers

Built from patched source, runs fine. I noticed that the gutter patches have been applied, and that there is a new menu-item (Options->Gutter Appearance). There is no visible gutter, though. Shouldn't there be? > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /box/xemacs-21.2-b14/Installation: > (Output from most recent run of ./configure) uname -a: Linux liatris 2.2.10 #1 Tue Jul 20 11:39:42 CDT 1999 i586 unknown ./configure '--prefix=/usr/local' '--with-site-lisp' '--with-xpm' '--with-tiff=no' '--with-dialogs=athena' '--error-checking=none' XEmacs 21.2-b19 "Shinjuku" configured for `i586-pc-linux'. Where should the build process find the source code? /box/xemacs-21.2-b14 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11/include Where do we find X Windows libraries? /usr/X11/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Motif native widgets. Using Athena dialog boxes. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files. Compiling in extra code for debugging. > Contents of /box/xemacs-21.2-b14/beta.err > keeping lines matching > "^--\[\[\|\]\]$\|make\[\|error\|warn\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compilation\|not\s-+found" > and then deleting lines matching > "confl.*with.*auto-inlining\|/box/xemacs-21\.2-b14/lisp/[^ ]+ hides " /box/xemacs-21.2-b14/lib-src/gnuserv.c:326: warning: `len' might be used uninitialized in this function /box/xemacs-21.2-b14/lib-src/etags.c:858: warning: `opt' might be used uninitialized in this function /box/xemacs-21.2-b14/lib-src/etags.c:1849: warning: array subscript has type `char' /box/xemacs-21.2-b14/lib-src/etags.c:1849: warning: array subscript has type `char' /box/xemacs-21.2-b14/lib-src/etags.c:1849: warning: array subscript has type `char' /box/xemacs-21.2-b14/lib-src/etags.c:1849: warning: array subscript has type `char' /box/xemacs-21.2-b14/lib-src/ootags.c:911: warning: `opt' might be used uninitialized in this function /box/xemacs-21.2-b14/lib-src/ootags.c:1912: warning: array subscript has type `char' /box/xemacs-21.2-b14/lib-src/ootags.c:1912: warning: array subscript has type `char' /box/xemacs-21.2-b14/src/config.h:36: warning: `alloca' redefined /usr/include/alloca.h:36: warning: this is the location of the previous definition bytecode.c:636: warning: `opcode' might be used uninitialized in this function callint.c:249: warning: `argcount' might be used uninitialized in this function callint.c:545: warning: `args' might be used uninitialized in this function callint.c:550: warning: `visargs' might be used uninitialized in this function callint.c:554: warning: `varies' might be used uninitialized in this function callint.c:555: warning: `arg_from_tty' might be used uninitialized in this function callint.c:556: warning: `argnum' might be used uninitialized in this function callint.c:571: warning: `prompt_start' might be used uninitialized in this function callint.c:572: warning: `prompt_limit' might be used uninitialized in this function callint.c:573: warning: `prompt_length' might be used uninitialized in this function callint.c:591: warning: `prompt_start' might be used uninitialized in this function callint.c:591: warning: `prompt_length' might be used uninitialized in this function callint.c:591: warning: `args' might be used uninitialized in this function callint.c:591: warning: `nargs' might be used uninitialized in this function callint.c:603: warning: `prompt_start' might be used uninitialized in this function callint.c:603: warning: `prompt_length' might be used uninitialized in this function callint.c:603: warning: `args' might be used uninitialized in this function callint.c:603: warning: `nargs' might be used uninitialized in this function callint.c:612: warning: `prompt_start' might be used uninitialized in this function callint.c:612: warning: `prompt_length' might be used uninitialized in this function callint.c:612: warning: `args' might be used uninitialized in this function callint.c:612: warning: `nargs' might be used uninitialized in this function callint.c:622: warning: `prompt_start' might be used uninitialized in this function callint.c:622: warning: `prompt_length' might be used uninitialized in this function callint.c:622: warning: `args' might be used uninitialized in this function callint.c:622: warning: `nargs' might be used uninitialized in this function callint.c:640: warning: `prompt_start' might be used uninitialized in this function callint.c:640: warning: `prompt_length' might be used uninitialized in this function callint.c:640: warning: `args' might be used uninitialized in this function callint.c:640: warning: `nargs' might be used uninitialized in this function callint.c:686: warning: `prompt_start' might be used uninitialized in this function callint.c:686: warning: `prompt_length' might be used uninitialized in this function callint.c:686: warning: `args' might be used uninitialized in this function callint.c:686: warning: `nargs' might be used uninitialized in this function callint.c:696: warning: `prompt_start' might be used uninitialized in this function callint.c:696: warning: `prompt_length' might be used uninitialized in this function callint.c:696: warning: `args' might be used uninitialized in this function callint.c:696: warning: `nargs' might be used uninitialized in this function callint.c:707: warning: `prompt_start' might be used uninitialized in this function callint.c:707: warning: `prompt_length' might be used uninitialized in this function callint.c:707: warning: `args' might be used uninitialized in this function callint.c:707: warning: `nargs' might be used uninitialized in this function callint.c:720: warning: `prompt_start' might be used uninitialized in this function callint.c:720: warning: `prompt_length' might be used uninitialized in this function callint.c:720: warning: `args' might be used uninitialized in this function callint.c:720: warning: `nargs' might be used uninitialized in this function callint.c:740: warning: `prompt_start' might be used uninitialized in this function callint.c:740: warning: `prompt_length' might be used uninitialized in this function callint.c:740: warning: `args' might be used uninitialized in this function callint.c:740: warning: `nargs' might be used uninitialized in this function callint.c:765: warning: `prompt_start' might be used uninitialized in this function callint.c:765: warning: `prompt_length' might be used uninitialized in this function callint.c:765: warning: `args' might be used uninitialized in this function callint.c:765: warning: `nargs' might be used uninitialized in this function callint.c:807: warning: `prompt_start' might be used uninitialized in this function callint.c:807: warning: `prompt_length' might be used uninitialized in this function callint.c:807: warning: `args' might be used uninitialized in this function callint.c:807: warning: `nargs' might be used uninitialized in this function callint.c:830: warning: `prompt_start' might be used uninitialized in this function callint.c:830: warning: `prompt_length' might be used uninitialized in this function callint.c:830: warning: `args' might be used uninitialized in this function callint.c:830: warning: `nargs' might be used uninitialized in this function callint.c:849: warning: `prompt_start' might be used uninitialized in this function callint.c:849: warning: `prompt_length' might be used uninitialized in this function callint.c:849: warning: `args' might be used uninitialized in this function callint.c:849: warning: `nargs' might be used uninitialized in this function callint.c:856: warning: `prompt_start' might be used uninitialized in this function callint.c:856: warning: `prompt_length' might be used uninitialized in this function callint.c:856: warning: `args' might be used uninitialized in this function callint.c:856: warning: `nargs' might be used uninitialized in this function callint.c:863: warning: `prompt_start' might be used uninitialized in this function callint.c:863: warning: `prompt_length' might be used uninitialized in this function callint.c:863: warning: `args' might be used uninitialized in this function callint.c:863: warning: `nargs' might be used uninitialized in this function editfns.c:1173: warning: `tzstring' might be used uninitialized in this function emacs.c:2196: warning: assignment from incompatible pointer type emacs.c:2255: warning: assignment from incompatible pointer type eval.c:2861: warning: `val' might be used uninitialized in this function eval.c:3127: warning: `val' might be used uninitialized in this function events.c:429: warning: `tail' might be used uninitialized in this function events.c:429: warning: `keyword' might be used uninitialized in this function events.c:546: warning: `modifiers' might be used uninitialized in this function event-tty.c:104: warning: `c' might be used uninitialized in this function redisplay-tty.c:329: warning: `instance' might be used uninitialized in this function extents.c:1822: warning: `start_open' might be used uninitialized in this function extents.c:1822: warning: `end_open' might be used uninitialized in this function extents.c:4378: warning: `fl' might be used uninitialized in this function extents.c:4390: warning: `at_flag' might be used uninitialized in this function extents.c:5010: warning: `layout' might be used uninitialized in this function fns.c:584: warning: `val' might be used uninitialized in this function fns.c:780: warning: `v' might be used uninitialized in this function frame.c:1571: warning: `ecran' might be used uninitialized in this function glyphs.c:326: warning: `typevec' might be used uninitialized in this function glyphs.c:1230: warning: `type' might be used uninitialized in this function glyphs.c:1267: warning: `type' might be used uninitialized in this function print.c:1091: warning: `i' might be used uninitialized in this function select.c:205: warning: `selection_data' might be used uninitialized in this function select.c:226: warning: `rest' might be used uninitialized in this function specifier.c:1643: warning: `tem' might be used uninitialized in this function specifier.c:1849: warning: `add_meth' might be used uninitialized in this function specifier.c:361: warning: `i' might be used uninitialized in this function symbols.c:309: warning: `tail' might be used uninitialized in this function symbols.c:1591: warning: `valcontents' might be used uninitialized in this function symbols.c:1984: warning: `valcontents' might be used uninitialized in this function symbols.c:2084: warning: `valcontents' might be used uninitialized in this function symbols.c:2131: warning: `bfwd' might be used uninitialized in this function symbols.c:2485: warning: `valcontents' might be used uninitialized in this function device-x.c: In function `x_IO_error_handler': device-x.c:112: warning: `d' might be used uninitialized in this function device-x.c:112: warning: `d' might be used uninitialized in this function glyphs-x.c:1154: warning: `dpy' might be used uninitialized in this function glyphs-x.c:1155: warning: `xs' might be used uninitialized in this function glyphs-x.c:1156: warning: `cmap' might be used uninitialized in this function glyphs-x.c:1157: warning: `depth' might be used uninitialized in this function glyphs-x.c:1158: warning: `visual' might be used uninitialized in this function glyphs-x.c:1162: warning: `result' might be used uninitialized in this function glyphs-x.c:1166: warning: `type' might be used uninitialized in this function glyphs-x.c:1167: warning: `force_mono' might be used uninitialized in this function glyphs-x.c:1209: warning: `type' might be used uninitialized in this function glyphs-x.c:1215: warning: `__s' might be used uninitialized in this function glyphs-x.c:1358: warning: `xs' might be used uninitialized in this function redisplay-x.c:451: warning: `instance' might be used uninitialized in this function window.c:438: warning: `retval' might be used uninitialized in this function window.c:438: warning: `retval' might be used uninitialized in this function window.c:438: warning: `retval' might be used uninitialized in this function window.c:4870: warning: `previous_minibuf_top' might be used uninitialized in this function window.c:407: warning: `retval' might be used uninitialized in this function Warning: doc lost for function make-char. /usr/local/lib/xemacs/site-lisp/pop3 hides /usr/local/lib/xemacs/packages/lisp/mail-lib/pop3

1 participants
0 comments

[SUCCESS] XEmacs 21.2-b19 "Shinjuku" on FreeBSD 25 years, 4 months

KINOSHITA Masahiro

% gcc -v gcc version egcs-2.91.66 19990314 (egcs-1.1.2 release) % uname -a FreeBSD **.jaist.ac.jp 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Wed Jul 28 15:20:14 JST 1999 m-kino＠**.jaist.ac.jp:/var/v6/src/sys/compile/OMOIKANE i386 XEmacs 21.2-b19 "Shinjuku" configured for `i386-unknown-freebsd3.2'. Where should the build process find the source code? /home/fs361/m-kino/wor k/xemacs-21.2.19 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/freebsd.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -O2 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Additional header files: /usr/local/include Additional libraries: /usr/local/lib Runtime library search path: /usr/local/lib:/usr/X1 1R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Using XFontSet to provide bilingual menubar. Compiling in support for Canna on Mule. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DSO module support. movemail will use "flock" for locking mail spool files. Compiling in extra code for debugging. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: ---------------------------------------------------------

1 participants
0 comments

Re: FYI mailcrypt-3.5.4 25 years, 4 months

SL Baur

Neal Becker <nbecker(a)fred.net> writes in xemacs-beta(a)xemacs.org: > http://freshmeat.net/news/1999/07/26/933042852.html Server Error Server Error This server has encountered an internal error which prevents it from fulfilling your request. The most likely cause is a misconfiguration. Please ask the administrator to look for messages in the server's error log.

2 participants
1 comments

Re: Merging with GNU Emacs 25 years, 4 months

SL Baur

Hrvoje Niksic <hniksic(a)srce.hr> writes in xemacs-beta(a)xemacs.org: > Pixel-based scrolling, which would require clipping the top-most line > in addition to the bottom-most one, would be really cool. And pixel-based filling, so auto-filling works properly with variable width fonts.

2 participants
1 comments

Re: gutter causes core dumps! 25 years, 4 months

Neal D. Becker

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> At 09:36 AM 7/30/99 -0400, nbecker(a)fred.net wrote: Andy> I'm guessing this is a bug in the Tab widget. I've had to fix one core Andy> dumping bug already. I suggest you back-up to vanilla 21.2.19. I rebuilt with make clean first. Maybe it's stable now (not sure yet). What is the cvs tag to grab vanilla 21.2.19?

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta July 1999