April 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Suggestion to add php-mode.el to XEmacs prog-modes package 23 years

Adrian Aichner

Hello Steve, I used 0.9.6 which I found at http://sourceforge.net/projects/php-mode/ and it worked fine for me. Best regards, Adrian -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

5 participants
5 comments

problem with custom.el file options not being noticed 23 years

Peter Brown

hi all got an interesting problem i have been playing arround with my custom.el file i decided to start from scratch with 21.4.1 so i moved my old .xemacs directory then i thought i would use the sample init.el file (thanks for wrighting this one ben) i then coppied a whole bunch of options from my old custom.el file to the new one now some of my options are not being recognised build package ones so far are all i have noticed so far havent checked all of them any idea what is causing this ?? did i do the wrong thing in copying from my old file ?? thanks in advance -- ------------------------------------------------------------------------- Peter Brown Web Programmer/Sys Admin/Apache Admin Education Development Web peter(a)edw.com.au www.edw.com.au rendhalver(a)users.sourceforge.net -------------------------------------------------------------------------

1 participants
0 comments

GTK code duplication 23 years

Ben Wing

bill, i notice that to do your gtk stuff, you simply copied a lot of the existing X-based code. although this was certainly easier in the short run, it's really a bad idea. you're just begging for bitrot. it means, for example, that if i ever modify the X code [which is highly likely], i'm going to have to make all the changes twice. i really really don't want to have to deal with this. could you please look into avoiding such duplication? it's really pretty easy -- put all common code in another file [e.g. event-xlike.c], and use an extra argument to conditionalize on gtk/x differences when necessary. -- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.

1 participants
0 comments

21.4.1 and 21.5.0 - Customization menu problems 23 years

Latchezar M. Dimitrov

Help ! ------------- Begin Forwarded Message ------------- To: "Latchezar M. Dimitrov" <lmdimi(a)mthcsc.wfu.edu> Subject: Re: (no subject) From: Steve Youngs <youngs(a)xemacs.org> X-Attribution: SY X-URL: <http://www.xemacs.org/> X-Face: #/1'_-|5_1$xjR,mVKhpfMJcRh8"k}_a{EkIO:Ox<]＠zl/Yr|H,qH#3jJi6Aw(Mg＠"!+Z"C N_S3!3jzW^FnPeumv4l#,E}J.+e%0q(U>#b-#`~>l^A!_j5AEgpU)>t+VYZ$:El7hLa1:%%L=3%B>n K{^jU_{& Date: 27 Apr 2001 18:11:51 +1000 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 |--==> "LMD" == Latchezar M Dimitrov <lmdimi(a)mthcsc.wfu.edu> writes: LMD> Now if somebody there helps me fix that button problem with LMD> customization LMD> and >> >>More explanation, please. Can you send me a screenshot? [1] LMD> Here is the screenshot (customize.gif). And the same is for any customization I LMD> have tried. So I use 21.1.14 to make my customizations. I'm not sure that I can help you with this. Send another post to xemacs-beta, together with a screenshot and the output of M-x describe-installation. LMD> I have 21.1.14 and 21.4.1 and 21.5.0 installed under the same conditions with LMD> the same configure parameters (I have complete logs of all installations if they LMD> are necessary). They use the same init file (.emacs). Everything is the same ... LMD> except for the font on menu bar (see attachements - Cuyahoga.gif and LMD> alfalfa.gif). I like the .14 font but have no idea of why .4.1 and .5.0 use a LMD> different font. The fonts on the menubar are controlled from your ~/.Xdefaults file: *menubar*Font: -*-helvetica-bold-r-*-*-*-80-*-*-*-*-*-* LMD> And one more question (help) if you do not mind. I'd like to have different LMD> fonts for two different types of comments I use - comment char on the 1st col LMD> and on any other col. I reserve 1st col for a comment char when I'd like to LMD> (temporarily) comment out a line of code (see alfalfa.gif) and use any other col LMD> for general comments. I'd like general comments to be grayed italic proportional LMD> font and 1st col (code line) comment to be grayed but the same as ordinary code LMD> (monospaced) font. Would you please help me to do (customize) this? Unfortunately, alfalfa.gif didn't come through. -- |---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------<youngs(a)xemacs.org>---| ------------- End Forwarded Message ------------- Latchezar (Lucho) Dimitrov Wake Forest University, Winston-Salem, NC home: (336) 794-2094 grad.lab: (336) 758-4954 mailto:dimil01g＠wfu.edu or http://www.wfu.edu/~dimil01g/ lmdimi(a)mthcsc.wfu.edu lmdimi(a)pilot.mthcsc.wfu.edu ... Type fast, think slow. ... "Hippocratic Oath For Software Engineers" uname -a: SunOS eon 5.8 Generic_108528-01 sun4u sparc SUNW,Ultra-5_10 .//configure '--prefix=/usr/scratch/XEmacs' '--with-prefix=no' '--cflags=-O' '--with-mule' '--with-canna=no' '--with-wnn6=no' '--with-tooltalk' '--error-checking=none' '--memory-usage-stats' '--with-dragndrop' '--with-cde' '--with-pop' '--with-workshop' '--with-xfs' '--use-union-type' '--with-dialogs=athena' '--site-includes=/home/deacon/csgrad/lmdimi/usr/local/include:/home/deacon/csgrad/lmdimi/usr/local/include/X11' '--site-libraries=/usr/scratch/lib:/usr/scratch/lib/X11' XEmacs 21.5-b0 "alfalfa" configured for `sparc-sun-solaris2.8'. Compilation / Installation: Source code location: /usr/scratch/XEmacs/xemacs-21.5.0 Installation prefix: /usr/scratch/XEmacs Additional header files: /home/deacon/csgrad/lmdimi/usr/local/include /home/deacon/csgrad/lmdimi/usr/local/include/X11 Additional libraries: /usr/scratch/lib /usr/scratch/lib/X11 Runtime library search path: /usr/ccs/lib:/usr/scratch/lib:/usr/dt/lib:/usr/openwin/lib:/usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.95.2:/usr/local/lib Operating system description file: `s/sol2.h' Machine description file: `m/sparc.h' Compiler: gcc -O Relocating allocator for buffers: yes GNU version of malloc: yes Window System: Compiling in support for the X window system: - X Windows headers location: /usr/dt/include /usr/openwin/include - X Windows libraries location: /usr/dt/lib /usr/openwin/lib - Handling WM_COMMAND properly. Compiling in support for the Athena widget set: - Athena headers location: X11/Xaw - Athena library to link: Xaw Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Using Motif native widgets. Compiling in support for Drag'n'Drop (EXPERIMENTAL). - Drag'n'Drop prototype: CDE. TTY: Images: Compiling in support for GIF images (builtin). Compiling in support for XPM images. Compiling in support for PNG images. Compiling in support for JPEG images. Sound: Compiling in support for sound (native). Databases: Compiling in support for GNU DBM. Compiling in support for LDAP. Internationalization: Compiling in support for Mule (multi-lingual Emacs). Compiling in support for XIM (X11R5+ I18N input method). - Using Motif to provide XIM support. Mail: Compiling in support for POP mail retrieval. Compiling in support for "dot-locking" mail spool file locking method. Other Features: Compiling in support for ToolTalk. Compiling in support for Sun WorkShop. Compiling in support for dynamic shared object modules. Using the union type for Lisp_Objects. Compiling in support for extra debugging code.

1 participants
0 comments

[comp.emacs.xemacs] C-h f doesn't work: No such face hyper-apropos-hyperlink 23 years

Simon Josefsson

Forward because Help->Send bug report sent it to c.e.xemacs.

1 participants
0 comments

Re: Regexp Question 23 years

Adrian Aichner

The following message is a courtesy copy of an article that has been posted to comp.emacs.xemacs as well. >>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: Hello George, taking a closer look I think you found a bug in XEmacs. Here is an enhanced test-case with my results included. Testers: Just keep on eval-last-sexp to insert your results on various platforms. (progn (setq reg1 "a\$b\\(c\$d\\|bc\\)" reg2 "a\$\\(bc\$d\\|bc\\)") (save-excursion (re-search-forward reg1) (goto-char (point-max)) (insert ";" (emacs-version) "\n") (insert (format ";reg1\\1:%s\n" (match-string 1))) (insert (format ";reg1\\2:%s\n" (match-string 2)))) (save-excursion (re-search-forward reg2) (goto-char (point-max)) (insert (format ";reg2\\1:%s\n" (match-string 1))) (insert (format ";reg2\\2:%s\n" (match-string 2))))) abc ;XEmacs 21.1 (patch 14) "Cuyahoga Valley" [Lucid] (i386-pc-win32) of Wed Mar 14 2001 on D5DC120J ;reg1\1:bc ;reg1\2:c ;reg2\1:bc ;reg2\2:nil ;XEmacs 21.4 (beta1) "Copyleft" [Lucid] (i586-pc-win32) of Tue Apr 24 2001 on D5DC120J ;reg1\1:bc ;reg1\2:c ;reg2\1:bc ;reg2\2:nil Best regards, Adrian >>>>> "George" == George Ogata <g_ogata(a)ihug.com.au> writes: George> I have this in a buffer (XEmacs 21.1.14): George> ---------- Buffer: foo ---------- George> (save-excursion George> (setq reg1 "a\$b\\(c\$d\\|bc\\)" George> reg2 "a\$\\(bc\$d\\|bc\\)") George> (re-search-forward reg1) George> (match-string 2))-!- George> abc George> ---------- Buffer: foo ---------- George> If I eval-last-sexp, it returns "c", but if I use reg2 George> instead of reg1, it returns nil. Is this how it should George> be? The left side of \| wasn't used in either match, was George> it? And so (match-string 2) should be nil for both? APA> Hi George, APA> to determine the matching subexpression, you have to count the number APA> of \( from the left, starting at one, match-string 0 returns the whole APA> match. APA> So, the \| is not what's relevant here, it just specifies an APA> alternative match inside the same subexpression. APA> Hope this helps, APA> Adrian APA> -- APA> Adrian Aichner APA> mailto:adrian＠xemacs.org APA> http://www.xemacs.org/ -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

Re: Guile support in XEmacs. 23 years

monkeyiq

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > >>>>> "monkeyiq" == monkeyiq <monkeyiq(a)dingoblue.net.au> writes: > > monkeyiq> just in case the relavant people are unaware of swig, > > Dunno about anybody else, but I'm aware of SWIG. Unfortunately, SWIG > is designed for projects which can accept the discipline imposed by > writing with SWIG as the target. Emacs is 25 or 30 years old, full of > cruft and idiosyncracy. Well, from reading the previous URLs on future directions of XEmacs with respect to scripting lang (lisp/scheme) it seemed that the preposed step 1 was to cleanup the cruft a little, at which point it may (possibly) be feasable to use swig to wrap the C part and expose it to other languages. > > monkeyiq> so that people who want to script emacs in python can, > monkeyiq> and people who want LISP can. > > It doesn't really work that way. Yes, there's 22MB of C code in ./src > and ./lwlib, and only 13MB of Lisp in ./lisp. But much of the code in > ../src is Lisp "hand-compiled" to C. Really, less than 1/3 of X?Emacs > is "real C" code, and much of that is "hardware" interfacing (care and > feeding of windowing systems, etc). Much C code that implements > editing functionality is just wrappers around Lisp functions. Admittedly one would get a very lispish API for other languages. but I dont see that having C implement a lisp function being a real problem here (maybe its just me), if a lisp function can call the C function, or a perl sub can call a function that smells very lispish because it operates "like" a lisp programmer would expect. ie. in this case the perl guy can still call the function, and maybe somebody then wraps many of these lisp feeling functions into an OO perl framework, to give a less lisp feel to the API. > > Not to mention that much of the really advanced functionality is based > on hooks, AKA callbacks, and they must conform to the Lisp API. This would really be the interesting part. If I can find a more generic solution than what witme is using on this currently, then I might be in a better position to talk of this. I have not fully beaten this to death in witme at the moment, but I have ideas on the wing to play with. > > So SWIG isn't much help at all. > > You're welcome to think about it and try it out; there's plenty of > room in the repository for a branch if you get to actually coding. > But when it gets sticky, don't say we didn't warn you. :-) Heh, I'll keep this in mind :) though I'd like to be a lot more sure that my ideas work before forceing another branch of emacs on the world. > -- > University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN > Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 > _________________ _________________ _________________ _________________ > What are those straight lines for? "XEmacs rules." > -- --------------------------------------------------- It's the question, http://witme.sourceforge.net If you think education is expensive, try ignorance. -- Derek Bok, president of Harvard

3 participants
2 comments

igrep & hexl 23 years

Jeff Mincy

I'm running xemacs 21.1 (native?) on w98 with cygwin I decided to figure out why hexl-mode was getting: Spawning child process: exec format error Basically, command.com wouldn't execute the hexlify-command, and /bin/sh wouldn't do c:\\Program Files\XEmacs\\... so I did: (setq shell-command-switch "-c") ;; was "/c" (setq shell-file-name "/Cygwin/bin/sh") ;; was c:\\COMMAND.COM (setq hexl-program "hexl.exe") (setq hexl-iso "-iso" exec-directory "c:/PROGRA~1/XEmacs/XEmacs-21.1.13/i386-pc-win32/") Ok, great, hexl works. But now, M-x igrep doesn't work. (setq shell-command-switch "/c") (setq shell-file-name "c:\\COMMAND.COM") Ok, now igrep works again. So how do I get both igrep and hexl to work? -jeff

1 participants
1 comments

XEmacs 21.2-b4[56] hangs on creating a new frame 23 years

Tony Lam

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.2 (beta46) "Urania" [Lucid] (sparc-sun-solaris2.8) of Mon Apr 2 2001 on philly configured using `configure --prefix=/home/tonyl/loc --with-prefix=no --with-gcc=no '--cflags=-v -xO4' --with-x --with-xpm --x-includes=/net/pkg/export/pkg.sparc.sunos5/X11R6.4/include:/import/dream/tools/include '--site-includes=/import/dream/tools/include /usr/dt/include /net/pkg/export/pkg.sparc.sunos5/local/include/db' --x-libraries=/net/pkg/export/pkg.sparc.sunos5/X11R6.4/lib '--site-libraries=/usr/lib /usr/lib /import/dream/tools/lib /import/dream/tools/lib/X11 /usr/dt/lib /net/pkg/export/pkg.sparc.sunos5/local/lib' --with-database=berkdb,dbm --with-png --with-jpeg --with-tooltalk --with-workshop --with-cde --with-sparcworks=yes --with-xface --with-socks=no --with-mule=no --with-xfs=no --site-runtime-libraries=/usr/ccs/lib:/import/dream/tools/lib:/import/dream/tools/lib/X11:/usr/dt/lib --error-checking=no --debug=yes --with-gtk=no' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: This has occurred quite frequently in v21.2-b4[56], with both CDE and GNome, XEmacs comes up and hangs immediately on creating a new frame. tonyl＠philly> xemacs-21.2-b46 xemacs-21.2-b46: X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 61 (X_ClearArea) Resource id in failed request: 0x0 Serial number of failed request: 1743 Current serial number in output stream: 1743 xemacs-21.2-b46: X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 70 (X_PolyFillRectangle) Resource id in failed request: 0x0 Serial number of failed request: 1744 Current serial number in output stream: 1816 xemacs-21.2-b46: X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 70 (X_PolyFillRectangle) Resource id in failed request: 0x0 Serial number of failed request: 1817 Current serial number in output stream: 1841 (gdb) where #0 0xfec98224 in _poll () from /usr/lib/libc.so.1 #1 0xfec4b808 in select () from /usr/lib/libc.so.1 #2 0xfee9b6cc in _XWaitForReadable () from /usr/lib/libX11.so.4 #3 0xfee9b4e4 in _XRead () from /usr/lib/libX11.so.4 #4 0xfee9c53c in _XReply () from /usr/lib/libX11.so.4 #5 0xfeea782c in XGetWindowProperty () from /usr/lib/libX11.so.4 #6 0x2275c4 in x_wm_hack_wm_protocols () #7 0x22a0d0 in x_popup_frame () #8 0x154204 in Fmake_frame () #9 0xb73c8 in Ffuncall () #10 0x69ea8 in execute_optimized_program () #11 0x697f4 in funcall_compiled_function () #12 0xb7858 in Ffuncall () #13 0x69ea8 in execute_optimized_program () #14 0x697f4 in funcall_compiled_function () #15 0xb7858 in Ffuncall () #16 0x69ea8 in execute_optimized_program () #17 0x6e318 in Fbyte_code () #18 0xb6050 in Feval () #19 0x1a56ac in readevalloop () #20 0x1a38b4 in Fload_internal () #21 0xb7450 in Ffuncall () #22 0x69ea8 in execute_optimized_program () ---Type <return> to continue, or q <return> to quit--- #23 0x697f4 in funcall_compiled_function () #24 0xb7858 in Ffuncall () #25 0x69ea8 in execute_optimized_program () #26 0x697f4 in funcall_compiled_function () #27 0xb7858 in Ffuncall () #28 0x69ea8 in execute_optimized_program () #29 0x6e318 in Fbyte_code () #30 0xb6050 in Feval () #31 0x1a56ac in readevalloop () #32 0x1a38b4 in Fload_internal () #33 0xb7450 in Ffuncall () #34 0x69ea8 in execute_optimized_program () #35 0x697f4 in funcall_compiled_function () #36 0xb7858 in Ffuncall () #37 0x69ea8 in execute_optimized_program () #38 0x697f4 in funcall_compiled_function () #39 0xb7858 in Ffuncall () #40 0x69ea8 in execute_optimized_program () #41 0x6e318 in Fbyte_code () #42 0xb6050 in Feval () #43 0xa214c in condition_case_1 () #44 0xa4228 in condition_case_3 () #45 0x6b424 in execute_rare_opcode () ---Type <return> to continue, or q <return> to quit--- #46 0x69cb0 in execute_optimized_program () #47 0x697f4 in funcall_compiled_function () #48 0xb7858 in Ffuncall () #49 0x69ea8 in execute_optimized_program () #50 0x697f4 in funcall_compiled_function () #51 0xb7858 in Ffuncall () #52 0x69ea8 in execute_optimized_program () #53 0x697f4 in funcall_compiled_function () #54 0xb6638 in Feval () #55 0xa214c in condition_case_1 () #56 0x766b4 in top_level_1 () #57 0xa1328 in internal_catch () #58 0x76808 in initial_command_loop () #59 0x976a4 in xemacs_21_2_b46_sparc_sun_solaris2_8 () #60 0x980e8 in main () (gdb)

3 participants
3 comments

Re: Agony, persistent solaris8 hang of doom: Can I help debug this? 23 years

John M. Adams

Ben Wing <ben(a)666.com> writes: > John -- if you're interested in doing a bit of coding to fix your problem, > here's what i wrote to Gunnar about rewriting the quit handling. this should > probably fix your problem along with it... OK, I'll give it a try. I appreciate everyone's comments. Thanks alot. -- John M. Adams

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 April 2001