From: henryn <henryn@ms.spacebbs.com>
To: <sourcenav@sources.redhat.com>
Subject: SN4.5.2 Win32 setup/usage for call-freq.tk
Date: Mon, 26 Mar 2001 13:14:00 -0000 [thread overview]
Message-ID: <B6E4F12E.2849%henryn@ms.spacebbs.com> (raw)
Folks:
Could someone give me at least somewhat detailed instructions on how to use
the utility "call-freq.tk" supplied in the SN4.5.2 Win32 release?
I've got as far as a completely functioning SN project, no problem, and I've
grokked that the "hyper.exe" console window is somehow required, but the
path is pretty obscure beyond that.
There's no "usage" comment in "call-freq.tk" and --even if there was-- it's
a bit difficult for those of us not immersed in this technology to see how
what to do with it. I tried the similar utilities --which do have some
usage information-- with no success.
It would be really helpful for someone to give me cookbook guidance on the
order of "given an existing project in directory 'x' with a name 'y', open
window 'z' and utter '<<incantation>>' to get the call frequency
information from the database."
Thanks,
Henry
Henry Neugass
Microsystems Consultant
Palo Alto
650/856-0357
next reply other threads:[~2001-03-26 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 13:14 henryn [this message]
2001-03-26 13:49 ` Ian Roxborough
2001-03-26 15:22 ` henryn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B6E4F12E.2849%henryn@ms.spacebbs.com \
--to=henryn@ms.spacebbs.com \
--cc=sourcenav@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).