Fix info bdes on funny designation arguments

Quoting "?" was accidentally fixed in commit 90631d56, v4.3.11.
Update documentation accordingly.

Closes #736592.
This commit is contained in:
Markus Armbruster 2012-06-10 17:36:07 +02:00
parent 150b2c5165
commit bf11d42c87

View file

@ -17,11 +17,11 @@ change them back, the sector will be updated normally by nav, march, etc.
(The normal use for these is to record minefields, so that you can march (The normal use for these is to record minefields, so that you can march
adjacent to the minefield without eliminating the information) adjacent to the minefield without eliminating the information)
.s1 .s1
Unlike normal designation, with bdes, you may use any character. You may use any character with bdes, not just sector designations.
If you wish to use a space, surround it with double quotes: However, certain characters need to be surrounded with double quotes
bdes # " " on the command line, like this:
.s1 .EX bdes # \(dq \(dq
You can't bdesignate something to a ? .EX bdes 47,11 \(dq?\(dq
.s1 .s1
Conditionals do not work with bdes (i.e. bdes # ?des=c C) unless Conditionals do not work with bdes (i.e. bdes # ?des=c C) unless
you own the sector. you own the sector.