From owner-freebsd-ports Mon Aug 12 14:48:04 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA26017 for ports-outgoing; Mon, 12 Aug 1996 14:48:04 -0700 (PDT) Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25984; Mon, 12 Aug 1996 14:47:58 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by sunrise.cs.berkeley.edu (8.7.5/8.6.12) with SMTP id OAA29112; Mon, 12 Aug 1996 14:47:40 -0700 (PDT) Received: from freefall.FreeBSD.ORG by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA20170; Mon, 12 Aug 1996 17:47:45 -0400 Received: from vector.jhs.no_domain (slip139-92-42-173.ut.nl.ibm.net [139.92.42.173]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA25932; Mon, 12 Aug 1996 14:47:27 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id XAA00582; Mon, 12 Aug 1996 23:39:19 +0200 (MET DST) Message-Id: <199608122139.XAA00582@vector.jhs.no_domain> To: "Jordan K. Hubbard" Cc: Chuck Robey , Narvi , "Julian H. Stacey" , bvsmith@lbl.gov, ports%freebsd.org@sunrise.cs.berkeley.edu, gj%freebsd.org@sunrise.cs.berkeley.edu, me%freebsd.org@sunrise.cs.berkeley.edu, asami%freebsd.org@sunrise.cs.berkeley.edu Subject: Re: xfig.3.1.4 extension to support vi -C signals linkage From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Address: Holz Strasse 27d, 80469 Munich, Germany Phone: +49.89.268616 Fax: +49.89.2608126 Web: http://www.freebsd.org/~jhs/ Mailer: EXMH 1.6.7, PGP available In-Reply-To: Your message of "Mon, 12 Aug 1996 06:55:00 PDT." <15717.839858100@time.cdrom.com> Date: Mon, 12 Aug 1996 23:39:19 +0200 Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: "Jordan K. Hubbard" > > > In an ideal world ... True ... every package would come pre designed for ev - er > y > > last eventuality, & we wouldn't need to add anything ;-) > > I'm not asking for a holy grail, I'm simply saying that rather than > modifying n ports in the same way, it would make far more sense to > evolve a more generic communications mechanism that *other* editors > could also use, Well if someone wants to take what I have done & change it to send some appropriate X event, that'd be nice. It'd probably be easy for an experienced X11 hacker to do, as my diffs point the way to where to hack in vi, but many others know more about X than me ... > and would have well-defined hooks for ports authors to > register if they so wished (catching SIGUSR1 is not my definition of a > "hook" :-). Yes, a standardised X event would be more attractive to have. Again, my diffs point the way to where in each port the event handling should be done. Meanwhile it's fully functional with SIGUSR1 (& yes I too felt sqeamish first time I used it, I'd forgotten & got used to it). I'd be willing to later change everything to X events myself, but I don't really know enough, I'd need some very explicit directed RTFMs, & they'd have to be machine readable, I have nothing but the paper pink X Win Sys Usrs Guide for R3 & R4 here, & no spare budget & book shelf space for a meter/yard of new X books. I also have a certain dubious doubt/lack of confidence about vi & other intrinsically non X things handing out X events, whether its wise, whether its easy, whether some intermediate process would be desirable, that would be a signal to X event converter, whether that would increase latency unacceptably. I hope a desire for a later elegance yet to be defined & written won't stop us benefiting from functionality meantime. Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/