[5646] in Athena Bugs

home help back first fref pref prev next nref lref last post

7.0: /usr/athena/lib/init/login: DEF_TERM

daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed Aug 1 08:41:41 1990

Date: Wed, 1 Aug 90 08:41:21 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: raeburn@MIT.EDU
Cc: bugs@ATHENA.MIT.EDU
In-Reply-To: raeburn@MIT.EDU's message of Wed, 25 Jul 90 16:55:24 EDT <9007252055.AA11961@multics.MIT.EDU>

   From: raeburn@MIT.EDU
   Date: Wed, 25 Jul 90 16:55:24 EDT

   Hmph.  I've tried that route [athena-ws] before, for different
   problems.  What is the step after that?

1. I monitor athena-ws for things that were discussed in bugs and
   referred there.  If the consensus seems to be in favor of the
   change being proposed, I reintroduce it as a bug report, and if
   necessary, get some people together to talk about it face-to-face.

2. If you don't see that happening, you can resubmit it as a new bug
   report, this time prefixing the report with, "Most people in
   athena_ws agree with me on this," or something like that.

   Why couldn't the appropriate "unsetenv" commands be run as part of the
   standard login startup?  It seems to be that $DEF_TERM is all but
   useless after it's finished.

This sounds reasonable -- unsetenv DEF_TERM by default, so that users
who want it will have to store it in another environment variable.
Alternatively, just make it a shell variable as you've already
suggested.

However, this does mean that we'll break the log-in files of people
who use the variable later in the files.  I'm one of those people.

  jik

home help back first fref pref prev next nref lref last post