XEmacs-Beta March 2015

xemacs-beta@xemacs.org

10 participants
38 discussions

Stephen J. Turnbull

Uwe Brauer writes: > I just run xemacs -vanilla and then gnuclient -nw and it worked as > expected, although I am not sure how to finish the process because the > function I am used to, when using gnuclient without "-nw", > > "C-x #" does not work in that case, so what should I do? C-x 5 0 (or M-x delete-frame RET). _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

3 participants
3 comments

path problem in auctex 9 years, 1 month

Uwe Brauer

Hi The latest auctex version 11.88 uses the following custom variable (defcustom TeX-style-path (let ((path)) ;; Put directories in an order where the more local files can ;; override the more global ones. (mapcar (lambda (file) (when file (add-to-list 'path file t))) (append (list TeX-auto-global TeX-style-global) TeX-auto-private TeX-style-private (list TeX-auto-local TeX-style-local))) path) "List of directories to search for AUCTeX style files. Per default the list is built from the values of the variables `TeX-auto-global', `TeX-style-global', `TeX-auto-private', `TeX-style-private', `TeX-auto-local', and `TeX-style-local'." :group 'TeX-file :type '(repeat (file :format "%v"))) the variable TeX-style-private is a name of a directory in which local files dwell. Now I have set this variable in Xemacs and in GNU emacs via custom (different custom files of course) to the value /home/oub/tex/sty/auto The issue is that TeX-style-path should contain also the value of TeX-auto-private, /home/oub/tex/sty/auto in GNU emacs it does, in Xemacs it does not. Is there anything in the above definition Xemacs does not understand? thanks Uwe Brauer _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
4 comments

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

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2015-03-03 - 2015-03-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. 566 open ( +1) / 317 closed ( +0) / 883 total ( +1) Open issues with patches: 13 Average duration of open issues: 2017 days. Median duration of open issues: 2192 days. Open Issues Breakdown new 258 ( +1) deferred 6 ( +0) napping 3 ( +0) verified 58 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0) Issues Created Or Reopened (1) ______________________________ xemacs in X-Windows over ssh to Raspberry Pi gives tiny font s 2015-03-04 http://tracker.xemacs.org/XEmacs/its/issue885 created anonymous _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

Re: [mlterm+gnuclient] (was: bidi support: poor-mans-bidi.el) 9 years, 1 month

Aidan Kehoe

Ar an seachtú lá de mí Márta, scríobh Uwe Brauer: > I know now how to use hebrew in mtlerm, (it is simple enough, aehm). I > have a running Xemacs with gnuserver running and use gnuclient for > example in auctex and okular. > > When I run gnulient foobar.tex, everything works as expected but > nothing seems to happen when I type gnuclient -nw, > > What do I miss? gnuclient -nw just says to open a new frame in the current terminal, rather than creating a new X11 window. Since the bidi support is in mlterm and not in XEmacs, you need the TTY frame, rather than the X11 window. If you’re already having the frame displayed in the TTY, no problem arises. When editing bidi text in mlterm, I use the following: (set-specifier (glyph-image continuation-glyph) [string :data ""] nil '(tty) 'prepend) This prevents the trailing backslash interrupting the paragraph bidi context and makes paragraphs more readable. I also use the following code, but it’s all Perso-Arabic specific, and so is unlikely to be relevant to you. Most of it actually consists of workarounds for display problems in mlterm, so it wouldn’t be appropriate to add to XEmacs. ;; When using the system keyboard through a TTY rather than quail, these ;; become useful. (define-key global-map [(control x) ?\u062e] 'other-window) (define-key global-map [(control x) ?\u0630] 'switch-to-buffer) (loop for (actual desired face) in '((?\u06c0 ?ة) ;; heh with hamze, display as a green teh marbute. (?\u2027 ?·) ;; HYPHENATION POINT, middot. (?\u02c8 ?\u02c8 bold-italic) ;; MODIFIER LETTER VERTICAL LINE (the ;; stress mark for IPA), display it as ;; bold-italic. (?\u200c ?\u2502) ;; zero-width-non-joiner, green vertical line (?\u200d ?\u0640)) ;; zero-width-joiner, green tatweel (which ;; helps in preserving joining) with glyph = nil with char-table = (specifier-instance current-display-table) do (setq glyph (make-glyph (vector 'string :data (string desired)))) (set-glyph-face glyph (or face 'green)) (put-char-table actual glyph char-table)) -- ‘Tramadol is further fed to cattle […] when working them […] (as draft animals) so that the animals do not get tired quickly. …’ — Angewandte Chemie, Sept 2014, describing the social context of (synthetic) tramadol having been found in Cameroon tree roots. _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

bidi support: poor-mans-bidi.el 9 years, 1 month

Uwe Brauer

Hello I just found poor-mans-bidi.el written by Niels Giesen, for GNU emacs, it uses either the freebidi or the bidiv engine. Here it is how it works, You turn on the minor mode, the screen gets split, a new buffer the BIDI buffer is created, which seems to be some sort of indirect buffer, of the original one. You start writing say hebrew L2R in the original buffer and it gets displayed R2L in the BIDI buffer via the freebidi engine, line breaks works. So this could be a nice enhancement of xemacs, since we have no BIDI support at all. The package works nicely in GNU emacs 23, it also works (sort of) in GNU emacs 24, although it does not make much sense since 24 has its own built in bidi-engine which is in conflict with the freebidi output. Now the mode works in xemacs for small buffers and mails. For large buffer however the BIDI buffer only displays the beginning of the original buffer, but if the cursor is say in the middle of the original buffer the BIDI buffer does not display this (it does so in GNU emacs). The author seems to have no interest in maintaining this package, given the circumstances very understandable. Is there anybody on the list with BIDI interest and lisp skills to have a look? Aidan? thanks Uwe Brauer _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

Re: incompatibility problem xemasc 21.531 and 33 byte compiled 9 years, 1 month

Stephen J. Turnbull

Glad you got the problem fixed. Steve _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

1 participants
0 comments

incompatibility problem xemasc 21.531 and 33 byte compiled 9 years, 1 month

Uwe Brauer

Hello on one laptop I have Kubuntu 10.04 32 bit and Xemacs 21.5.33 Mule compiled the other PC runs Kubuntu 14.04 with 64 bit and Xemacs.21.33 compiled. When I use now my init files from the first one in the second (which usually works/ed) I obtain an error I attach (and do not understand). I use the same mule-packages and official xemacs-package in both Xemacsen Any help is strongly wellcome (it seem that the error has to do with an compilation in compatibility regards Uwe Brauer ( _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta

2 participants
1 comments

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

XEmacs Issue Tracking System

ACTIVITY SUMMARY (2015-02-24 - 2015-03-03) 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. 565 open ( +0) / 317 closed ( +0) / 882 total ( +0) Open issues with patches: 13 Average duration of open issues: 2014 days. Median duration of open issues: 2185 days. Open Issues Breakdown new 257 ( +0) deferred 6 ( +0) napping 3 ( +0) verified 58 ( +0) assigned 145 ( +0) committed 19 ( +0) documented 3 ( +0) done/needs work 15 ( +0) _______________________________________________ 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 March 2015