Hi.
When I start xemacs I get 20 times or so the following kernel messages:
Mar 24 15:56:32 computer kernel: [ 1565.560842] ioctl32(xemacs21-nomule:5715): Unknown cmd fd(5) cmd(0000530a){t:'S';sz:0} arg(ffd6b35c) on socket:[46842]
I use a 64 bit kernel but a 32 bit system, don't know whether that's
related. Also don't know, whether these messages are related to my
crashes cf. <878vwnx7b7.fsf(a)debian.IGP> and <87oc5c5bm4.fsf(a)debian.IGP>
--
Omnis enim res, quae dando non deficit, dum habetur et non datur,
nondum habetur, quomodo habenda est.
Augustinus, De doctrina christiana
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
On Fri, 18 Mar 2011 15:11:42 +0100, Andreas wrote:
> I read the newsgroup, there the message is still available under the
> given ID. Under mid.gmane.org you can find it under
> 201103151352.18476.bss(a)iguanasuicide.net (But can you access the raw
> mail from there?)
Yes - by appending /raw to the URL:
* http://article.gmane.org/gmane.linux.debian.user/403780/raw
Best regards,
Adam
--
"Ge mig en vinterdrog, ge mig allt du har Adam Sjøgren
Kom nu jag är kroniskt låg, bara mörkret hörs" asjo(a)koldfront.dk
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello,
I am running Slackware64 13.1 and XEmacs 21.4.22.
XEmacs was working just fine for months.
I installed E17 as the window manager instead of KDE 4.6.0.
All Xwindows apps work fine, but not XEmacs. Sigh.
A window comes up, has my XEmacs coloring and menus, but the right side
of the window is white, say 40% of screen width wide, and %100 high.
What is cut off is not the title bar (with minimize, maximize, and
close), but everything below it, the menu (no help button on right)
all text area, status bar at the bottom, and right end of minibuffer
is just white.
XEmacs seems to come up in two stages, a smaller window for a blink of
an eye, then the full size window. This might be because of the
set-frame-size command in my init.el to resize the window on startup:
(set-frame-size (window-frame) 140 80) ;--size window for 30" monitor.
If I execute the above command with larger or smaller values then
control-x control-e, The window narrows or widens, but the left hand
area that shows correctly does not change, just shows more or less of
the white area.
Grabbing the upper left corner with the mouse, I can resize the window
smaller or bigger and the symptom's remain the same. as the window gets
narrower, the white area shrinks, but resizing bigger restores the white
area.
However, when I grab the upper right corner to resize it, as soon as
I begin to resize the window, the white goes away and "help" on menu is
back and fullwidth status bar and minibuffer are back too. I just have
to move it a few pixels, too, and it fixes itself whether I go bigger
or smaller.
Is something not being updated on startup--that IS updated after a
resize? Can I workaround it by adding something to update the screen on
startup?
I installed 21.4.22 because I believed the warnings about 21.5 not being
stable yet, but came to understand that 21.4.22 code base is frozen, so
no non-serious bug fixes are made anymore. Does anyone know if
upgrading to the latest version would fix this problem? I installed
21.4.22 on all computers in my business thinking it was the latest
stable version, so it would be bit of work to upgrade them all (XP and
Slackware OS's) though I will, if someone is sure that would solve it.
Any ideas or things to try?
Steve Mitchell
PS I can take screenshots or a 10 second video to show this if someone
wants me too. It is repeatable every time.
Here is my init.el in it's entirety:
;--------------- SKM's init.el ----------------
;---- display extra items in status bar
(line-number-mode 1)
(column-number-mode 1)
(display-time)
;---- add recent files list to file menu
(load "recent-files")
(setq recent-files-menu-path '("File"))
(setq recent-files-add-menu-before "Exit XEmacs")
(recent-files-initialize)
;---- set printing to print in black and white
;(setq ps-default-fg nil)
;(setq ps-default-bg nil)
(setq ps-print-color-p nil)
(load-file "~/.xemacs/printer-setup.el")
;---- set window size for when program starts
(set-frame-size (window-frame) 140 80 )
;---- load file to get mouse scroll wheel working
(load-file "~/.xemacs/intellimouse.el")
;---- set path to where xemacs macros are stored
; typical for Linux systems: ~/xemacs_macros
; typical for Windows files: c:\xemacs_macros
(setq cnc-macro-path "~/xemacs_macros")
;---- load files for cnc macros that are in the menu
(load-file (concat cnc-macro-path "/swiss-print.el" ))
(load-file (concat cnc-macro-path "/refchart.el"))
(load-file (concat cnc-macro-path "/remove-spaces.el"))
(load-file (concat cnc-macro-path "/add-spaces.el"))
(load-file (concat cnc-macro-path "/removeCRCR.el"))
(load-file (concat cnc-macro-path "/cnc-mill-macro.el"))
(load-file (concat cnc-macro-path "/cnc-lathe-macro.el"))
;---- load CNC menu and put in menubar
(load-file (concat cnc-macro-path "/cncmenu.el"))
;---- set path for refchart's files
(setq cnc-refchart-path "~/xemacs_macros")
;---- define key to load cnc-mill-macro
(global-set-key [f12] 'cnc-mill-macro)
(global-set-key [f11] 'cnc-lathe-macro)
;----- set toolbar height for 64 pixel icons
;(set-specifier top-toolbar-height 72)
;----- turn off toolbar
(set-specifier top-toolbar-height (cons (selected-frame) 0))
;----- start up with a new buffer instead of scratch buffer
(switch-to-buffer (create-file-buffer "untitled.txt"))
;----- set some scrolling values
(setq
scroll-conservatively 10
scroll-step 2)
;(setq frame-title-format "%S: %f")
(load "big-menubar")
;----- set how many buffers are listed in buffer list
(setq buffers-menu-max-size 20)
;----- Add copy, paste, etc. to lisp-mode popup menu.
(setq emacs-lisp-mode-popup-menu
(cons "Emacs-Lisp"
(cons ["%_Undo" advertised-undo :active (and (not (eq
buffer-undo-list t)) (or buffer-undo-list pending-undo-list)) :suffix
(if (or (eq last-command (quote undo)) (eq last-command (quote
advertised-undo))) "More" "")]
(cons ["Cu%_t" kill-primary-selection :active (selection-owner-p)]
(cons ["%_Copy" copy-primary-selection :active (selection-owner-p)]
(cons ["%_Paste" yank-clipboard-selection :active
(selection-exists-p (quote CLIPBOARD))]
(cons ["%_Delete" delete-primary-selection :active
(selection-owner-p)]
(cons "---" (construct-lisp-mode-menu t t)))))))))
;---- define control-delete to delete current region
(global-set-key '(control delete) 'delete-primary-selection)
;---- define the left windows key and x to kill a line in Linux
(global-set-key '(super x) 'kill-entire-line)
;---- set size for file-open dialog on 30" monitor to see more files
(setq dialog-frame-plist (plist-put dialog-frame-plist 'width 120))
(setq dialog-frame-plist (plist-put dialog-frame-plist 'height 40))
;---- turn on complex buffer menu
(setq complex-buffers-menu-p t)
;---- load buffer colors menu
(load-file "~/xemacs_macros/buffer-colorize-menu.el")
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hello
Lately I use vc-annotate quite often with RCS.
I would find it very useful if from the vc-annotate buffer I
could jump directly to a specific line of the file.
Example I execute vc-annotate in the workfile version and I
obtain
2011-03-22 1.11: \input{aned10-header-beamer}
2011-03-22 1.5 : %\input{aned10-header-article}
So putting to cursor to the second line I would like to jump
to the line in the corresponding file (which happens to be
line number two of the file.)
Anybody know about such a function?
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
ACTIVITY SUMMARY (2011-03-15 - 2011-03-22)
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.
515 open ( +1) / 240 closed ( +0) / 755 total ( +1)
Open issues with patches: 11
Average duration of open issues: 810 days.
Median duration of open issues: 843 days.
Open Issues Breakdown
new 185 ( +1)
deferred 6 ( +0)
napping 4 ( +0)
verified 51 ( +0)
assigned 155 ( +0)
committed 25 ( +0)
documented 2 ( +0)
done/needs work 24 ( +0)
Issues Created Or Reopened (1)
______________________________
Implement `display-color-cells' for TTYs 2011-03-19
http://tracker.xemacs.org/XEmacs/its/issue757 created stephen
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
The commit mails are not coming anymore. (Automatic mails sent from
mercurial on the commit. Subject line starts with "commit: ".) The
buildbot wants to have them. What is up?
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Didier Verna <didier(a)xemacs.org> writes:
> I wrote:
>
>> Is there a way to tell HG *not* to push closed branches, or even
>> better, how can I simply eradicate the old branch from my repo ?
>
> hg strip is the answer to question #2. Question #1 holds though.
hg push -rtip
ought to do the job. ("push" and "pull" are operations on (entire)
repositories - they have nothing to do with the state of the working
directory.)
--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
Hi,
After consulting the XEmacs INSTALL and PROBLEM files, I am unable to
proceed with building XEmacs on an AIX machine.
My ulimits:
% ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 4000000
stack(kbytes) 4000000
memory(kbytes) 4000000
coredump(blocks) 100000
nofiles(descriptors) unlimited
% uname -a
AIX c2n6 3 5 00C885E24C00 powerpc unknown AIX
I've recompiled XEmacs code with the following settings/flags in an attempt
to get more information:
CC=xlc_r
./configure --with-gcc=no --error-checking=all --debug=yes
After make halts again attempting to do "Testing for Lisp shadows ..." I
manually recreated the xemacs executable so
that I can run the debugger.
% ./temacs -nd -batch -l ../lisp/loadup.el dump
and re-ran the command that caused the SEGV
% xemacs -batch -vanilla -f list-load-path-shadows
Segmentation fault (core dumped)
Exit 139
dbx xemacs core
Type 'help' for help.
warning: The core file is not a fullcore. Some info may
not be available.
[using memory image in core]
reading symbolic information ...
Segmentation fault in . at 0x2020200
0x02020200 warning: Unable to access address 0x2020200 from core
0x20... are space characters which suggests a bad pointer. This is all I
have.
The core file is extremely small ('not a fullcore')
% ls -la src/core
-rw-rw-r-- 1 we24uf g06 7984 Mar 16 16:00 src/core
In fact, just invoking 'xemacs' without arguments is sufficient for a SEGV
to be
generated.
I ran temacs autotest feature... it didn't blow up. Most tests completed
okay or were skipped.
My google-fu didn't find anything particularly applicable to this
situation. Does anyone have any suggestions for me to try to get more
information as to what might be wrong or get me past this hurdle?
Thanks!
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
APPROVE COMMIT 21.5
Note: Reply-To set to xemacs-beta.
Jeff Sparkes' commit
changeset: 5373:b6e59ea11533
user: Jeff Sparkes <jsparkes(a)gmail.com>
date: Thu Mar 17 14:35:02 2011 -0400
summary: Add min-colors specifier to defface, and document it.
breaks initialization on TTYs (eg, xemacs -nw) because
`display-color-cells' currently returns nil on TTYs (cf issue757 on
the tracker), and code in faces.el expects that to return an integer.
This doesn't quite break the build, but it isn't debuggable via
-debug-init and AFAICS there is no workaround, so I'm going to go
ahead and commit.
The workaround I've employed is to assume that a display that returns
nil is monochrome, and thus display-color-cells is 2. I've made the
change in faces.el rather than in display-color-cells.
Please advise me on whether the change should be made in
display-color-cells instead. I'm of two minds; if there is no
information on visual depth, returning nil allows higher-level code to
make its own assumptions for that case. On the other hand, the API is
simpler if it always returns an integer, and user code can always
override (although that's kind of unclean).
This change also adds a new node to customize.texi documenting
`defface' and clarifies some documentation in the Faces node of
faces.texi. The new code builds without errors and XEmacs starts
correctly, on Gentoo Linux.
2011-03-19 Stephen J. Turnbull <stephen(a)xemacs.org>
* faces.el (face-spec-set-match-display):
Protect against `display-color-cells' returning nil.
Delete unreferenced let-binding of `min-colors'.
2011-03-19 Stephen J. Turnbull <stephen(a)xemacs.org>
* lispref/customize.texi (Face Definitions): New node.
(Customization): Add entry to menu.
(Variable Definitions): Add cross-ref for `defface'.
(Customization Types): Fixup Previous link.
* lispref/faces.texi (Faces):
Clarify that built-in properties of faces are computed at runtime.
diff -r eac2e6bd5b2c lisp/ChangeLog
--- a/lisp/ChangeLog Thu Mar 17 21:50:34 2011 +0000
+++ b/lisp/ChangeLog Sat Mar 19 21:55:48 2011 +0900
@@ -1,3 +1,9 @@
+2011-03-19 Stephen J. Turnbull <stephen(a)xemacs.org>
+
+ * faces.el (face-spec-set-match-display):
+ Protect against `display-color-cells' returning nil.
+ Delete unreferenced let-binding of `min-colors'.
+
2011-03-17 Aidan Kehoe <kehoea(a)parhasard.net>
* bytecomp.el (byte-compile-catch):
diff -r eac2e6bd5b2c lisp/faces.el
--- a/lisp/faces.el Thu Mar 17 21:50:34 2011 +0000
+++ b/lisp/faces.el Sat Mar 19 21:55:48 2011 +0900
@@ -1702,7 +1702,6 @@
(type (plist-get props 'type))
(class (plist-get props 'class))
(background (plist-get props 'background))
- (min-colors (plist-get props 'min-colors))
(match t)
(entries display)
entry req options)
@@ -1715,7 +1714,9 @@
(type (memq type options))
(class (memq class options))
(background (memq background options))
- (min-colors (>= (display-color-cells frame)
+ ;; `display-color-cells' can return nil (eg, TTYs).
+ ;; If so, assume monochrome.
+ (min-colors (>= (or (display-color-cells frame) 2)
(car options)))
(t (warn "Unknown req `%S' with options `%S'"
req options)
diff -r eac2e6bd5b2c man/ChangeLog
--- a/man/ChangeLog Thu Mar 17 21:50:34 2011 +0000
+++ b/man/ChangeLog Sat Mar 19 21:55:48 2011 +0900
@@ -1,3 +1,13 @@
+2011-03-19 Stephen J. Turnbull <stephen(a)xemacs.org>
+
+ * lispref/customize.texi (Face Definitions): New node.
+ (Customization): Add entry to menu.
+ (Variable Definitions): Add cross-ref for `defface'.
+ (Customization Types): Fixup Previous link.
+
+ * lispref/faces.texi (Faces):
+ Clarify that built-in properties of faces are computed at runtime.
+
2011-03-15 Aidan Kehoe <kehoea(a)parhasard.net>
* lispref/objects.texi (Character Type):
diff -r eac2e6bd5b2c man/lispref/customize.texi
--- a/man/lispref/customize.texi Thu Mar 17 21:50:34 2011 +0000
+++ b/man/lispref/customize.texi Sat Mar 19 21:55:48 2011 +0900
@@ -15,6 +15,7 @@
* Common Keywords::
* Group Definitions::
* Variable Definitions::
+* Face Definitions::
* Customization Types::
* Enabling Behavior::
@end menu
@@ -163,6 +164,7 @@
@section Defining Customization Variables
Use @code{defcustom} to declare user-editable variables.
+For face declarations, use @code{defface} instead. @xref{Face Definitions}.
@tindex defcustom
@defmac defcustom option default doc [keyword value]...
@@ -288,7 +290,67 @@
customization buffer. The @code{saved-value} property is actually a
list whose car is an expression which evaluates to the value.
-@node Customization Types, Enabling Behavior, Variable Definitions, Customization
+@node Face Definitions, Customization Types, Variable Definitions, Customization
+@section Face Definitions
+
+Use @code{defface} to declare a new face. Conventions used in
+specifying properties are similar to those for general customizable
+variables. @xref{Variable Definitions}.
+
+@defun defface face spec doc &rest args
+
+Declare @var{face} as a customizable face that defaults to @var{spec}.
+@var{face} does not need to be quoted.
+
+Third argument @var{doc} is the face documentation.
+
+If @var{face} has been set with `custom-set-face', set the face attributes
+as specified by that function, otherwise set the face attributes
+according to @var{spec}.
+
+The remaining arguments @var{args} are a property list, which has the
+form
+
+ @var{keyword} @var{value}...
+
+The following @var{keyword}s are defined:
+
+@table @code
+@item:group
+@var{value} is a customization group. Add @var{face} to that group.
+@end table
+
+@var{spec} is an alist of the form ((@var{display} @var{atts})...).
+
+@var{atts} is a list of face attributes and their values. The possible
+attributes are defined in the variable `custom-face-attributes'.
+
+The @var{atts} of the first entry in @var{spec} where the
+@var{display} matches the frame take effect in that frame.
+@var{display} can either be the symbol t, which will match all frames,
+or an alist of the form \((@var{req} @var{item}...)...)
+
+For @var{display} to match a frame, the @var{req} property of the
+frame must match one of the @var{item}. The following @var{req} are
+defined:
+
+@table @code
+@item @code{type} (the value of @code{window-system})
+ Should be one of @code{x}, @code{mswindows}, or @code{tty}.
+
+@code{class} (the frame's color support)
+ Should be one of @code{color}, @code{grayscale}, or @code{mono}.
+
+@code{min-colors} (the minimum number of colors the frame supports)
+ Should be in integer which is compared to @code{display-color-cells}
+
+@code{background} (what color is used for the background text)
+ Should be one of @code{light} or @code{dark}.
+@end table
+@end defun
+
+
+@node Customization Types, Enabling Behavior, Face Definitions, Customization
@section Customization Types
When you define a user option with @code{defcustom}, you must specify
diff -r eac2e6bd5b2c man/lispref/faces.texi
--- a/man/lispref/faces.texi Thu Mar 17 21:50:34 2011 +0000
+++ b/man/lispref/faces.texi Sat Mar 19 21:55:48 2011 +0900
@@ -26,10 +26,13 @@
Each built-in property of a face is controlled using a specifier,
which allows it to have separate values in particular buffers, frames,
-windows, and devices and to further vary according to device type
-(X or TTY), device class (color, mono, or grayscale) and number of
-displayable colors (min-colors).
-@xref{Specifiers}, for more information.
+windows, and devices. These properties are computed when the face is
+instantiated, allowing them to vary according to properties of the
+display device, such as type (X or TTY), visual class (color, mono, or
+grayscale), and number of colors displayable on the device.
+@xref{Specifiers}, for more information on specifiers.
+@xref{Face Definitions}, for defining faces whose properties vary
+according to their runtime environments.
The face named @code{default} is used for ordinary text. The face named
@code{modeline} is used for displaying the modeline. The face named
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta