August 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: XEmacs documentation binaries available 25 years, 3 months

john s jacobs anderson

> Well, I typically use efs and do the edit on my local machine. The > telnet session I usually get to xemacs.org have lots of delays (either > because the socks proxy I have to use or because my ISP has not best > link). So editing the files directly becomes a pain in the ass. I didn't even try xemacs on www.xemacs.org, because I've gotten in the habit of using vi(m) to edit stuff remotely for my web page. (Because of net delays and because it's a slow starter on the server.) EFS is on the list of 'things to learn how to do in XEmacs without thinking', but it's a long list, and it just keeps growing! (recent additions: quickurl.el, supercite, that footnoting package...) john. -- ------------------------------------------------------------------- John S Jacobs Anderson jacobs(a)azstarnet.com http://www.treefort.org/~jacobs/ <-- GeneHack:bioinfo*linux*opinion

1 participants
0 comments

selection or font problem 25 years, 3 months

Stef Epardaud

hi, i have a font/selection problem: when i select text and expand/reduce the selection, the selected area is not always the same, which results in having 'dirty' regions not repainted correctly. i am using 21.2.19 and my only option is ./configure --with-mule i launch xemacs with -vanilla and the font is the default, i have no clue what the default font is on my X though... (could it be it?) Jan Vroonhof said it could be my font, but then ... isn't xemacs supposed to handle different fonts ? especially the one it gets for 'default' ? so here it is step by step: i open xemacs, i am in the scratch buffer. i go up three times to be on the ;; "If you..." line set the mark, go down to select the line, go one more down to select the two lines ";; If ..." and ";; then" , and then if i go back up to reduce the selection of one line, the selected part "file with C-x C-f," is one pixel larger than the rest of the selected line. so when i delete the selected line with C-w there is a line of one pixel high that stays dirty on the screen. the cursor also leaves a bit of it i just noticed. i understand this is not very easy to explain, but since it is reproducable everytime, i made screenshots that show the steps one by one. i didn't want to send these imaes to the list, so i put them on the web at: http://tanglefoot.lunatech.com/~stephane/xemacs-sel1.gif http://tanglefoot.lunatech.com/~stephane/xemacs-sel2.gif http://tanglefoot.lunatech.com/~stephane/xemacs-sel3.gif http://tanglefoot.lunatech.com/~stephane/xemacs-sel4.gif http://tanglefoot.lunatech.com/~stephane/xemacs-sel5.gif from those screenshots you can clearly see there is one line of one pixel high of selection left, and a part of the cursor not repainted as well. it gets very messy when it comes to editing some serious code, and i've had to learn to put a C-l between all selection commands :( we have the problem on all machines here, with 21.1 and 21.2, it started after 20.4 i must say... -- # Stef Epardaud, # There is no limit to the power of computing ... # Java Defeater # ... except men maybe ? # Earth # Lunatech Research, # Solar System # soon we will quit researching and start finding...

1 participants
0 comments

Re: XEmacs documentation binaries available 25 years, 3 months

SL Baur

Marcus Thiessel <marcus(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > john s jacobs anderson writes: >> change made, in place on the server, using vim. ugh. now I feel all >> dirty... > You should at least use XEmacs and viper if you insist on the vi > look & feel. :-) Do we have an XEmacs built on the server? ftp.xemacs.org does not have XEmacs installed[1] as far as I am aware. > But you probably right if you argue that XEmacs would help if somebody > (which is me in that case) is not able to save the right buffer and > put it in place. > I hate Mondays!!!! :-) Footnotes: [1] Film at 11.

2 participants
1 comments

Re: xemacs source code HOWTO ? 25 years, 3 months

Michael Sperber

>>>>> "Mike" == mike fabian <mike.fabian(a)mail.rhein-ruhr.de> writes: Mike> Michael Sperber [Mr. Preprocessor] writes: >> >>>>> "dv" == Didier Verna <verna(a)inf.enst.fr> writes: >> dv> Andy Piper <andy(a)xemacs.org> wrote: >> >> >> These are not useless. It means you can just change the header instead of >> >> all of your source code if your definition of how to access bar changes. >> dv> Yes, but I'd prefer being able to debug XEmacs, even if it costs me a dv> one-or-two-shot sed call on all sources to change "->foo" to "->bar" once in a dv> year (century ?). >> >> Well, the solution to that is to move more code into the substrate, >> rather than switching the implementation language to one of the three >> most fucked-up languages alive. Mike> What are the other two candidates? There, things are not quite so clear-cut. Among the contenders are certainly Perl, Tcl, and COBOL. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

latest cvs core dumps 25 years, 3 months

Jeff Miller

just did a cvs update. starting xemacs give me this backtrace. # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque, size=4) 0x82c21c0> ...) # (unwind-protect ...) # (unwind-protect ...) # bind (inhibit-quit frame-being-created) make-frame(nil #<x-device on ":0.0" 0x1b19>) frame-initialize() # bind (debugger debug-on-error command-line-args-left) command-line() # (unwind-protect ...) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Segmentation fault (core dumped) not much looking at the core dump (gdb) where #0 0x403ce111 in __kill () #1 0x80874d5 in fatal_error_signal () #2 <signal handler called> (gdb)

1 participants
0 comments

Re: xemacs source code HOWTO ? 25 years, 3 months

SL Baur

Didier Verna <verna(a)inf.enst.fr> writes in xemacs-beta(a)xemacs.org: > sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) wrote: dv> I whish we rewritte XEmacs in C++ someday. >> >> Yeah, let's REALLY screw things up for good ... > I said "someday", not "today"... I'm /not/ the one who can tell whether > it's already feasible, in terms of C++ normalization and existence of a > decent C++ compiler on all platforms that we currently support. "Normalization"? What normalization might that be? I am greatly distressed that current stable kde is uncompilable shared with gcc-2.95. C++ is like a beautiful rose ... that smells bad. :-)

1 participants
0 comments

Re: XEmacs documentation binaries available 25 years, 3 months

Jan Vroonhof

john s jacobs anderson <jacobs(a)azstarnet.COM> writes: > That's because that URI should be > /pub/xemacs/docs/a4/internals-a4.pdf.gz > if memory serves... Unfortunately the pdf's (at least the new-user-intro-letter thta I checked) are also ugly (sorry Darryl and Kazuyuki). They are made with bitmap fonts instead of Type 1 fonts. They really should be redone using texi2pdf on a modern teTeX 1.0/Tex Live-4 installation. Jan

3 participants
2 comments

Re: constantly crashing in Gnus 25 years, 3 months

Jan Vroonhof

Ulrich Drepper <drepper(a)cygnus.com> writes: > > :-) What compiler were you using? > > A quite stable egcs release. Well the stable egcs 1.0.3 and gcc 2.8.1. releases are responsible for about half the crashes in our bug tracking archive, so I have got into the habit of asking. However this almost for sure a real XEmacs bug. > Anyhow, I have now a version with all debug info compiled in and will > try to get more information. Well. I think that unless you also set x_debug_events to 1 using a debugger it won't help much. I am pretty sure (based on Karl's backtrace), that the crash can be made to go away if we simply chop the XIC xic = FRAME_X_XIC (x_any_window_to_frame (get_device_from_display (event->display), event->window)); line in event-Xt.c into pieces and do nothing if x_any_window_to_frame returns NULL. However as Kyle says, it would be much nicer to actually not get into that situation in the first place. Thus, observing that the window still has a parent that we didn't delete: Can you try out this patch? In particular can you trigger the assert? (which replaces the crash). The patch is of the "untested but obvious type". Index: event-Xt.c =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs/src/event-Xt.c,v retrieving revision 1.41.2.11 diff -u -u -r1.41.2.11 event-Xt.c --- event-Xt.c 1999/07/30 09:14:01 1.41.2.11 +++ event-Xt.c 1999/08/17 00:20:50 ＠＠ -780,9 +780,16 ＠＠ int bufsiz = sizeof (buffer); Status status; #ifdef XIM_XLIB - XIC xic = FRAME_X_XIC (x_any_window_to_frame + XIC xic; + struct frame *f; + + /* Sometimes we get a keysym for a window that we have deleted, + but its parent is still known too us. */ + f = x_any_window_or_parent_to_frame (get_device_from_display (event->display), - event->window)); + event->window); + assert(f != NULL); + XIC xic = FRAME_X_XIC (f); #endif /* XIM_XLIB */ #endif /* HAVE_XIM */

1 participants
0 comments

Re: xemacs source code HOWTO ? 25 years, 3 months

Jan Vroonhof

Stef Epardaud <stef(a)lunatech.com> writes: > my checkout is 21.1.4, but my modules/sample/ directory is empty. > i'll try to chekout a newer version... If you want to hack C sources, having the 21.2.x sources is a must. > for something completely different: does anybody have selection problems > with 21.1.4 ? when i select text and expend/reduce the selection, the > selection is not painted/repainted correctly, and it leaves lines of > unrepainted selections of one pixel high around the screen until text or > something else redraws over it. is it me or is it just everyone, or just > my version? we have it here on all machines, even with -vanilla, but we > all use the same version. No such problems here. Maybe you have a font that triggers it. Jan

1 participants
0 comments

Re: xemacs source code HOWTO ? 25 years, 3 months

Adrian Aichner

>>>>> "Stef" == Stef Epardaud <stef(a)lunatech.com> writes: Stef> my checkout is 21.1.4, but my modules/sample/ directory is empty. Stef> i'll try to chekout a newer version... Yep, modules are new in 21.2. Use cvs -z3 -d :pserver:xemacs＠cvs.xemacs.org:/usr/CVSroot checkout -P -r release-21-2 xemacs to get the latest files on the 21.2 branch. Good luck, Adrian

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 1999