Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sun-barr!ccut!wnoc-tyo-news!dclsic!sjc!spider!leia!harkcom From: harkcom@potato.pa.Yokogawa.CO.JP (Alton Harkcom) Newsgroups: comp.windows.x Subject: Re: xdm => bug (or should I call it an insect) Message-ID: Date: 29 Aug 90 23:08:26 GMT References: <9008160412.AA18389@xenon.lcs.mit.edu> Sender: news@leia.pa.yokogawa.co.jp Organization: Yokogawa Electric Corporation, Tokyo, Japan. Lines: 26 In-reply-to: paul@ixi.uucp's message of 20 Aug 90 15:18:18 GMT In article paul@ixi.uucp (Paul Davey) writes: =}I have another way of making my window manager run with a customised =}environment, =} [xdm stuff deleted] But you are still entering through an xterm with the -ls option. That is something that almost nobody does here. Without using ax xterm, it is impossible to use you .login file as if you were logging in. Note to Consortium: No matter what you call it, xdm handles a person logging in yet makes it impossible to use the .login file. Any situation which allows the reading of .login doesn't allow for checking envar's or using stty and such. If xdm wants to act like a login shell make it act like a login shell instead of only doing half the job. If you don't want it to act like a login shell then don't let it log users in. -- -- $@2#2OEE5!3t<02q