X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil] ["1404" "Thu" "18" "June" "1998" "11:34:48" "+0200" "Hans Aberg" "haberg@MATEMATIK.SU.SE" nil "30" "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 LAA08419; Thu, 18 Jun 1998 11:35:32 +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 <5.A9BBFB4A@listserv.gmd.de>; Thu, 18 Jun 1998 11:35:31 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 364971 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Thu, 18 Jun 1998 11:35:18 +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 LAA29481 for ; Thu, 18 Jun 1998 11:35:11 +0200 (MET DST) Received: from [130.237.37.106] (sl89.modempool.kth.se [130.237.37.115]) by mail.nada.kth.se (8.8.7/8.8.7) with ESMTP id LAA22879 for ; Thu, 18 Jun 1998 11:35:04 +0200 (MET DST) X-Sender: su95-hab@mail.nada.kth.se References: from Hans Aberg at "Jun 17, 98 07:20:22 pm" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Reply-To: Mailing list for the LaTeX3 project In-Reply-To: <9806180437.aa15317@boole.maths.tcd.ie> Date: Thu, 18 Jun 1998 11:34:48 +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: 2570 At 04:37 +0100 98/06/18, Timothy Murphy wrote: >Does this really mean I'll have to say "\math/phi" >every time I want a \phi ? There are two questions: What names to use on a development level, and how to implement features that are easy to the user. On the development level, long names are mainly (I think) the question of the speed of TeX, but I think TeX is not slowed much down by that. It is good if names alway expand to \math/phi or \phys/phi because it makes those names separate and they cannot clash. But on the user level, there must be shortcuts: The user should avoid using those '/' as much as possible. One suggestion would be that the user is allowed to make local definitions: When typing say (inventing a syntax on the fly) it expands to \document/name/my_doc/foo -- the point is that when several documents are blended together, these local definitions can be made globally available if needed. I just jot down some ideas on how the matter could be developed. -- Doing this correctly would need (in the example) a careful study on how to actually blend together several documents, just as the discussions carried out earlier here in this group. Hans Aberg * Email: Hans Aberg * Home Page: * AMS member listing: