luis@titan.hbar.rice.edu (Luis Soltero) (11/06/88)
I ams so happy! I just got XV10R4 running under uPort on my 386 (snappy). i am however having a small problem w/ gnu emacs 18.51 compiled using HAVE_X_WINDOWS and HAVE_X_MENU (or something like that). emacs compiles O.K., links O.K, and dumps O.K. however when i run it it opens a window hangs around for about 5 seconds and then decides it's finished. it just exits!! any ideas? thanks in advance. --luis@titan.rice.edu
scotty@l5comp.UUCP (Scott Turner) (11/07/88)
In article <LUIS.88Nov5120631@titan.hbar.rice.edu> luis@titan.hbar.rice.edu (Luis Soltero) writes: > >I ams so happy! I just got XV10R4 running under uPort on my 386 (snappy). >i am however having a small problem w/ gnu emacs 18.51 compiled using >HAVE_X_WINDOWS and HAVE_X_MENU (or something like that). emacs compiles >O.K., links O.K, and dumps O.K. however when i run it it opens a window >hangs around for about 5 seconds and then decides it's finished. it just >exits!! any ideas? thanks in advance. > >--luis@titan.rice.edu This EXACT same problem occured here as well. Running from the login xterm seemed to help... The real solution came when the 18.52 update was installed. After the upgrade it has been operating quite happily from whatever xterm it is fired up from. Spawning xterm's from other than the login xterm causes trouble here when the uwm is used to grab and move the spawned xterm. After you let go at the new location the xterm dies and you get an "Alarm 8 call" on the login xterm. Weird. Other weirdness.... X grows. It's like the blob. Due to all the patches applied the system can now run for over a week without a crash. This means that X will run for over a week without being restarted as well. ps -el reveals that X starts out life using 125 clicks (4096 bytes per click I think, the dox aren't too clear) of memory. After a solid week of use/abuse it can grow to eat 315 clicks of memory (with only one xterm running!) Once the memory useage reaches approx 331 clicks X stops processing mouse movement. If you login over a serial line and kill the processes attached to X windows the windows WILL disappear, so the X hasn't totally crashed. It just won't listen to the mouse anymore. Restarting X will cure the above problem(s). New outbitmap vs old outbitmap. The old outbitmap program could output bitmaps the size (or even larger!) than the physical screen. The new outbitmap program chokes on anything larger than approx 1024x1200. The old outbitmap was the outbitmap distributed without source code and when the WGE didn't support DOS. Setting the root window background hasn't worked so far. All efforts to place user generated bitmaps into the root window's background have failed. The calls don't generate errors, they seem to work, but nothing happens. Anyone out there gotten this to work? (xphoon is a good example program to try) Scott Turner scotty@l5comp -or- uunet!l5comp!scotty
sandy@turnkey.TCC.COM (Sanford 'Sandy' Zelkovitz) (11/07/88)
In article <LUIS.88Nov5120631@titan.hbar.rice.edu>, luis@titan.hbar.rice.edu (Luis Soltero) writes: > > I ams so happy! I just got XV10R4 running under uPort on my 386 (snappy). > i am however having a small problem w/ gnu emacs 18.51 compiled using > HAVE_X_WINDOWS and HAVE_X_MENU (or something like that). emacs compiles > O.K., links O.K, and dumps O.K. however when i run it it opens a window > hangs around for about 5 seconds and then decides it's finished. it just > exits!! any ideas? thanks in advance. > > --luis@titan.rice.edu This is only a guess on my part; however, the interface in GNU-Emacs may be for X11.2 and not for X10.4. You may want to check this out to see if my guess is reality. If so, you will probably have to make some modifications to the GNU code. Sanford <sandy> Zelkovitz