October 2017 - XEmacs-Beta - XEmacs Mailing List Archives

Including "vc-fossil.el" in vc? 5 years, 7 months

Hauke Fath

Hi, I nave been banging a bit on vc-fossil.el from <http://chiselapp.com/user/venks/repository/emacs-fossil/doc/tip/doc/index...>, and got it to work with Xemacses "slightly-older vc. Provided there is interest: What would be the procedure to include the fuke with the XEmacs vc? Cheerio, hauke -- The ASCII Ribbon Campaign Hauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344

2 participants
4 comments

is speed a concern? 5 years, 10 months

Julian Bradfield

Another possibly silly question arising from perusal of the great Mule merge... Is speed (or small linear factors in memory) ever actually a concern nowadays? The whole deal of supporting multiple internal buffer formats seems to be justified by speed for multi-lingual processing, and there are various tricky things scattered around the rest of the code to improve speed. The last time I can remember being disturbed by XEmacs' slowness was sometime in the mid 90s when I was running Lucid Emacs 19 on a 68040. (The days when a full compile was a go-out-for-long-dinner job rather than a you-may-just-have-time-to-make-coffee job.) On the other hand, I don't do extensive non-English processing. Do people find XEmacs noticeably slow in any normal usage pattern? -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

6 participants
9 comments

Summary of XEmacs Issue Tracking System Issues 7 years

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-10-24 - 2017-10-31) 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. 574 open ( +0) / 323 closed ( +0) / 897 total ( +0) Open issues with patches: 13 Average duration of open issues: 2943 days. Median duration of open issues: 3154 days. Open Issues Breakdown new 266 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

Summary of XEmacs Issue Tracking System Issues 7 years, 1 month

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-10-17 - 2017-10-24) 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. 574 open ( +0) / 323 closed ( +0) / 897 total ( +0) Open issues with patches: 13 Average duration of open issues: 2936 days. Median duration of open issues: 3147 days. Open Issues Breakdown new 266 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

Summary of XEmacs Issue Tracking System Issues 7 years, 1 month

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-10-10 - 2017-10-17) 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. 574 open ( +0) / 323 closed ( +0) / 897 total ( +0) Open issues with patches: 13 Average duration of open issues: 2929 days. Median duration of open issues: 3140 days. Open Issues Breakdown new 266 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

Buildbot down due to maintenance 7 years, 1 month

Mats Lidell

Hi, I have been forced to take down the buildbot for maintenance. I hope to get it up during the week but no promises I'm afraid. Yours -- %% Mats

2 participants
2 comments

21.4.6 hangs on X11 clipboard on HP-UX 10.20 7 years, 1 month

Gary Beckmann

Periodically, xemacs will "hang" (stop taking input, not refresh screen). When killed, the back traces look like: Lisp backtrace follows: own-selection-internal(CLIPBOARD "\n" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("\n" CLIPBOARD) # bind (push string) own-clipboard("\n" t) # bind (replace string) kill-new("\n") # bind (undo-high-threshold tail verbose end start) kill-region(558 559) # bind (entire-line arg) kill-line-1(nil nil) # bind (arg) kill-line(nil) # bind (command-debug-status) call-interactively(kill-line) # (condition-case ... . error) # (catch top-level ...) Lisp backtrace follows: own-selection-internal(CLIPBOARD "xemacs-beta-request(a)xemacs.org" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("xemacs-beta-request(a)xemacs.org" CLIPBOARD) # bind (push string) own-clipboard("xemacs-beta-request(a)xemacs.org" t) # bind (replace string) kill-new("xemacs-beta-request(a)xemacs.org") # bind (end start) copy-region-as-kill(403374 403404) # bind (end start) kill-ring-save(403374 403404) # bind (command-debug-status) call-interactively(kill-ring-save) # (condition-case ... . error) # (catch top-level ...) Lisp backtrace follows: own-selection-internal(CLIPBOARD "xemacs-beta-request(a)xemacs.org" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("xemacs-beta-request(a)xemacs.org" CLIPBOARD) # bind (push string) own-clipboard("xemacs-beta-request(a)xemacs.org" t) # bind (replace string) kill-new("xemacs-beta-request(a)xemacs.org") # bind (end start) copy-region-as-kill(403374 403404) # bind (end start) kill-ring-save(403374 403404) # bind (command-debug-status) call-interactively(kill-ring-save) # (condition-case ... . error) # (catch top-level ...) Lisp backtrace follows: own-selection-internal(CLIPBOARD "src/" nil nil) # bind (zmacs-region-stays data-type how-to-add type data) own-selection("src/" CLIPBOARD) # bind (push string) own-clipboard("src/" t) # bind (replace string) kill-new("src/") # bind (undo-high-threshold tail verbose end start) kill-region(27 23) # bind (count) kill-word(-1) # bind (count) backward-kill-word(1) # bi: gary＠rules[19] ; nd (command-debug-status) call-interactively(backward-kill-word) # (condition-case ... . error) # (unwind-protect ...) read-minibuffer-internal("Find file: ") byte-code("..." [standard-output standard-input prompt recursion-depth minibuffer-depth t read-minibuffer-internal] 2) # (catch exit ...) # bind (mouse-grabbed-buffer current-prefix-arg minibuffer-history-variable minibuffer-history-position minibuffer-scroll-window) # (unwind-protect ...) # bind (minibuffer-default _history_ oconfig mconfig frame buffer window oframe owindow dir default abbrev-table history readp keymap initial-contents prompt) read-from-minibuffer("Find file: " "~/cdev/RSAcore/dev/se/src/" #<keymap read-file-name-map size 2 0xd3c> nil file-name-history nil "~/cdev/RSAcore/dev/se/src/sePTVMgr.cxx") # bind (minibuffer-completion-table minibuffer-completion-predicate minibuffer-completion-confirm last-exact-completion insert completer initial-contents must-match default dir prompt history) read-file-name-2(file-name-history "Find file: " nil "~/cdev/RSAcore/dev/se/src/sePTVMgr.cxx" nil nil read-file-name-internal) # bind (completer initial-contents must-match default dir prompt history type) read-file-name-1(file file-name-history "Find file: " nil "~/cdev/RSAcore/dev/se/src/sePTVMgr.cxx" nil nil read-file-name-internal) # bind (history initial-contents must-match default dir prompt) read-file-name("Find file: " nil nil nil) call-interactively(find-file) # (condition-case ... . error) # (catch top-level ...) That's four of them. They all have in common the kill-new function. Has anyone else seen this? Any ideas what I can try? OS: HP-UX 10.20 compiled with HP's Ansi C compiler Motif 1.2 (from HP). gary

4 participants
3 comments

RE: (SPF_HELO_SOFTFAIL) (SPF_SOFTFAIL) RE: qxe generation problem 7 years, 1 month

Benson Margulies

Sure. -----Original Message----- From: Ben Wing [mailto:ben＠xemacs.org] Sent: Sunday, November 26, 2006 7:22 AM To: Benson Margulies Cc: Stephen J. Turnbull; XEmacs-Beta(a)xemacs.org Subject: Re: (SPF_HELO_SOFTFAIL) (SPF_SOFTFAIL) RE: qxe generation problem Benson Margulies wrote: > I successfully added --includedir of PlatformSDK/include, and ran it > from a shell in cygwin. I didn't try to automate this for use in a > Makefile or NMAKE file. > > -----Original Message----- > From: Stephen J. Turnbull [mailto:stephen＠xemacs.org] > Sent: Saturday, November 25, 2006 6:20 AM > To: Benson Margulies > Cc: Ben Wing; XEmacs-Beta(a)xemacs.org > Subject: qxe generation problem > > Benson Margulies writes: > > > The QXE generator assumes a directory structure that no longer > applies > > in VC7. The Win32 SDK files are no longer in the compiler include > > directory. They are in the platform SDK. If all the files you want > are > > in Win32, then passing --includedir can do the job. Otherwise, more > > complexity is called for. > > Ben (Wing), any comments? If you don't have upgraded code for VC7 to > commit at this point, I'd like to tell Benson to do what he needs to > do, and we can deal with the merge later. > > Benson, this looks great. could you possibly fix up the NMAKE file (nt/xemacs.mak)? Basically, add a HAVE_VC7 just like the existing HAVE_VC6, and default it to 1. then modify the rule for unicode-encapsulate so it's conditionalized appropriately: something like unicode-encapsulate: cd $(SRC) ! if $(HAVE_VC7) perl ../lib-src/make-mswin-unicode.pl --includedir PlatformSDK/include --c-output intl-auto-encap-win32.c --h-output intl-auto-encap-win32.h intl-encap-win32.c ! else perl ../lib-src/make-mswin-unicode.pl --c-output intl-auto-encap-win32.c --h-output intl-auto-encap-win32.h intl-encap-win32.c ! endif [mind the tab damage, etc] _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta

3 participants
7 comments

Summary of XEmacs Issue Tracking System Issues 7 years, 1 month

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2017-10-03 - 2017-10-10) 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. 574 open ( +0) / 323 closed ( +0) / 897 total ( +0) Open issues with patches: 13 Average duration of open issues: 2922 days. Median duration of open issues: 3133 days. Open Issues Breakdown new 266 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 57 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0)

1 participants
0 comments

Why isn't packages/xemacs-packages/psgml/etc/cdtd in CVS? 7 years, 1 month

Stephen J. Turnbull

It seems that packages/xemacs-packages/psgml/etc/cdtd/.cvsignore _is_ in CVS, which causes cdtd to get created, but then after that I always get a move away xemacs-packages/psgml/etc/cdtd/.cvsignore; it is in the way message. -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN My nostalgia for Icon makes me forget about any of the bad things. I don't have much nostalgia for Perl, so its faults I remember. Scott Gilbert c.l.py

4 participants
5 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 October 2017