August 2011 - XEmacs-Beta - XEmacs Mailing List Archives

Eric S. Johansson

I am having no end of problems building under cygwin. I keep going back to fetch missing libraries and I keep corrupting something which forces me to rebase cygwin which is a very hand breaking sequence. Is there any less fragile environment I could build in and still be useful to you guys? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

4 participants
3 comments

Summary of XEmacs Issue Tracking System Issues 13 years, 3 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2011-08-09 - 2011-08-16) XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 543 open ( +1) / 251 closed ( +0) / 794 total ( +1) Open issues with patches: 12 Average duration of open issues: 907 days. Median duration of open issues: 987 days. Open Issues Breakdown new 204 ( +1) deferred 6 ( +0) napping 4 ( +0) verified 54 ( +0) assigned 153 ( +0) committed 30 ( +0) documented 3 ( +0) done/needs work 24 ( +0) Issues Created Or Reopened (1) ______________________________ Crash reading a specific xml file 2011-08-10 http://tracker.xemacs.org/XEmacs/its/issue796 created sdcoonce _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

My XEmacs can't find its packages 13 years, 3 months

Alan Mackenzie

Hi, XEmacs. My XEmacs cannot find its packages. o - I configured the XEmacs build with a bare "./configure". o - I ran "make install" as root, which moved the program to /usr/local/bin/xemacs. o - I put the sumo tarball in /usr/local/lib/xemacs as instructed by the FM and gunzipped and tar -xf'd it there. o - load-path is ("/usr/local/share/xemacs/site-lisp/" "/usr/local/share/xemacs-21.5-b31/lisp/") Why does this not work? Why can I not find the name of the variable holding the pertinent directory? Why can I find no documentation about how the package system works? I've tried C-h v'ing just about every variable starting "package-", and none of them fits the bill. Why does the doc string for packages-load-path-depth not mention where it is going deep from? This is frustrating. Thanks in advance for the help. -- Alan Mackenzie (Nuremberg, Germany). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

10 participants
22 comments

Re: trying to figure out alternative cut and paste (Eric S. Johansson) 13 years, 3 months

steven Mitchell

Eric, I'm not sure of all of what you said since I have never used Naturally Speaking, but I do know that the method of copy/paste used by windows is known by the name CUA. There is a cua-mode for XEmacs, I quickly searched google for XEmacs and CUA and found one link to a copy of the cua-mode for XEmacs: http://ftp.sa.xemacs.org/contrib/cua-mode.el I'm sure there are other places to get it too. Maybe that mode would change things the way you would like them. Another thought is that you can redefine the keyboard mapping to what suits you as well. Some keys like control-X which is used so much in XEmacs would be hard to redefine and still keep everything working. I wanted to redefine the copy/paste keys awhile back, so here is a fine that I wrote back then--maybe you could use it for an example to give you a leg up on getting your own desired layout working. Note the super key (windows key to left of spacebar) is not easily re-defined in Windows, so that would need changed someway for this exact code to work in windows. This code also highlights the block correctly too. Steve Mitchell -----------snip------------------------------------------------------------------------------------- ; skm-blocks.el ; Byrel and Steve Mitchell ; Nov 12, 2009 ; mark blocks by: ; same key for marking first and second block end markers ; once both ends marked, keys to copy, cut, move, & delete block ; ; Goal: ; to do all block commands: mark, copy, move, del, etc. with the left hand ; while the right hand used for positioning in buffer with cursor keys ; ; first written mimicing Vedit+ method (for right hand):: ; F9 to mark first end, ; F9 to mark second end, ; then Cntl-F9 (copy to cursor) or Alt-F9 (move to cursor) ; Vedit+ uses the delete key while block highlighted to delete block. Won't work here ; so we define a key with the same prefix (super) for deleting highlighted block ; ; possible improvements: ; add vars to choose how point (or cursor position or block markers) is moved when block { is copied, etc. ; that is, do these things move with the block, stay where they were was, : or move to end of new block, etc.? ; add function to unmark all block ends? ; currently marking a "third" end unmarks the 2 previously selected block ends ; and counts the third end as marking a new first-end-of-block ; find a name for this kind of block marking other than my intials. ; add functions to do columnar block marking (rectangles), with new key combinations. ; add vars to config how columnar block marking should work, insert, overwrite, etc. ; (defvar block-marker-highlight-mode 1 "block-marker-highlight-mode can have 3 values: 0 = highlighing is removed following a block copy or block move 1 = w/ a copy, orig block remains highlighted w/ a move, block is highlighted at new position 2 = w/ copy or move, block is highlighted at new position" ) (defvar block-marker-end-position-mode t "block-marker-end-position-mode has 2 values: t = after a block copy/move, cursor is positioned at end of inserted block nil = after a block copy/move, cursor is positioned at beginning of inserted block note: t is similar to the way Xemacs works by default") (defvar block-mark1 (point-marker)) ;var to hold 1st end of our block (defvar block-mark2 (point-marker)) ;var to hold 2nd end of our block (defvar block-ends-marked 0) ;0 if no ends marked, ;1 or 2 for number of ends marked (defvar block-copiedp nil) ;t if block copied ;-------- mark-block -------------------------- (defun mark-block () "Marks either end of block with skm type blocks." (interactive) (if ( or (eq block-ends-marked 0 ) (eq block-ends-marked 2)) ;are we marking the first end of a block? (progn (setq block-mark1 (point-marker)) (setq block-ends-marked 1) (clear-highlighting ) (set-mark-command nil)) ;starts highlighting ( if (eq block-ends-marked 1) ; if there is 1 block marker already, we are marking the second end. (progn (setq block-mark2 (point-marker)) (setq block-ends-marked 2) (highlight-region ) ))) ) ;-------- copy-block-to-point ----------------- (defun copy-block-to-point () "Copies skm-marked block to cur. cursor pos. " (interactive) (let ((start-pos (point))) (if ( < block-ends-marked 2) (message "Both ends not marked: %d end(s) marked." block-ends-marked ) ;error if there aren't 2 ends marked (save-excursion (set-buffer (marker-buffer block-mark1)) (copy-to-register ?c block-mark1 block-mark2)) (insert-register ?c t) (setq block-copiedp t) (let ((end-pos (point))) (if (eq block-marker-highlight-mode 0) ;0 = clear all highlighting (clear-highlighting-at-point ( marker-buffer block-mark1) block-mark1) (if (eq block-marker-highlight-mode 2 ) ;2 = highlight at new position (progn (clear-highlighting-at-point ( marker-buffer block-mark1) block-mark1) (goto-char start-pos) (push-mark) (goto-char end-pos) (highlight-region)))))) (if (not block-marker-end-position-mode) ;determine where to leave cursor (goto-char start-pos)) )) ;-------- move-block-to-point ----------------- (defun move-block-to-point () "Moves skm-marked block to current cursor pos. " (interactive) (if ( < block-ends-marked 2) (message "Both ends not marked: %d end(s) marked." block-ends-marked ) (save-excursion (set-buffer (marker-buffer block-mark1)) (copy-to-register ?c block-mark1 block-mark2 t)) (let ((start-pos (point)) end-pos ) (insert-register ?c t) (setq end-pos (point)) (setq block-copiedp t) (clear-highlighting-at-point ( marker-buffer block-mark1) block-mark1) (if (eq block-marker-highlight-mode 0) ;0 = clear all highlighting nil (goto-char start-pos) (push-mark) (goto-char end-pos) (highlight-region)) (if (not block-marker-end-position-mode) ;determine where to leave cursor (goto-char start-pos)) ))) ;-------- cut-block --------------------------- (defun cut-block () "Cuts skm-marked block from file." (interactive) (if ( < block-ends-marked 2) (message "Both ends not marked: %d end(s) marked." block-ends-marked ) (copy-to-register ?c block-mark1 block-mark2 t) (setq block-copiedp t))) ;------- highlight a block persistantly ----------- (defun highlight-region () (interactive) (let (new-extent) (setq new-extent (make-extent (mark t) (point))) (set-extent-property new-extent 'face 'zmacs-region) (set-extent-property new-extent 'wordstar-block t))) ;------- clear the highlighted blocks in a buffer ----------- (defun clear-highlighting-whole-buffer (&optional buffer) (interactive) (let ((highlighted-list (extent-list buffer nil nil nil 'face 'zmacs-region))) (while highlighted-list (delete-extent (car highlighted-list)) (setq highlighted-list (cdr highlighted-list))))) (defun clear-highlighting-at-point (&optional buffer position) (interactive) (if (not position) (setq position (point))) (while (extent-at position buffer 'wordstar-block nil 'at ) (delete-extent (extent-at position buffer 'wordstar-block nil 'at )) )) ;------------key assignments ------------------ ;--- key assignments to mimic VEdit+ method ;--- to verify we have algorithm correct (global-set-key [ f9 ] 'mark-block) (global-set-key [ (control f9) ] 'copy-block-to-point) (global-set-key [ (meta f9) ] 'move-block-to-point) (global-set-key [ (control meta f9) ] 'cut-block) ;not in Vedit, but for testing (global-set-key [ (control shift f9) ] 'clear-highlighting) ;not in Vedit, but for testing ;------- key assignments for left hand use ;--- using only super key (left windows-logo key) shifting ;Doesn't work with xemacs in Windows since Windows preempts the super key ; have to experiment to find something to work for windows' xemacs... (global-set-key [ (super space) ] 'mark-block) (global-set-key [ (super v) ] 'copy-block-to-point) ;mnemonic: V for insert, drive a V (wedge) in (global-set-key [ (super m) ] 'move-block-to-point) ;mnemonic: M for move (global-set-key [ (super c) ] 'cut-block) ;mnemonic: C for Cut (global-set-key [ (super n) ] 'clear-highlighting-at-point) ;mnemonic: think N for No highlighting _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

5 participants
5 comments

Re: Problem with mule-tests when run by build-slaves 13 years, 3 months

Aidan Kehoe

Ar an t-ochtú lá de mí Lúnasa, scríobh Mats Lidell: > Aidan Kehoe writes 2011-08-08 10:53: > > Basically, the korea-util.el in core has bugs that the korea-util.el in > > the packages does not. The former is picked up by the buildbot, the > > latter when running manually--this is one of the load-path shadows the > > build has been warning us about for years. > > I think the core unit tests should not use the packages at all. Maybe > the load-path should just be nil when running the core unit tests if > that is possible. I disagree. I think the core unit tests should not need the packages, in the same way they don’t need the tac and cat executables (see os-tests.el), but it’s reasonable for them to use them if they are available. > > [...] And do similar things for the other *-util.el mule > > files that are shadowed by package files. > > Yes but if the functionality is in core why do we need the package or > vice versa. It is strange to have it in both places. What am I missing? You’re not missing anything. We need some of the content of korea-util.el in core, but the file itself should not be there. -- ‘Iodine deficiency was endemic in parts of the UK until, through what has been described as “an unplanned and accidental public health triumph”, iodine was added to cattle feed to improve milk production in the 1930s.’ (EN Pearce, Lancet, June 2011) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Problem with mule-tests when run by build-slaves 13 years, 3 months

Stephen J. Turnbull

Mats Lidell writes: > The core tests should not depend on functionality in the packages. Sure, I accept that as a principle. I'm not going to do anything about it, though, unless somebody's willing to guarantee me an income of USD 100,000 for five years. Otherwise I need to keep my day job. ;-) [...] > Now, this is not the problem here. The unit tests that clearly indicates > that the core functionality is broken are fixed by a package. That's a bug in the core, then. Let's fix it. > It only shows up in the buildbot since no packages are installed > there. That is also a bug in core. There is a missing package-suppress form, which would make it show up for the developers, too. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Can one put a function into function-key-map? 13 years, 3 months

Aidan Kehoe

Ar an triú lá de mí Lúnasa, scríobh Alan Mackenzie: > [...] This extension makes an Emacs usable on the Linux console. The > complete files are too big to post here, but if you're interested enough, > I could email them to you. Please do, or as Stephen suggested, add them as attachments to a tracker issue. -- ‘Iodine deficiency was endemic in parts of the UK until, through what has been described as “an unplanned and accidental public health triumph”, iodine was added to cattle feed to improve milk production in the 1930s.’ (EN Pearce, Lancet, June 2011) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Summary of XEmacs Issue Tracking System Issues 13 years, 3 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2011-08-02 - 2011-08-09) XEmacs Issue Tracking System at http://tracker.xemacs.org/XEmacs/its/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 542 open ( +5) / 251 closed ( +0) / 793 total ( +5) Open issues with patches: 12 Average duration of open issues: 901 days. Median duration of open issues: 983 days. Open Issues Breakdown new 204 ( +4) deferred 6 ( +0) napping 4 ( +0) verified 54 ( +0) assigned 153 ( +0) committed 29 ( +0) documented 3 ( +0) done/needs work 24 ( +0) Issues Created Or Reopened (5) ______________________________ NSCreateObjectFileImageFromFile is deprecated 2011-08-03 http://tracker.xemacs.org/XEmacs/its/issue791 created stephen Syntax table documentation is deficient 2011-08-04 http://tracker.xemacs.org/XEmacs/its/issue792 created stephen List of text properties respected by core needs update in Lisp 2011-08-04 http://tracker.xemacs.org/XEmacs/its/issue793 created stephen No Mule guidance in installation instructions 2011-08-05 http://tracker.xemacs.org/XEmacs/its/issue794 created andersjm Re: Problem with forward-sexp. 2011-08-07 http://tracker.xemacs.org/XEmacs/its/issue795 created stephen Issues Now Closed (1) _____________________ [Bug: 21.5-b31] Sub-process fails in ginger/Cygwin native 67 days http://tracker.xemacs.org/XEmacs/its/issue768 HThompson _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: Impossible to commit to packages 13 years, 3 months

Aidan Kehoe

Ar an naoiú lá de mí Iúil, scríobh Michael Sperber: > They finally got back to me: > > cvs.alioth.debian.org offers only read-only access per design, > apparently. We're now supposed to use > > cvs.debian.org > > Seems to work for me ... Not here. Are you sure you’re trying to commit? bonbon [ cat mule-packages/leim/CVS/Root :ext:sperber-guest＠cvs.debian.org:/cvs/xemacs bonbon [ cvs commit -m 'Sync some changes to the IPA input methods from GNU.' mule-packages/leim/ChangeLog mule-packages/leim/leim-list.el mule-packages/leim/quail/ipa-21.5.el Can't do setuid (cannot exec sperl) cvs commit: Pre-commit check failed Can't do setuid (cannot exec sperl) cvs commit: Pre-commit check failed cvs [commit aborted]: correct above errors first! bonbon [ -- ‘Iodine deficiency was endemic in parts of the UK until, through what has been described as “an unplanned and accidental public health triumph”, iodine was added to cattle feed to improve milk production in the 1930s.’ (EN Pearce, Lancet, June 2011) _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Fwd: [Python-mode] xemacs Potential problem 13 years, 3 months

Eric S. Johansson

should have sent this here as well. -------- Original Message -------- Subject: [Python-mode] xemacs Potential problem Date: Mon, 08 Aug 2011 20:43:53 -0400 From: Eric S. Johansson <esj(a)harvee.org> To: python-mode(a)python.org I'm experimenting with the latest beta and try to figure out what's the right set of options for configure for production version and I got this error. Any ideas? (1) (file-mode-spec/warning) Error in File mode specification: Malformed list: :background Backtrace follows: backtrace(nil t) # bind (standard-output standard-output handler-arg-name) backtrace-in-condition-handler-eliminating-handler(call-trapping-errors-Ldc9FC5Hr) # bind (errstr call-trapping-errors-Ldc9FC5Hr) #<compiled-function (from "/home/esj/xemacs-beta/lisp/files.elc") (call-trapping-errors-Ldc9FC5Hr) "...(17)" [call-trapping-errors-Ldc9FC5Hr errstr error-message-string lwarn file-mode-spec warning "Error in %s: %s\n\nBacktrace follows:\n\n%s" "File mode specification" backtrace-in-condition-handler-eliminating-handler] 8 0x694>((malformed-list :background)) apply(face-custom-attributes-set highlight-indent-face nil (custom) :background) # bind (display atts tags frame spec face) face-display-set(highlight-indent-face ((((class color) (min-colors 88) (background dark)) :background "grey22") (((class color) (min-colors 88) (background light)) :background "grey88")) nil (custom)) # bind (value frames frame args doc spec face) custom-declare-face(highlight-indent-face ((((class color) (min-colors 88) (background dark)) :background "grey22") (((class color) (min-colors 88) (background light)) :background "grey88")) "Basic face for highlighting indentation guides." :group basic-faces) (defface highlight-indent-face (quote ((((class color) (min-colors 88) (background dark)) :background "grey22") (((class color) (min-colors 88) (background light)) :background "grey88"))) "Basic face for highlighting indentation guides." :group (quote basic-faces)) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) (load-internal "[internal]") load-internal("highlight-indentation" nil require nil undecided) # bind (handler path nosuffix nomessage noerror filename) load("highlight-indentation" nil require nil) # (unwind-protect ...) require(highlight-indentation) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) (load-internal "[internal]") load-internal("python-mode" nil nil nil undecided) # bind (handler path nosuffix nomessage noerror filename) load("python-mode" nil nil nil) # (unwind-protect ...) python-mode() # bind (alist mode name keep-going) # (unwind-protect ...) # bind (just-from-file-name) set-auto-mode() #<compiled-function (from "/home/esj/xemacs-beta/lisp/files.elc") nil "...(5)" [set-auto-mode t] 1 0x695>() # (unwind-protect ...) call-with-condition-handler(#<compiled-function (from "/home/esj/xemacs-beta/lisp/files.elc") (call-trapping-errors-Ldc9FC5Hr) "...(17)" [call-trapping-errors-Ldc9FC5Hr errstr error-message-string lwarn file-mode-spec warning "Error in %s: %s\n\nBacktrace follows:\n\n%s" "File mode specification" backtrace-in-condition-handler-eliminating-handler] 8 0x694> #<compiled-function (from "/home/esj/xemacs-beta/lisp/files.elc") nil "...(5)" [set-auto-mode t] 1 0x695>) # (condition-case ... . ((error))) # bind (find-file) normal-mode(t) # bind (nomodes after-find-file-from-revert-buffer noauto warn error) after-find-file(nil t) # (unwind-protect ...) # bind (inhibit-read-only error number truename rawfile nowarn filename buf) find-file-noselect-1(#<buffer "food_calc.py"> "/home/esj/food/food_calc.py" nil nil "c:/cygwin/home/esj/food/food_calc.py" (361450 -22488999)) byte-code("..." [number truename rawfile nowarn filename buf set-buffer-major-mode find-file-noselect-1] 7) # (condition-case ... . ((t (byte-code "Â!Ã ＠ A\"" [buf data kill-buffer signal] 3)))) # bind (number truename buf wildcards rawfile nowarn filename) find-file-noselect("~/food/food_calc.py" nil nil t) # bind (coding-system-for-read wildcards codesys filename) #<compiled-function (from find-file) (filename&optional codesys wildcards) "...(37)" [wildcards filename coding-system-for-read thunk value codesys check-coding-system find-file-noselect nil #<compiled-function (from "/home/esj/xemacs-beta/lisp/files.elc") (buffer) "...(21)" [buffer buffer-file-name file-exists-p set-buffer-modified-p t switch-to-buffer] 3 0x67b> mapcar] 5 1247230 (list (read-file-name "Find file: ") (and current-prefix-arg (read-coding-system "Coding system: ")) t) 0x67c>("~/food/food_calc.py" nil t) call-interactively(find-file) (dispatch-event "[internal]") # (condition-case ... . error) # (catch top-level ...) _______________________________________________ Python-mode mailing list Python-mode(a)python.org http://mail.python.org/mailman/listinfo/python-mode _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

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 August 2011