From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Elijah Meeks <elijahmeeks@yahoo.com>
Cc: xconq7@sources.redhat.com
Subject: Re: Action-Notices list
Date: Mon, 26 Jul 2004 01:31:00 -0000 [thread overview]
Message-ID: <4102EE80.4010300@phy.cmich.edu> (raw)
In-Reply-To: <20040724205007.739.qmail@web13125.mail.yahoo.com>
Elijah Meeks wrote:
> The design manual doesn't seem to have any entries for
> the various action-notices and event-notices. I've
> cribbed from games that use this feature but I was
> wondering if anyone knew all the actions that could be
> referenced, especially for event notices.
I think the two best authorities, as of now, are the 'kernel/action.def'
and 'kernel/history.def' files. They list the names of all possible
actions and events, respectively.
In the case of actions, you will see the action's name in quotes right
after "DEF_ACTION(".
In the case of events, you will see the event's name in quotes right
after "DEF_HEVT(".
Eric
next prev parent reply other threads:[~2004-07-24 23:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-17 9:50 Weird fuel behavior Robert Goulding
2004-07-17 9:57 ` Hans Ronne
2004-07-17 14:16 ` Robert Goulding
2004-07-17 20:06 ` Hans Ronne
2004-07-17 20:31 ` Robert Goulding
2004-07-17 21:13 ` Hans Ronne
2004-07-17 21:31 ` Robert Goulding
2004-07-18 13:07 ` Hans Ronne
2004-07-18 20:20 ` Robert Goulding
2004-07-18 22:14 ` Hans Ronne
2004-07-18 22:16 ` Eric McDonald
2004-07-19 2:50 ` Hans Ronne
2004-07-20 8:05 ` Jim Kingdon
2004-07-20 13:38 ` Hans Ronne
2004-07-20 19:19 ` Jim Kingdon
2004-07-20 19:50 ` Hans Ronne
2004-07-20 21:36 ` Eric McDonald
2004-07-20 22:07 ` Hans Ronne
2004-07-20 23:12 ` Eric McDonald
2004-07-21 0:32 ` Stan Shebs
2004-07-21 0:47 ` Eric McDonald
2004-07-21 1:11 ` Hans Ronne
2004-07-21 1:33 ` Eric McDonald
2004-07-24 23:19 ` Action-Notices list Elijah Meeks
2004-07-26 1:31 ` Eric McDonald [this message]
2004-07-21 0:55 ` Weird fuel behavior Hans Ronne
2004-07-24 20:50 ` Eric McDonald
2004-07-20 15:17 ` Eric McDonald
2004-07-20 15:40 ` Jim Kingdon
2004-07-19 3:07 ` Robert Goulding
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=4102EE80.4010300@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=xconq7@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).