1 10/31/92 CY74 Multics Forum Interactive Meeting System User's Guide
2 Errata Information for MR12.5
3
4
5 pg 3-3: under the section CURRENT TRANSACTION, add the following |
6 to the end of the first paragraph: |
7 |
8 When you enter a meeting, the current transaction is |
9 initially set to the last seen transaction that has not been |
10 deleted or expunged. If there is no seen transaction in the |
11 meeting, "current" will then be set to the first non_deleted |
12 transaction. |
13
14
15 pg 3-4: under the RELATIVE ORDER KEYWORDS section, update |
16 'current' with the following: |
17 |
18 current, c |
19 refers to a transaction that was affected by list, |
20 print, write or reset. |
21
22
23 pg 3-5: in the section SEEN/UNSEEN TRANSACTIONS, update the |
24 keywords 'last_seen' and 'last_unseen" with the following: |
25 |
26 last_seen |
27 refers to the highest-numbered transaction marked as |
28 having been seen. |
29 |
30 last_unseen |
31 refers to the highest-numbered transaction not marked as |
32 having been seen. |
33
34
35 pg 7-17: under the NOTES section of the 'delete' request, add |
36 the following: |
37 |
38 If there are no more non_deleted transactions left after the |
39 old current transaction, "current", is set to the last |
40 un-deleted transaction. |
41
42
43 pg 7-47: under the '-meeting' control argument for 'reply', add |
44 the following: |
45
46
47 The subject will be the subject of the transaction to which |
48 the user is replying. As forum does not chain transactions |
49 across meetings, the transaction which is created in the |
50 meeting_name meeting will not be chained to anything even |
51 though it has a header which is of the standard "Re: |
52 <subject>" format. If the user enters the same request |
53 multiple times, the resulting transactions will not be |
54 chained together, although they will all have the same |
55 title. Note that if a user subsequently attends the |
56 meeting_name meeting and replys to any of the transactions |
57 posted from the first meeting, the user's reply will be |
58 chained to the transaction number in the meeting_name |
59 meeting to which he replied. |
60
61
62 pg 8-2: add the following control argument to the 'forum' |
63 command: |
64 |
65 -auto_write |
66 specifes that the qedx request automatically updates the |
67 message when the user quits the editor. |
68
69
70 pg 8-3: add the following control argument to 'forum' command: |
71 |
72 -no_auto_write |
73 specifes that the qedx request requires the user to use |
74 the 'write' request to update the message before |
75 quitting the editor. Any attempt to exit without |
76 writing results in a query. |