January 2001 - XEmacs-Beta - XEmacs Mailing List Archives

BUG: finder-commentary kills existing buffer 23 years, 3 months

Jari Aalto+mail.emacs

If I run finder-commentary on file that is already in my Emacs, it is removed. It should be retained. Jari

1 participants
0 comments

Anyone using b39 non-Solaris + SIGIO + widgets + Motif? 23 years, 3 months

Andy Piper

Ray Toy is seeing this behaviour under Solaris (2.7?): When font-locking a buffer the progress gauge moves very slowly unless one moves the mouse around at the same time. I need to know whether anyone is using a similar configuration and whether they are or are not seeing the problem. For instance HPUX + widgets + Motif would do fine. If others are not seeing the problem it may be indicative of SIGIO wierdness under Solaris. I do not have the problem under cygwin + motif, but then SIGIO is broken on that platform. I also do not have the problem under Linux + Athena but then it may be Motif related. Thanks andy -------------------------------------------------------------- Dr Andy Piper Principal Consultant, BEA Systems Ltd

1 participants
0 comments

XEmacs 21.1.13 will be released Sun (2001-01-07) evening 23 years, 3 months

Vin Shelton

I will be releasing 21.1.13 tomorrow evening my time (EST). The release will be based on the current contents of CVS. (I committed 3 or 4 minor fixes this evening, BTW). This is, therefore, your last chance to complain about any show-stopper bugs present in 21.1 CVS. - vin

2 participants
1 comments

Win32 port: expand-file-name uses backslashes? (Emacs compatibility) 23 years, 3 months

Jari Aalto+mail.emacs

I was hit by the fact that expand-file-name does not work the same way as in Emacs. It returns the result in backslash format in win32 and forward slashes in Unix. This is a bit hard and ugly when I combine paths always with forward slashes. (expand that) + "path/here" \that\dir/path/here It also defeated In my code member and pushnew tests now when everything was not in forward slash format. Oh well... In Emacs it always returns forward slashes which I think is easy for a develooper. Would it be possible to modify it so that expand-file-name had an additional argument FORMAT that would control the path expansion. By default it would return always forward slashes to regain Emacs compatibility. With extra argument: FORMAT 'native as OS default. In Win32 \ in Unix / 'dos Explicit \ request 'unix Explicit / request Jari -- http://tiny-tools.sourceforge.net/

2 participants
1 comments

FSF Emacs compatibility: require command needs synching 23 years, 3 months

Jari Aalto+mail.emacs

In XEmacs "21.2 (beta32) (require FEATURE &optional FILE-NAME) In Emacs 20.6 require is a Lisp function. (require FEATURE &optional FILE-NAME NOERROR) If feature FEATURE is not loaded, load it from FILENAME. If FEATURE is not a member of the list `features', then the feature is not loaded; so load the file FILENAME. If FILENAME is omitted, the printname of FEATURE is used as the file name, but in this case `load' insists on adding the suffix `.el' or `.elc'. If the optional third argument NOERROR is non-nil, then return nil if the file is not found. Normally the return value is FEATURE. (require FEATURE &optional FILE-NAME NOERROR) Jari -- http://tiny-tools.sourceforge.net/

2 participants
1 comments

defmacro problem: create var inside let statement? 23 years, 3 months

Jari Aalto+mail.emacs

I' trying to select correct variable at compile timeusing the defmacro, but it seems that I don't understand how to use it inside let definitions. Here is the problem: (defmacro my-load-user-init-file () (cond ((boundp 'load-user-init-file-p) (intern "load-user-init-file-p")) ((boundp 'init-file-user) (intern "init-file-user")) (t (intern "dummy")))) (defun test () (let* (((my-load-user-init-file) t) ) 'ok)) Compiling file e:\home\jaalto\tmp\t1.el at Fri Jan 05 22:48:18 2001 While compiling test: ** Attempt to let-bind non-symbol (my-load-user-init-file) What magic I need? -- http://tiny-tools.sourceforge.net/

2 participants
1 comments

subr doc representation 23 years, 3 months

Ilya N. Golubev

It works this way (doc.c): doc type is (char *). If (EMACS_INT) doc >= 0, it is really a pointer. Otherwise we should use (off_t) (- (EMACS_INT) doc) for seeking in `DOC' file. It used to be this way in emacs-18.55, so it worked for all known platforms for more than 10 yrs, and my ones are no exception. But what forbids it to stop working? What requires valid pointers to be non- negative when converted to integer? Once it is not the case, doc implementation has to be rewritten. Most surprising is why design its own representation rules for doc? We just have a way to store both integer and pointer in a single word distinguishably: Lisp_Object. Why not reuse it for Lisp_Subr.doc?

3 participants
6 comments

Module path initialization 23 years, 3 months

Jerry James

I finally got around to performing an experiment. There are four binary variables in the experiment: 1) Build inside the source tree vs. build outside the source tree. 2) A vanilla XEmacs 21.2.39 vs. an XEmacs 21.2.39 with this patch applied: <URL:http://www.xemacs.org/list-archives/xemacs-beta/200012/msg00170.html>. Between builds, I completely removed the source tree, and then reunpacked the XEmacs 21.2.39 tarball to be sure there was no poisoning of one test by another. (Yes, this took awhile.) 3) Building with no previously built XEmacs installed vs. building with a previous build of 21.2.39 installed. I am using a prefix of /usr/local/test for this so that my XEmacs 21.1 won't get in the way. 4) Run in place vs. run in the install location. For each of the 16 possible combinations of these variables, I report on the values of 3 Lisp variables related to modules. Note that I did NOT specify any module directories when configure was run, so configure-module-directory and configure-site-module-directory are both nil in every case. The results are shown below. Even though variables #1 and #3 should not be affecting the outcome, they are. Also, although #4 should affect the outcome, it isn't affecting it in the right way. Note that, even though we are running in place in Experiments 3, 7, 11, and 15, paths in /usr/local/test appear in the results. Also, and much worse, although we are running the installed version in Experiments 10, 12, and 14, paths in /usr/src/xemacs-21.2.39 appear in the results! Experiment #1: Outside, vanilla, no installed tree, run in place module-load-path = nil module-directory = nil site-module-directory = nil Experiment #2: Outside, vanilla, no installed tree, installed module-load-path = nil module-directory = nil site-module-directory = nil Experiment #3: Outside, vanilla, installed tree, run in place module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/include/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/") module-directory = "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Experiment #4: Outside, vanilla, installed tree, installed module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/include/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/") module-directory = "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Experiment #5: Outside, patched, no installed tree, run in place module-load-path = nil module-directory = nil site-module-directory = nil Experiment #6: Outside, patched, no installed tree, installed module-load-path = nil module-directory = nil site-module-directory = nil Experiment #7: Outside, patched, installed tree, run in place module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/") module-directory = "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Experiment #8: Outside, patched, installed tree, installed module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/") module-directory = "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Experiment #9: Inside, vanilla, no installed tree, run in place module-load-path = ("/usr/src/xemacs-21.2.39/modules/" "/usr/src/xemacs-21.2.39/modules/base64/" "/usr/src/xemacs-21.2.39/modules/ldap/" "/usr/src/xemacs-21.2.39/modules/sample/" "/usr/src/xemacs-21.2.39/modules/zlib/") module-directory = "/usr/src/xemacs-21.2.39/modules/" site-module-directory = nil Experiment #10: Inside, vanilla, no installed tree, installed module-load-path = ("/usr/src/xemacs-21.2.39/modules/" "/usr/src/xemacs-21.2.39/modules/base64/" "/usr/src/xemacs-21.2.39/modules/ldap/" "/usr/src/xemacs-21.2.39/modules/sample/" "/usr/src/xemacs-21.2.39/modules/zlib/") module-directory = "/usr/src/xemacs-21.2.39/modules/" site-module-directory = nil Experiment #11: Inside, vanilla, installed tree, run in place module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/src/xemacs-21.2.39/modules/" "/usr/src/xemacs-21.2.39/modules/base64/" "/usr/src/xemacs-21.2.39/modules/ldap/" "/usr/src/xemacs-21.2.39/modules/sample/" "/usr/src/xemacs-21.2.39/modules/zlib/") module-directory = "/usr/src/xemacs-21.2.39/modules/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Experiment #12: Inside, vanilla, installed tree, installed module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/src/xemacs-21.2.39/modules/" "/usr/src/xemacs-21.2.39/modules/base64/" "/usr/src/xemacs-21.2.39/modules/ldap/" "/usr/src/xemacs-21.2.39/modules/sample/" "/usr/src/xemacs-21.2.39/modules/zlib/") module-directory = "/usr/src/xemacs-21.2.39/modules/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Experiment #13: Inside, patched, no installed tree, run in place module-load-path = ("/usr/src/xemacs-21.2.39/modules/" "/usr/src/xemacs-21.2.39/modules/base64/" "/usr/src/xemacs-21.2.39/modules/ldap/" "/usr/src/xemacs-21.2.39/modules/sample/" "/usr/src/xemacs-21.2.39/modules/zlib/") module-directory = "/usr/src/xemacs-21.2.39/modules/" site-module-directory = nil Experiment #14: Inside, patched, no installed tree, installed module-load-path = ("/usr/src/xemacs-21.2.39/modules/" "/usr/src/xemacs-21.2.39/modules/base64/" "/usr/src/xemacs-21.2.39/modules/ldap/" "/usr/src/xemacs-21.2.39/modules/sample/" "/usr/src/xemacs-21.2.39/modules/zlib/") module-directory = "/usr/src/xemacs-21.2.39/modules/" site-module-directory = nil Experiment #15: Inside, patched, installed tree, run in place module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/") module-directory = "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Experiment #16: Inside, patched, installed tree, installed module-load-path = ("/usr/local/test/lib/xemacs/site-modules/" "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/") module-directory = "/usr/local/test/lib/xemacs-21.2-b39/i686-pc-linux/modules/" site-module-directory = "/usr/local/test/lib/xemacs/site-modules/" Regards, -- Jerry James

2 participants
1 comments

w/o menu gutter misplaced 23 years, 3 months

Ilya N. Golubev

Version: 21.2.37, 21.2.38 Platform: SCO 5.0.2, gcc 2.95.2 1. Run `xemacs -q' 2. Evaluate (set-specifier menubar-visible-p nil 'global) Gutter with buffer tabs remains located as if there is still a frame menu. Upper text window of the same frame becomes attached to frame upper edge, so that part of its text is overlapped by gutter.

2 participants
6 comments

[ 111160 ] xemacs-build-reports mailing list 23 years, 3 months

nobody

Support Request #111160, was updated on 2001-Jan-04 11:34 You can respond by visiting: http://sourceforge.net/support/?func=detailsupport&support_id=111160&grou... Category: Lists Status: Open Priority: 5 Summary: xemacs-build-reports mailing list By: jasonrm Date: 2001-Jan-04 11:34 Message: Logged In: YES user_id=85984 Browser: Mozilla/4.76 [en] (X11; U; Linux 2.2.14 i686) The web interface would not allow me to create this list due to a character input limitation. Instead I had to create `xemacs-binary-kit' which is not what we want. Can you please rename this mailing list? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/support/?func=detailsupport&support_id=111160&grou...

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