document pseudo-class 'P' slightly better
Inspired by the diff from entrez. I didn't care for 'time'. I don't like 'novelty' much either, but it is a little more accurate since there is no time factor involved with just-picked-up.
This commit is contained in:
@@ -764,10 +764,13 @@ use a menu to pick which object(s) to drop.
|
|||||||
drop only unpaid food.
|
drop only unpaid food.
|
||||||
.PE
|
.PE
|
||||||
The last example shows a combination.
|
The last example shows a combination.
|
||||||
There are three categories of object filtering: class (\(oq!\(cq for
|
There are four categories of object filtering: class (\(oq!\(cq for
|
||||||
potions, \(oq?\(cq for scrolls, and so on), shop status (\(oqu\(cq for
|
potions, \(oq?\(cq for scrolls, and so on), shop status (\(oqu\(cq for
|
||||||
unpaid, in other words, owned by the shop), and bless/curse state
|
unpaid, in other words, owned by the shop), bless/curse state
|
||||||
(\(oqB\(cq, \(oqU\(cq, \(oqC\(cq, and \(oqX\(cq as shown above).
|
(\(oqB\(cq, \(oqU\(cq, \(oqC\(cq, and \(oqX\(cq as shown above),
|
||||||
|
and novelty (\(oqP\(cq, recently picked up items; controlled by picking
|
||||||
|
up or dropping things rather than by any time factor).
|
||||||
|
.lp ""
|
||||||
If you specify more than one value in a category (such as \(lq!?\(rq for
|
If you specify more than one value in a category (such as \(lq!?\(rq for
|
||||||
potions and scrolls or \(lqBU\(rq for blessed and uncursed), an inventory
|
potions and scrolls or \(lqBU\(rq for blessed and uncursed), an inventory
|
||||||
object will meet the criteria if it matches any of the specified
|
object will meet the criteria if it matches any of the specified
|
||||||
|
|||||||
@@ -861,10 +861,14 @@ the bless\-ed/\-un\-curs\-ed/\-curs\-ed groups may be typed.\\
|
|||||||
%.ei
|
%.ei
|
||||||
%.ed
|
%.ed
|
||||||
The last example shows a combination.
|
The last example shows a combination.
|
||||||
There are three categories of object filtering: class (`{\tt !}' for
|
There are four categories of object filtering: class (`{\tt !}' for
|
||||||
potions, `{\tt ?}' for scrolls, and so on), shop status (`{\tt u}' for
|
potions, `{\tt ?}' for scrolls, and so on), shop status (`{\tt u}' for
|
||||||
unpaid, in other words, owned by the shop), and bless/curse state
|
unpaid, in other words, owned by the shop), bless/curse state
|
||||||
(`{\tt B}', `{\tt U}', `{\tt C}', and `{\tt X}' as shown above).
|
(`{\tt B}', `{\tt U}', `{\tt C}', and `{\tt X}' as shown above),
|
||||||
|
and novelty (`{\tt P, recently picked up items; controlled by picking
|
||||||
|
up or dropping things rather than by any time factor).
|
||||||
|
%.lp ""
|
||||||
|
\\
|
||||||
If you specify more than one value in a category (such as ``{\tt !?}'' for
|
If you specify more than one value in a category (such as ``{\tt !?}'' for
|
||||||
potions and scrolls or ``{\tt BU}'' for blessed and uncursed), an inventory
|
potions and scrolls or ``{\tt BU}'' for blessed and uncursed), an inventory
|
||||||
object will meet the criteria if it matches any of the specified
|
object will meet the criteria if it matches any of the specified
|
||||||
|
|||||||
@@ -467,11 +467,13 @@ allow_category(struct obj *obj)
|
|||||||
set_bknown(obj, 1);
|
set_bknown(obj, 1);
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* There are three types of filters possible and the first and
|
* Version 3.6 had three types of filters possible and the first
|
||||||
* third can have more than one entry:
|
* and third can have more than one entry:
|
||||||
* 1) object class (armor, potion, &c);
|
* 1) object class (armor, potion, &c);
|
||||||
* 2) unpaid shop item;
|
* 2) unpaid shop item;
|
||||||
* 3) bless/curse state (blessed, uncursed, cursed, BUC-unknown).
|
* 3) bless/curse state (blessed, uncursed, cursed, BUC-unknown).
|
||||||
|
* Version 3.7 added a fourth:
|
||||||
|
* 4) 'novelty' ('P' for just picked up items).
|
||||||
* When only one type is present, the situation is simple:
|
* When only one type is present, the situation is simple:
|
||||||
* to be accepted, obj's status must match one of the entries.
|
* to be accepted, obj's status must match one of the entries.
|
||||||
* When more than one type is present, the obj will now only
|
* When more than one type is present, the obj will now only
|
||||||
|
|||||||
Reference in New Issue
Block a user