December 2012 - XEmacs-Beta - XEmacs Mailing List Archives

editres patch (was: background pixmaps) 11 years, 11 months

steven Mitchell

It's not super-important, but I'd like to understand why this patch fixes things. You are talking about the editres patch Benson found, right? I noticed it was for a 1.0.3 version of editres IIRC, not the latest 1.0.5. I agree--that I would like to understand why this fixes things. Latest steps we did here: 1. system with old editres, didn't work. 2. applied patch and recompiled 3. now it works. 4. to double-check, remove patch, and recompile. 5. check again, and old copy of editres works. (but shouldn't as the patch is gone, double checked to be sure) Am I to think the patch is not making it happen, but the patching/recompiling process is???? So what exactly could about the patching process makes a difference (on two different Linux distributions, so far) I hope somebody can figure out what exactly did fix it. Steve _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

editres patch (was: background pixmaps) 11 years, 11 months

Charles Waldman

It's not super-important, but I'd like to understand why this patch fixes things. For example, consider this change: - sprintf(msg, res_labels[14]); + sprintf(msg, "%s", res_labels[14]); res_labels[14] is initialized (from the app-defaults file) to the string "Click on any widget in the client.\nEditres will select that widget in the tree display." This string has no '%' characters in it. Shouldn't sprintf(buf, "%s", STRING) do the same thing as sprintf(buf, STRING) provided that STRING has no '%' characters in it? _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

subsetp gives wrong result 11 years, 11 months

steven Mitchell

Benson and I were trying to use subsetp and getting wrong results. subsetp is supposed to take two lists and check all the elements of the first list are contained in the second list. (subsetp (list ?a) (list ?a ?b ?c ?d)) returns t (subsetp (list ?a ?b) (list ?a ?b ?c ?d)) returns t (subsetp (list ?a) nil) returns (?a) But should return nil. (subsetp nil (list ?a ?b ?c ?d)) returns t (subsetp nil nil ) returns nil but should return t Attached is a patch that fixes both wrong cases. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
3 comments

finding the function mark-c-function 11 years, 11 months

steven Mitchell

On the menu, Edit-->Mark-->C Function references mark-c-function as what it runs. C-H k then clicking on the menu item gives this error: Symbol's function definition is void: mark-c-function I tried getting help with C-h k, then C-M h and it says it runs mark-defun instead, which is the command for marking a lisp function. running grep I only find the text "mark-c-function" inside 2 files out of all xemacs source files, both of them document files, and no references to it in the source code itself. grep mark-c-function /usr/src/ -r /usr/src/xemacs-21.5.32/man/xemacs/programs.texi:＠code{mark-c-function}, which is almost the same as ＠code{mark-defun}, /usr/src/xemacs-21.5.32/info/xemacs.info-2:`mark-c-function', which is almost the same as `mark-defun', but which Has the mark-defun been updated so that it covers what mark-c-function used to do and it is not needed now? In which case the 2 files that reference it should be updated to not reference it?, Or is there some other explanation? Steve M. I tried in both C mode and lisp mode and C-M-h works, I just want to use the function in some lisp code I'm working on. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

background pixmaps 11 years, 11 months

Benson Mitchell

I'm using Arch, and editres works on xemacs. Poking at slackware's source dir, it becomes apparent that they're building from the exact same editres source tar (1.0.5), but slackware builds unpatched, while we use a single patch. I've attached the patch, but for reference, it can be retrieved from the tarball at: https://aur.archlinux.org/packages/xo/xorg-editres/xorg-editres.tar.gz I tried running my editres against Steve's xemacs (via X forwarding his xemacs to my box) and it worked fine, so the problem doesn't seem to be in xemacs. I'd try building editres with that patch, see if it fixes it... Could also be due to shared library versions, though. Benson _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
2 comments

Summary of XEmacs Issue Tracking System Issues 11 years, 11 months

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2012-12-11 - 2012-12-18) 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. 556 open ( +0) / 290 closed ( +0) / 846 total ( +0) Open issues with patches: 13 Average duration of open issues: 1309 days. Median duration of open issues: 1390 days. Open Issues Breakdown new 229 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 56 ( +0) assigned 153 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 18 ( +0) Issues Now Closed (1) _____________________ Filter out non-dev users 1802 days http://tracker.xemacs.org/XEmacs/its/issue5 dani70ce _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

XFT fonts [was: build failure on Ubuntu 12.04.1] 11 years, 11 months

Charles Waldman

I'm still trying to get a working, current XEmacs on Ubuntu (first time using this distro). XFT support is a key feature for me - if I'm going to look at a screen full of code all day, it better look nice! I configured --with-xft, installed a whole bunch of fonts, but none of them seem to be available, either via the command-line "-font" flag, or through the options menu. In fact the Options/Font menu shows lots and lots of fonts, but they are all greyed out ... screen shot here - http://cgw.placeholderdomains.net/xemacs-font-menu.png All of the font names are similarly greyed-out, but the two radio buttons for "DejaVu Sans Mono" are selected. This is running with '-q' and no X resources. Any clue what I'm doing wrong here? Thanks! _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

10 participants
35 comments

list-registers, errors 11 years, 11 months

steven Mitchell

I'm trying to use the list-register command out of register.el. I set some registers to contain values: (set-register ?a "register a" ) (set-register ?b "register b" ) (set-register ?c "register c" ) (set-register ?d "register d" ) evaling each with C-x C-e after the close paren on that line. I can verify that the values are correct this way: (view-register ?a ) (view-register ?b ) (view-register ?c ) (view-register ?d ) But when I run the command (list-registers) I get various errors: wrong argument type: number-char-or-marker-p, "a" But I didn't give it the string "a", I gave it char a ?a. so what type is it expecting? or it gives me a buffer *output* with the words: Register a contains then the following error in the minibuffer: Invalid regexp: "Invalid content of \\{\\}" putting debug on error on, from the menu, gives this backtrace: Debugger entered--Lisp error: (invalid-regexp "Invalid content of \\{\\}") string-match("[^ \n].\\{,20\\}" "register a") describe-register-1(?a) (progn (describe-register-1 (car elt)) (terpri)) (if (get-register (car elt)) (progn (describe-register-1 ...) (terpri))) (while #:G34812 (setq elt (car #:G34812)) (if (get-register ...) (progn ... ...)) (setq #:G34812 (cdr #:G34812))) (let ((#:G34812 list) elt) (while #:G34812 (setq elt ...) (if ... ...) (setq #:G34812 ...))) (catch (quote #:nil) (let (... elt) (while #:G34812 ... ... ...))) (block nil (let (... elt) (while #:G34812 ... ... ...))) (dolist (elt list) (when (get-register ...) (describe-register-1 ...) (terpri))) (with-output-to-temp-buffer "*Output*" (dolist (elt list) (when ... ... ...))) (let ((list ...)) (setq list (sort* list ... :key ...)) (with-output-to-temp-buffer "*Output*" (dolist ... ...))) list-registers() eval((list-registers)) eval-interactive((list-registers)) eval-last-sexp(nil) call-interactively(eval-last-sexp) (dispatch-event "[internal]") I assume the string-match is where it is failing and that is part either of the sort* (when the error was wrong type) or part of the describe-register function (when the error is invalid regex). the code for list-registers is short: ---from /usr/src/xemacs-21.5.32/lisp/register.el (defun list-registers () "Display a list of nonempty registers saying briefly what they contain." (interactive) (let ((list (copy-sequence register-alist))) (setq list (sort* list #'< :key #'car)) (with-output-to-temp-buffer "*Output*" (dolist (elt list) (when (get-register (car elt)) (describe-register-1 (car elt)) (terpri)))))) I looked up the sort* function, and understand the list that will be sorted in place, and the :key is to tell what field to base the sort on, the car of each list item, so sorting by register name here, I think, but do not comprehend the predicate in the middle: #'< Does the less than mean do an ascending or descending sort? I haven't found a list in the manuals of what is allowed for the predicate of sort*. Any ideas? Steve M. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

4 participants
10 comments

background pixmaps 11 years, 11 months

steven Mitchell

I can set a background pix-map in the default face, and it works fine. When I set a background pixmap in the face for any of the: Menubar Toolbar Tabbar it does not work. No errors, just doesn't show the pix-map on the screen. It *does* change the preview box in the customize face buffer, the sample does indeed have the correct background shown for all three faces for the tabbar, toolbar, and menubar. So something at least is recognizing my pix-map--just not on the screen. Any idea what I have to do to get a background pixmap to work in those three areas? Steve M. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

7 participants
25 comments

Re: background pixmaps 11 years, 11 months

Jerry James

On Thu, Dec 13, 2012 at 10:11 AM, steven Mitchell <smitchel(a)bnin.net> wrote: > Jerry, > I'm using Slackware64 14.0. > > Is your Fedora version 64 bit? Yes. > Which version? Fedora 17. -- Jerry James http://www.jamezone.org/ _______________________________________________ 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 December 2012