Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!rpi.edu!tale From: tale@pawl.rpi.edu (David C Lawrence) Newsgroups: comp.windows.x Subject: Re: awm -- system.awmrc & ~/.awmrc Message-ID: Date: 9 May 89 17:05:45 GMT References: Sender: usenet@rpi.edu Reply-To: tale@pawl.rpi.edu Distribution: comp Lines: 22 In-reply-to: tom@ICASE.EDU's message of 9 May 89 11:52:49 GMT In article tom@ICASE.EDU (Tom Crockett) writes: Tom> I haven't noticed any problem with this. My ~/.awmrc seems to Tom> work fine. Although I do use the reset* commands to completely Tom> override everything, so it's probably not the same situation. Right, it's not the same. ~/.awmrc is certainly being read, the awm startup code and experience show me it is. I bound a test menu to a button which was undefined by system.awmrc and it shows up; however, binding it to a button which had been previously bound in system.awmrc did not result in the binding being replaced. The whole point is to not use reset* directives in ~/.awmrc. Right now our users have 512k diskspace limits -- pretty small (but it really is pretty firm for now). In light of that, being able to keep .*rc files small when you only want to make minimal changes to the defaults is very desirable. The way awm is acting now everyone would have to copy the whole system.awmrc just to change one binding; this is quite contrary to the manual page. Dave -- tale@rpitsmts.bitnet, tale%mts@itsgw.rpi.edu, tale@pawl.rpi.edu