November 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: vfork revisited (was 64bit clean XEmacs) 25 years, 5 months

Colin Rafferty

Sam Steingold writes: > Why not have an exec-like call which creates a new process (instead of > replacing the current one with the new one)? We already have that. Call system() with a `&' at the end of the command string. However, there are generally other things that one needs to do after the fork, but before the exec. For example, if you want the two processes talking, you want to do some dup2() calls to make stdin and stdout be on pipes. > Also, how is vfork different from vork? [linux man says that vfork=fork] I assumes you mean "different from fork". Anyway, I tried to summarize from memory, but it turns out that the man page on Solaris explains it better that I can: vfork() can be used to create new processes without fully copying the address space of the old process. It is useful when the purpose of fork() would have been to create a new system context for an execve(). vfork() differs from fork() in that the child borrows the parent's memory and thread of control until a call to execve() or an exit (either by a call to _exit() (see exit(2)) or abnormally). The parent process is suspended while the child is using its resources. -- Colin

3 participants
2 comments

Re: wierd color problem with xemacs-21.0-b57 25 years, 5 months

Jan Vroonhof

Per Abrahamsen <abraham(a)dina.kvl.dk> writes: > Ok, I tried this (to avoid gnuclient interference): > > xterm% xemacs > M-x customize-face RET custom-invalid-face RET > M-x make-frame-on-tty RET RET Note you need an extra C-x 5 b RET and C-x b RET. The problem happens only on the _second_ tty frame. > So, it is a bug introduced in 21.0. The code to initialize custom > faces for a new frame in 20.4 are `initialize-custom-faces' and > `custom-initialize-frame'. Does calling one of these manually in 21.0 > helps? (custom-initialize-frame (selected-frame)) does nothing but (initialize-custom-faces (selected-frame)) cures the problem. given this... (defun custom-initialize-frame (frame) "Initialize frame-local custom faces for FRAME if necessary." (unless (equal (get-custom-frame-properties) (get-custom-frame-properties frame)) (initialize-custom-faces frame))) this would seem that get-custom-frame-properties somehow does something different in 21.0. In 21.0 on the second tty frame (get-custom-frame-properties) -> (type tty class mono background dark) (Note that this is on an xterm with a white background!) In 20.4 it was (get-custom-frame-properties) -> (type x class color background light) Looks in faces.el: (defun get-custom-frame-properties (&optional frame) "Return a plist with the frame properties of FRAME used by custom. If FRAME is nil, return the default frame properties." (cond (frame ;; Try to get from cache. (let ((cache (frame-property frame 'custom-properties))) (unless cache ;; Oh well, get it then. (setq cache (extract-custom-frame-properties frame)) ;; and cache it... (set-frame-property frame 'custom-properties cache)) cache)) 20.4: (default-custom-frame-properties) 21.0: ;; We avoid this cache, because various frame and device 21.0: ;; properties can change. 21.0: ;;(default-custom-frame-properties) (t (setq default-custom-frame-properties (extract-custom-frame-properties (selected-frame)))))) I think the problem is obvious. However I am not sure whether the 21.0 is more correct and there should be another way to fix this. Also I cannot find where these functions are called and/or how the initial frame on the new device gets the correct faces. The most suspect changelog entry seems to be 1998-03-27 Kyle Jones <kyle_jones(a)wonderworks.com> * faces.el: Separated face intializations based on device classes into device type specific (tag set, instantiator) pairs. Kyle, what did you do there?

3 participants
2 comments

Re: Out of toppic: The Halloween Documents 25 years, 5 months

Jan Vroonhof

wmperry(a)aventail.com (William M. Perry) writes: > also check out > http://www.microsoft.com/ntserver/highlights/editorletter.asp for their > response. > > Seems reasonable enough, other than the bit about open standards at the > end. :) The main theme of the reply seems to confirm the intentional leak theory. Intentional leak? Yes, minister!

1 participants
0 comments

Re: print buffer 25 years, 5 months

Jan Vroonhof

"Peter Gieser" <pete(a)pog.ufl.edu> writes: > I am running 21.0 and the funtionality to print seems to be missing. > Am *I* missing something? Where are the print functions suppose to be? In the os-utils package. Jan

1 participants
0 comments

Re: xemacs and oversized characters 25 years, 5 months

Jan Vroonhof

jcb(a)dcs.ed.ac.uk writes: > 20.4(Mule) and 21.2-b3(Mule). Haven't tried 21.0. > (By the way, could you point me to a description of what XEmacs > version numbers mean? I haven't found one in the obvious places, but > maybe I haven't looked.) 20.4 latest stable release 21.0 The next stable release. This is feature frozen. 21.1 Bug fix release wrt 21.1 21.2 The next release with new stuff after 21.0 As people have already written things that should not go into 21.0 there has been a 21.2 branch opened for that. > They don't visually overlap, but the top of the circumflex is drawn in > the bottom pixel of the "f" `cell', and gets left behind. Here they are well separated. The fix in 21.x is that now ascend+descent is used for the height instead of just ascent. As f has no descent there should be ample room for the dots. For instance here 'y' and 'Ä' touch each other so there I could understand a problem. (Just look at the size of the block cursor.) Likewise with 20.4 as it forgot the descent sometimes (which is why the specs were there). Note: Are you sure it was a really a bug that your X server didn't paint outside of the ascend? I don't know what the specs say but it seems pretty difficult to deal with in an interactive environment. Jan

1 participants
0 comments

Re: xemacs and oversized characters 25 years, 5 months

jcb＠dcs.ed.ac.uk

In article <bypvb1ge0z.fsf(a)bolzano.math.ethz.ch> Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: >> At present, it uses (I say this based on observation, not source >> inspection) the font ascent to determine the line spacing. >Which version did you use? I recall fixes regarding this be applied and.. 20.4(Mule) and 21.2-b3(Mule). Haven't tried 21.0. (By the way, could you point me to a description of what XEmacs version numbers mean? I haven't found one in the obvious places, but maybe I haven't looked.) >> foo >> Acircumflex >....in my XEmacs 21.0 these do not overlap. X is homegrown X11R6.3 on >Solaris 2.5.1. I used exactly the same fontspec. They don't visually overlap, but the top of the circumflex is drawn in the bottom pixel of the "f" `cell', and gets left behind. >And I think most these have been eliminated too. Or at least should >have been. I cannot remember seeing fly specks recently. You're right; 21.2 seems much better than 20.4; I was confused. Apologies to the fixers. >> (1) XEmacs should treat outsize characters as it treats any other >> random glyph, and increase the line height accordingly. > >I would say (1). TeX does 2, but TeX is not an editor. I suppose what TeX does is more like (1), in that it looks at the metrics of individual characters, and if they exceed the linespacing, it increases the linespacing (in unmodified Plain TeX or most LaTeX styles). But it's more like (2) in that it takes no account of where the ink goes. But as you say, TeX is not an editor.

1 participants
0 comments

print buffer 25 years, 5 months

Peter Gieser

I am running 21.0 and the funtionality to print seems to be missing. Am *I* missing something? Where are the print functions suppose to be? Pete -- Peter Gieser, Ph.D. Phone: (352) 392-5198 #306 POG Statistical Office FAX: (352) 392-8162 104 North Main Street #600 Email: pete(a)pog.ufl.edu Gainesville, FL 32601 Web: www.stat.ufl.edu/personnel/faculty.html * Send me email to receive my PGP public key *

1 participants
0 comments

[Q] make-image-instance 25 years, 5 months

Didier Verna

How can make-image-instance fail saying "color allocation failed" knowing that I'm running under a 24 bit TrueColor display ? -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

[patch] Re: bbdb cvs archive 25 years, 5 months

Colin Rafferty

Didier Verna writes: > The latest bbdb archive from cvs seem to use the function > extent-data. I vaguely remember having fixed this problem (or someone else, > maybe) a while ago. Is the cvs version outdated ? My mistake. Steve claimed that his patch subsumed yours, and I didn't check. Here is your patch that we will to apply, and needs to be applied for XEmacs 21.2+. 1998-11-09 Didier Verna <verna(a)inf.enst.fr> * lisp/bbdb-xemacs.el (bbdb-fontify-buffer): extent-data is obsolete (and gone in 21.2+). Replace it. (bbdb-menu): ditto. ------- Start of forwarded message ------- To: XEmacs beta list <xemacs-beta(a)xemacs.org>, info-bbdb(a)xemacs.org Subject: [PATCH] XEmacs obsolete function From: Didier Verna <verna(a)inf.enst.fr> Date: 24 Jul 1998 09:54:18 +0200 This patch avoids using extent-data, a function that is obsolete at least from XEmacs 20.3 and will completely disapear in XEmacs 21.2 and later. --- bbdb-xemacs.el.orig Fri Jul 24 09:40:35 1998 +++ bbdb-xemacs.el Fri Jul 24 09:41:49 1998 ＠＠ -55,7 +55,7 ＠＠ (set-specifier scrollbar-height (cons (current-buffer) 0))) ;; first delete existing extents (map-extents (function (lambda (x y) - (if (eq (extent-data x) 'bbdb) + (if (eq (extent-property x 'data) 'bbdb) (delete-extent x)))) (current-buffer) (point-min) (point-max) nil) (let ((rest bbdb-records) ＠＠ -271,7 +271,7 ＠＠ (let ((extent (or (extent-at (point) (current-buffer) 'highlight) (error ""))) record field face) - (or (eq (extent-data extent) 'bbdb) + (or (eq (extent-property extent 'data) 'bbdb) (error "not a bbdb extent")) (highlight-extent extent t) ; shouldn't be necessary... (goto-char (extent-start-position extent)) ------- End of forwarded message ------- -- Colin

1 participants
0 comments

Re: vfork revisited (was 64bit clean XEmacs) 25 years, 5 months

Sam Steingold

At the risk of exposing my ignorance, I will ask the basic question that has been bothering my from the times I learned about fork/exec. Why not have an exec-like call which creates a new process (instead of replacing the current one with the new one)? My understanding is that usually exec follows fork and fork is followed by exec - so why not merge the calls? Also, how is vfork different from vork? [linux man says that vfork=fork] Thanks. -- Sam Steingold (http://www.goems.com/~sds) running RedHat5.1 GNU/Linux Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. Trespassers will be shot. Survivors will be prosecuted.

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