on 3/10/03 12:33 PM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: > On Monday 10 March 2003 15:27, Kurt Bigler wrote:
[snip] >> Been taking a breather. I do still want to check through the "lengthy >> discussions" to make sure there weren't a couple of "tiny" features or >> issues that might have gotten dropped. In any case I am pretty sure these >> won't impact the overall logic in any way. I have a hunch/memory that >> there might be at least one such issue. >> >> It will take me less than an hour this afternoon to do this--just in case >> you want to wait before posting this cleanup. I will try to get to it >> before 3pm pacific time, and probably done by 3:30. > > Go for it. I'm swamped still at work, so I'll be lucky if I can do the cleanup > today. I'm working towards the cleanup, but I just can't be sure that I'll > have time today. [snip rest] Well, I looked, and all I found were a couple of points for the documentation. I only checked briefly, but I don't think these two points have made it into the doc, at least not completely. I think the same concepts apply, although the surrounding details have changed. on 3/1/03 7:46 PM, Kurt Bigler <[EMAIL PROTECTED]> wrote: > As I recall, this "original" functionality can result in 4 ways: > (1) no logindomainlist file > (2) no match found in the logindomainlist file > (3) matching entry has first field empty > (4) matching entry enables popup list, and the blank entry is chosen > > (Possible notes there for the documentation.) and... on 3/3/03 10:36 PM, Kurt Bigler <[EMAIL PROTECTED]> wrote: > on 3/3/03 6:42 AM, Jesse Guardiani <[EMAIL PROTECTED]> wrote: > >>> without the popup is it a default or is >>> it just the login domain? >> >> It's a HARD default. You can't choose anything else. It's a default from the >> perspective of the logindomainlist file, but not necessarily the user. I may >> note this distinction in my docs. > > Good to know. I think that's fine. A short note in the doc will do it. Thats all! -Kurt
