May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

artifacts when dragging vertical dividers in 40pre4 26 years, 6 months

William M. Perry

Just playing around with the new draggable vertical divider. It was nice and 3d in pre3... pre4 its flat and lifeless. And I get the following screen artifacts when dragging slowly to the right. This is Linux 2.0.33[1], XFree86 3.3.2 -Bill P. --[[image/gif Content-Disposition: inline; filename="artifacts.gif"][base64]] R0lGODdhNgGmAPcAAAAAAAAAiHBwcHh4eKCgoLAgILi4uMjIyODg4PDw8Pj4+Ai/AGglAU8N ABYCAAhAAPTI6EdJRxYWFggICBAMOO7y8Qn//0C/v/4EGBoA8QIA/0AAv1AQXwHuEAAJAgBA QGjw8EhAQGjwaE9ATzh87PNPR/8WFr8ICIEbG1VbSAMAFkAACGYEaEgATxYAFggACGjwjjlA GA4WAggIQO28SDnyAA3/AEC/AJgEDQkAABQAAEAAAADwRQBAAAAWAAQIAFjIMHbySBL/Fgy/ CFgldHYN8RIC/whAvwgEbnkAjREAB4DwjkhAGBYWAmgESEgAABYAAAgAABDwDe5AAAkWAEAI AFTgRfPyAP//AL+/ABQlOA8NSAUCFkBACAMAdABI8QAW/wAIvzhgoEfyjRb/Bwi/CEwE8AIA QAAAFgAACBAQg+7uAAkJwEBAAnDwaPNAT0TwSBpAAAUWALB8EEZPABYWAAgIADgbRkdbAEwE EgIAALwQgPPz8f///7+/v90lTnQNlQgCBwhACGw0GEdIcA4WFQCQAQDyAAD/AAC/ADAEYvQA x/8AEr8ACAgQkGDu8WQJ/0BAvxDwNe5AiAkWB0AICCzw1PRAbf8WFTB83PRP9v8W/78IvwgA kGAA9GQA/+zw3/NAfP8WBcBoDadPAAcWAAC8AABJAAAIAAEQ3ADu9gAJ/wBAvzb+3AEa9gAC /6ZSAAAB9AAA/wAAvwBKAABoAAFPADTkAPTyADCBAPRVAP8DAL9AAOw23PNK9vxUEKfz7gf/ CQi/QAgKIGAAAGQAADbs8AEAQKZu/gAAGgDAAgACQABfAADzANwKAfYASP8AFgD4BABf8AAQ QAACFgBACAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACwAAAAANgGmAAAI/gAVCBxIsKDBgwgTKlzIsKHD hxAjSlw4IMGBixgxVhQIoOPEjyBDihxJsqTJkyhPVszIcqOCjgBSypxJs6bNmzhHrmSpMQFH jzmDCh1KtKhRgjt5HnAJ86jTp1CjSj2YlCdToFOzat3KlWTVlj5fYu1KtqxZs18zXo15tq3b t0fT9vzJFq7du3hVWlS6NGzTvIADC24o9+LawYgTIy7cl67ix5DhMj4cubLlrZP9jr3MuTPR zI49ix59E7TYuqRTq/a6Vynl1bBjRzT9V7bt2whpb8bN27Zu1L2Dw/4tvPjw1lY1AzfOnDPx 5tCdIwcbOrp1yM+va188Xa3y7eAF/mcPT15y97mny6t/O369e67t38uXGn++/bjnDX+/z99p /f4AlpZfY+kFaGBO/x2ooEkJLuhgSA0+KOFsA7424YUfRYjhhrlVuB+HIBLmYXUhltghXwTW ZuKKSI1YIIswKqBhjBPOSOODNt64YI46HshjjwH+CGR/Qg55X5FGzodkku8tyeR6Tj5ZXpRS hkdlldtdieV1Wm4ZXZdeNgdmmMaNSaZwZp7ZW5pq4sZmm765qCKc9r1J53EoWninfHbumVqf fo4GaKCeDUqodHl+eKh6hi5aWaOOYifnbpFqB2mliV2K6WCabhpYp57mBWqod41KqnmJkniq mJMut2px/qa+elasspZFa61d3YorZq3uWmavvqIJbLBrDkusm8YeG2eqLyq7LF96OosntIpK O61r1Vqrmq7aFsVtt0N9C25Q4o6LU7nm2oRuujSty65M7r6LUrzyMphsvY/ei6+kzM65L7/U qvrvY/QODNIACCesMMLZGrwYARBHLDEBDTssXgIYZ6wxxgJbLB7FrlHcsceADQCyVSI3S/LH J2sEccUrl/pySy+PHLNdJs9sWMQw38wezy7XrLLPMgOds9D+Ei2ZxBYdnXLSSrvlNMUT9xx1 WRtnzfHQYi7s9ddghy322GSXbfbZaKet9toDNKviX2zHLffccmtt99145633/t589+3334AH ngDVE/Ps9lhwF84zxYI37vjjd6Mo+eSUV2755Zhnrvnml5ucseI+vY04UFO/nIDnnKeu+uqs t+7667DHvjnqB2Bc9eGoJc70XrTL7vvvwAcv/PC+91774DWLnjvpPCNnPPHQRy/99NSv/vzx IitPUOIYozxg9eCHL/74sl9/EcfaDwR3fuaT7/778McfcncIZz/68myZjLD38vfv///iM179 kne/7TEPYvtz2fcAyMAGOpBztBug4dIXmqklsH0PzKAGN+g9CTINdwbMn+IS1jIOvo5uKEyh ClfIwrERDnQgVN8BR0iAFtrwhgmDnA53yMMe+vBx/jEMzQ+HSMS+IeCISEyiEpfIxCY68YlQ jKIUp0jFKlrxilhUYmiyyMUuevGLYAyjGMdIxjKKUQBbNKMa1whFA7jxjXCMoxznSMc62vGO eMyjHvfIxz768Y9vFAAaC3REQBrykIhMZBwLwEg4AkCRfISJIzsCyUpa8pJ7FGQaMcnJTiay AHF8ZCclGUo5itKTqEylITVJSASkMgCwNAAsZ0lLVdoxAIcEpSNTeco39tKNv7SlMIcpR1b+ pZCvfCMuZalMYspxmXdkZCPhqMtdjtIAvwxmMJ3JTVUaEyjITCY0cTnOWJYzlspEpxtn2Uda nrOO1TRAPIHpyUdm05Td/synML/JlnAmM53QZCY5n7nOZjKzoAa9Y0DHuUhpUhOfvoSJKCU6 UYkC06LYxCg9SxlRUlL0oh7F6EczGtKSUpKkJx2pSkXKUpNW1KVw5KdACinNadZUlzd1Y07l WdNmMnShAgXoMgMKUD8OtKgP1WlSrYnJU/ZSm/qMKiplqgB/evKoB4XjQIdqUKLG0auGXCYo qxnPeWLzmhtNqy+lylZMUtWqnGRoVrl6VLnaNaGAlOsbHTrWnW5TkZIM7Ecp+te2GjaTgzym K1HJTnfW0pyyHCpkI7tQdSK0nZaN5GE3y9k/vnWxnQ3tHQsr2tJ29rOmTa1qV7ta1LK2m4KM Ta1sZ0vb2tr2trjNrW53y9ve+va3wA0ubdMo3OIa97jITa5yl8vc5jpXuVt8rnSnm9urWfe6 2M2udrfL3e5697vgDa94x0ve8pp3QwEBADs= [1] Can't wait to get my two new processors next week, when it will become linux 2.1 + SMP :)

1 participants
0 comments

[bug] window sizes changed on redisplay - due to frame toolbar changes? 26 years, 6 months

Greg Klanderman

xemacs -q C-x 2 (shrink-window-pixels 2) (window-pixel-height) (redraw-frame) (window-pixel-height) => different value in the debugger, in a different example, I see that frame toolbar update is now resizinf the frame which is resizing each window to an integer multiple of default face height. No time to look into this now (last Seinfeld calls), can whoever made these changes please look into it? thanks, greg (gdb) where #0 set_window_pixsize (window=547440640, new_pixsize=812, nodelete=0, set_height=1) at window.c:2840 #1 0x132024 in set_window_pixheight (window=547440640, new_pixheight=812, nodelete=0) at window.c:2962 #2 0xb9d20 in change_frame_size_1 (f=0x2f5200, newheight=59, newwidth=100) at frame.c:2892 #3 0xba320 in change_frame_size (f=0x2f5200, newheight=59, newwidth=100, delay=0) at frame.c:2968 #4 0x7fb7c in update_frame_toolbars (f=0x2f5200) at toolbar.c:788 #5 0xeb344 in redisplay_frame (f=0x2f5200, preemption_check=0) at redisplay.c:5376 #6 0xeb57c in redisplay_device (d=0x2c3c00) at redisplay.c:5498 #7 0xeb918 in redisplay_without_hooks () at redisplay.c:5614 #8 0xebb14 in redisplay () at redisplay.c:5682 #9 0x92128 in Fnext_event (event=546277380, prompt=-1607946236) at event-stream.c:2235 #10 0x5631c in Fcommand_loop_1 () at cmdloop.c:570 #11 0x5613c in command_loop_1 (dummy=-1607946236) at cmdloop.c:494 #12 0x6e364 in condition_case_1 (handlers=-1607946140, bfun=0x56118 <command_loop_1>, barg=-1607946236, hfun=0x55a64 <cmd_error>, harg=-1607946236) at eval.c:1653 #13 0x55b78 in command_loop_3 () at cmdloop.c:256 #14 0x55ba0 in command_loop_2 (dummy=-1607946236) at cmdloop.c:267 #15 0x6e000 in internal_catch (tag=-1607868564, func=0x55b94 <command_loop_2>, arg=-1607946236, threw=0x0) at eval.c:1328 #16 0x55da8 in initial_command_loop (load_me=351124) at cmdloop.c:305 #17 0x6afe4 in xemacs_21_0_b40_sparc_sun_solaris2_5_1 (argc=1, argv=0xeffff60c, envp=0xeffff614, restart=2452552) at emacs.c:1680 #18 0x6b710 in main (argc=1, argv=0xeffff60c, envp=0xeffff614) at emacs.c:2097

2 participants
1 comments

Re: divider color ?? 26 years, 6 months

SL Baur

Kirill M Katsnelson <kkm(a)kis.ru> writes: > No, there is currently no way to set it. I was going to hack on dividers > issues tomorrow (have to sleep a bit), so I'll do a face specifier for > that, ok? O.K. > | It should be possible to set the colors (on everything including > | menubars and scrollbars) from Lisp. Since the dividers are new they > | should start off doing The Right Thing. > | > | > It seems to be using the modeline color. > Absolutely correct. I don't see a problem with defaulting to the modeline color if there's a face specifier to change it.

1 participants
0 comments

Re: divider color ?? 26 years, 6 months

SL Baur

Greg Klanderman <greg(a)alphatech.com> writes: > Is it possible to set the divider color? If there is, it doesn't pass the apropos test. It should be possible to set the colors (on everything including menubars and scrollbars) from Lisp. Since the dividers are new they should start off doing The Right Thing. > It seems to be using the modeline color. Unfortunately, my modeline > is white and shadowless. I would like the dividers to be grey and > shadowed. White does not shadow well, the light side becomes a > pixmap texture and the dark side is background.

2 participants
1 comments

divider color ?? 26 years, 6 months

Greg Klanderman

Is it possible to set the divider color? It seems to be using the modeline color. Unfortunately, my modeline is white and shadowless. I would like the dividers to be grey and shadowed. White does not shadow well, the light side becomes a pixmap texture and the dark side is background. Otherwise they're very cool! greg

1 participants
0 comments

[Success] XEmacs 21.0b40p4 (Saanen-pre4) on HPUX 9.05 26 years, 6 months

Nobu Toge

I retried building b40p4 with GNU make (3.76.1). Now it builds and runs fine without a hitch. I noticed that I have been using HPUX make for thje last few days, and apparently that was the cause of the problem as I reported in my last posting. Should use GNU make. uname -a: HP-UX accad1 A.09.05 A 9000/735 2005266055 two-user license ./configure 'hppa1.1-hp-hpux9.05' '--dynamic=yes' '--prefix=/usr/local' '--with -dialogs=athena' '--with-xface' '--with-tty=yes' '--site-includes=/usr/local/lib /gcc-lib/hppa1.1-hp-hpux9.05/2.8.1/include /usr/local/canna/include' '--error-ch ecking=none' '--with-jpeg' '--with-xpm' '--with-sound=no' '--with-mule' '--with- canna' '--with-xfs' '--with-database=no' '--with-x' '--cflags=-pipe -mpa-risc-1- 1 -mschedule=7100 -mjump-in-delay -funroll-loops -O5' '--package-path=/usr/local /lib/xemacspack' '--with-dragndrop=no' XEmacs 21.0-b40 "Saanen-pre4" configured for `hppa1.1-hp-hpux9.05'. Where should the build process find the source code? /users4/toge/HPUX/XEma cs210/xemacs-21.0-b39 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/hpux9-shr.h' and `m/hp800.h' What compiler should XEmacs be built with? gcc -pipe -mpa-risc-1- 1 -mschedule=7100 -mjump-in-delay -funroll-loops -O5 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/include/Motif1.2 /usr/local/X11R6/include Where do we find X Windows libraries? /usr/lib/Motif1.2 /usr /lib/X11R6 Additional header files: /usr/local/lib/gcc-lib /hppa1.1-hp-hpux9.05/2.8.1/include /usr/local/canna/include Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for JPEG image conversion. Compiling in support for PNG image conversion. Compiling in support for TIFF image conversion. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using Motif to provide XIM support. Compiling in support for Canna on Mule. Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Compiling in extra code for debugging. Compiling in code for checking XEmacs memory usage. -- Nobu Toge (toge(a)accad1.kek.jp)

1 participants
0 comments

Vertical-Divider/Modeline Wierdness 26 years, 6 months

Jim Radford

"21.0 \"Saanen-pre4\" XEmacs Lucid (beta40)" C-x 2 C-x 3 C-x 2 _________ / | \ | D | |-C--| E | | | F| |-A--|-B--| | | | | \_________/ You can't move the left middle modeline (A) at all, but you can move the one adjacent to it (B) (which then moves the one you couldn't move (A)). When you move this divider(B), you can move the one above it (C) up, but not down. This gives it (C) a stair-step effect. Actually if you play for a while, it sometimes moves it (C) down a little, but not much. If you move a vertical divider (D) to the right so that the mouse is still in the window that shrinks (E), then it (E) will not shrink if the cursor is too far to the right (F). This doesn't happen when moving left. This make it hard to shrink the window all the way when moving the divider to the right. Thanks for the work on the vertical-dividers, -Jim

1 participants
0 comments

Re: enable-clash-detection 26 years, 6 months

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > Clash detection is really hard to do right. I need a lot of > convincing before it can ever be re-enabled by default. I still maintain that this is a very useful XEmacs feature. We should work hard before abandoning it. > Clash detection has serious conceptual problems. > > It is very difficult for emacs to tell if two filenames used by > different clients really clash or not - e.g. two clients editing > /etc/passwd will clash only if they are on the same machine. > > In general, clients are going to have separate file name spaces. > > clash detection requires a directory writable by every client. None of these are conceptual problems, and I believe the new implementation resolves them by doing away with the concept of a global directory. > In the case where it does work reliably (single-user machine, no > network filesystems) is also the case where it's the least useful. > > A feature that only works intermittently, causes perceptible slowness > on all file operations, and fails to scale well is a feature that > needs to be explicitly enabled by the user. > > Keep in mind my vision for the future: someone provides a binary > installed XEmacs that is used potentially by everyone worldwide simply > by setting their PATH. I implemented such a `non-distribution' of > XEmacs in 1993 at IBM. I had users in California, Toronto, and Sweden > using the exact same binary. Do we really want these users to deal > with mutual clash-detection? > > Martin > > I say NO! to enabling global clash-detection. Will you at least *look* at the new implementation before saying "NO!"? Sheesh... -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The meta-Turing test counts a thing as intelligent if it seeks to devise and apply Turing tests to objects of its own creation.

1 participants
0 comments

Re: enable-clash-detection 26 years, 6 months

Hrvoje Niksic

SL Baur <steve(a)xemacs.org> writes: > > 2. Is the default (disabled) intentional? > > I vaguely remember it being intentional. There are definitely > problems with the implementation. I think we should reenable the clash detection by default, and fix the problems if/when they arise. Clash detection is a *good* feature, and one of the more advertised features of Emacs in general. We should preserve it. Just IMHO. > > Personally I think locking like this has no place in an > > application (other than automatic handling of other systems like > > for CVS). > > I don't know. The Roman Numeral editor does it. File locking is > unreliable over NFS. IMO it's safer to not use it. The current code > will detect when a file has changed out from under the editor and > that's the best we can hope for in the general case. Yup. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- A radioactive cat has eighteen half-lives.

3 participants
2 comments

Re: [Failure] XEmacs 21.0b40p4 (Saanen-pre4) on HPUX 9.05 26 years, 6 months

David Bush

> From steve(a)xemacs.org Thu May 14 18:16:43 1998 > Mail-Copies-To: never > To: xemacs-beta(a)xemacs.org > Subject: Re: [Failure] XEmacs 21.0b40p4 (Saanen-pre4) on HPUX 9.05 > X-Face: (:YAD＠JS'&Kz'M}n7eX7gEvPR6U1mJ-kt;asEc2qAv;h{Yw7ckz<7+X_SYeTNAaPui:e~x$ ,A=gkt*>UPL/}\a/#C~v2%ETiAY_sx;xve0yL??JWTtX_-NUzXyP38UdW#cmN1\4(X!c3m#%IbtB-3 Z-!xpZi!`E.s{(;aP=b11"!3wQu]1j(a)^V|;n=B|{l<bZV1.AI`zWV%kPCnUhcgEe\(}/_kNd6,*3ZJ Q3o<YQ3^u;7jS=:p0--u3msQO > X-Attribution: sb > From: SL Baur <steve(a)xemacs.org> > Mime-Version: 1.0 (generated by tm-edit 7.108) > Date: 14 May 1998 14:53:31 -0700 > X-Mailing-List: <xemacs-beta(a)xemacs.org> > > Nobu Toge <toge(a)accad1.kek.jp> writes: > > [filled and edited for line length reasons] > > > EMACSBOOTSTRAPLOADPATH= ... > > -o ../lib-src/DOC -d ... > > > abbrev.c alloc.c blocktype.c buffer.c bytecode.c > > callint.c callproc.c casefiddle.c casetab.c > > chartab.c cmdloop.c cmds.c console.c > > console-stream.c data.c device.c dired.c doc.c > > doprnt.c dynarr.c editfns.c elhash.c emacs.c eval.c > > events.c $(extra_objs) event-stream.c extents.c > > `$(extra_objs)'? > > > faces.c fileio.c $(LOCK_OBJ) filemode.c floatfns.c > > `$(LOCK_OBJ)'? > > > fns.c font-lock.c frame.c general.c getloadavg.c > > glyphs.c glyphs-eimage.c $(gui_objs) hash.c > > `$(gui_objs)'? > > > imgproc.c indent.c insdel.c intl.c keymap.c > > $(RTC_patch_objs) line-number.c lread.c lstream.c > > `$(RTC_patch_objs)'? > > > macros.c marker.c md5.c minibuf.c objects.c opaque.c > > print.c process.c profile.c pure.c rangetab.c > > redisplay.c redisplay-output.c regex.c search.c > > $(sheap_obj) signal.c sound.c specifier.c strftime.c > > `$(sheap_obj)'? > > > symbols.c syntax.c sysdep.c undo.c $(x_objs) > > `$(x_objs)'? > > > widget.c window.c ralloc.c > > > sh: syntax error at line 4: `(' unexpected > > *** Error code 2 > > That appears to be coming from the unsubsituted variables noted > above. They are supposed to be substituted by Make. > > > ... > > At this moment I cannot even tell what this "line 4" means. > > If someone kindly gives me what to look for, perhaps I can do a bit more > > bug hunting. > > Maybe it's an HP make bug. Do things work better if you do it with > GNU make? I have seen exactly the same problem under DG/UX with an older (archaic) version of GNU make. I'll try again with the latest. david

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 May 1998