While looking through ri File, I found Windows::Security, and in there
is a
method named LookupAccountName. I searched through the mailing list
archives and google, and didn’t see anything in there about it. The
problem
is that I may not understand what’s going on when I’m trying to do a
search
in ri. I got as specific as I could and ri says it can’t find anything,
or
that I need to be more specific…
C:\ruby\programs>ri LookupAccountName
Nothing known about LookupAccountName
C:\ruby\programs>ri Windows::Security#LookupAccountName
More than one method matched your request. You can refine
your search by asking for information on one of:
Windows::Security#LookupAccountName,
Windows::Security#LookupAccountName
Anyway, what I was wondering was what this returned as I’m looking to
create
a script using it to search a user’s my document’s folder (for example).
“c:\documents and settings#{username}” based on who is logged in.
Alternately, you could let me know if there’s a better alternative, let
me
know.
On Dec 6, 2006, at 12:53 , Jason M. wrote:
C:\ruby\programs>ri LookupAccountName
Nothing known about LookupAccountName
C:\ruby\programs>ri Windows::Security#LookupAccountName
More than one method matched your request. You can refine
your search by asking for information on one of:
Windows::Security#LookupAccountName,
Windows::Security#LookupAccountName
Do you have two copies of the gem installed? ri doesn’t handle that
at all
–
Eric H. - [email protected] - http://blog.segment7.net
I LIT YOUR GEM ON FIRE!
Eric,
This is because there are two versions of gems' windows-pr docs
in your system. The ri displays information from those docs. So pls hide
(say, delete/move to aother place ) the doc of one version
(e.g.windows-pr-0.5.3) and use the other one (e.g.
windows-pr-0.5.1-mswin32). And you can get correct info from the command
“ri --gems Windows::Security#LookupAccountName”. Generally the docs
mentioned above are in “C:\Ruby1.8.5(ruby_home)\lib\ruby\gems\1.8\doc”.
Pls reply if still issues.
Shiwei
The views expressed are my own and not necessarily those of Oracle and
its affiliates.