X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["2059" "Thu" "18" "June" "1998" "12:01:04" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "44" "Re: Modules" "^Date:" nil nil "6" nil nil nil nil nil] nil) Received: from listserv.gmd.de (listserv.gmd.de [192.88.97.1]) by mail.Uni-Mainz.DE (8.8.8/8.8.8) with ESMTP id MAA12251; Thu, 18 Jun 1998 12:01:53 +0200 (MET DST) Received: from lsv1.listserv.gmd.de (192.88.97.2) by listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <6.57973801@listserv.gmd.de>; Thu, 18 Jun 1998 12:01:51 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 365049 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 18 Jun 1998 12:01:44 +0200 Received: from mail.nada.kth.se (root@mail.nada.kth.se [130.237.222.92]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id MAA02992 for ; Thu, 18 Jun 1998 12:01:20 +0200 (MET DST) Received: from [130.237.37.106] (sl44.modempool.kth.se [130.237.37.64]) by mail.nada.kth.se (8.8.7/8.8.7) with ESMTP id MAA24505 for ; Thu, 18 Jun 1998 12:01:11 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se References: <13704.121.527407.877988@fell.open.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <199806180546.PAA08908@ricetub.anu.edu.au> Date: Thu, 18 Jun 1998 12:01:04 +0200 From: Hans Aberg Sender: Mailing list for the LaTeX3 project To: Multiple recipients of list LATEX-L Subject: Re: Modules Status: R X-Status: X-Keywords: X-UID: 2571 At 15:46 +1000 98/06/18, Richard Walker wrote: >.. We need some >shortcuts. Here are some possibilities. > >============================================================ >1. Use a variant of the Apple solution: author/product >codes. E.g. assign a four-(hex-)digit code to a developer. Assume I >am allocated a5d4; then my macros begin \a5d4/. . . >There might be special codes for e.g. the LaTeX base and packages. One drawback with such an idea is that somebody would need to assign such codes: But if TeX is not bothered by long names I think it should not be needed, because an user could use "a5d4" as a shortcut expanding to a long name. >============================================================ >2. Extend doc.sty to do the following: >(a) The package writer uses the long names as above when editing the >dtx file. We assume that the writer has the help of a good text >editor to save on keystrokes! Even if one has to write out all the long names by hand, one way to do it is to first use shorter names, and then insert the long names after the package has been developed. But I think that also developers of packages will need developer user commands that simplifies this stuff. Anyway, I think one will have to do some experimenting with how to produce useful shortcuts, while retaining the feature that the long module names do not clash. -- I should perhaps point out that a module (say "math") that wants to supply short names could have a submodule "short", so that if there is a short version of "alpha" in "math" named "al", its long name would be "math/short/al". Then an user could say (inventing a syntax) that expands to \math/short/foo instead of \math/foo. So once one has started with modules, it is possible to supply those things on the logical level, without extra files and stuff. Hans Aberg * Email: Hans Aberg * Home Page: * AMS member listing: