3 acme \- control files for text windows
17 The text window system
19 serves a variety of files for reading, writing, and controlling
21 Some of them are virtual versions of system files for dealing
22 with the virtual console; others control operations
26 When a command is run under
28 a directory holding these files is posted as the 9P service
33 Some of these files supply virtual versions of services available from the underlying
34 environment, in particular the character terminal files in Plan 9's
40 sees the same set of files; there is not a distinct
43 Other files are unique to
47 is a subdirectory used by
51 as a mount point for the
53 files associated with the window in which
56 It has no specific function under
61 is the standard and diagnostic output file for all commands
64 (Input for commands is redirected to
68 appears in a window labeled
72 is the directory in which the command
74 The window is created if necessary, but not until text is actually written.
77 is an empty unwritable file present only for compatibility; there is no way
78 to turn off `echo', for example, under
82 holds a sequence of lines of text, one per window. Each line has 5 decimal numbers,
83 each formatted in 11 characters plus a blank\(emthe window ID;
84 number of characters (runes) in the tag;
85 number of characters in the body;
86 a 1 if the window is a directory, 0 otherwise;
87 and a 1 if the window is modified, 0
88 otherwise\(emfollowed by the tag up to a newline if present.
89 Thus at character position 5×12 starts the name of the window.
90 If a file has multiple zeroxed windows open,
91 only the most recently used will appear in the
96 is an empty file, writable without effect, present only for compatibility with
100 reports a log of window operations since the opening of the
103 Each line describes a single operation using three fields separated by single spaces:
104 the decimal window ID, the operation, and the window name.
107 blocks until there is an operation to report, so reading the file
108 can be used to monitor editor activity and react to changes.
109 The reported operations are
113 (window creation via zerox),
119 The window name can be the empty string; in particular it is empty in
121 log entries corresponding to windows created by external programs.
124 is a directory analogous to the numbered directories
129 creates a new window. Thus to cause text to appear in a new window,
132 For more control, open
134 and use the interface described below.
139 window has associated a directory numbered by its ID.
140 Window IDs are chosen sequentially and may be discovered by the
146 indirectly through the
148 file. The files in the numbered directories are as follows.
151 may be written with any textual address (line number, regular expression, etc.),
152 in the format understood by button 3 but without the initial colon, including compound addresses,
153 to set the address for text accessed through the
156 When read, it returns the value of the address that would next be read
157 or written through the
165 are character (not byte) offsets. If
169 are identical, the format is just
171 Thus a regular expression may be evaluated by writing it to
176 address has no effect on the user's selection of text.
179 holds contents of the window body. It may be read at any byte offset.
182 is always appended; the file offset is ignored.
185 may be read to recover the five numbers as held in the
187 file, described above, plus five more fields: the width of the
188 window in pixels; the name of the font used in the window;
189 the width of a tab character in pixels; a 1 if there is undo history, 0 otherwise;
190 a 1 if there is redo history, 0 otherwise.
191 Text messages may be written to
193 to affect the window.
194 Each message is terminated by a newline and multiple
195 messages may be sent in a single write.
202 address to that of the user's selected text in the window.
205 Mark the window clean as though it has just been written.
208 Mark the window dirty, the opposite of clean.
211 Remove all text in the tag after the vertical bar.
224 Set the user's selected text in the window to the text addressed by the
229 Set the command string to recreate the window from a dump file.
231 .BI dumpdir " directory
232 Set the directory in which to run the command to recreate the window from a dump file.
237 interactive command with no arguments; accepts no arguments.
242 interactive command with a single (required) argument.
247 file is first opened, regular expression context searches in
249 addresses examine the whole file; this message restricts subsequent
250 searches to the current
257 returning the window to the usual state wherein each modification to the
258 body must be undone individually.
261 Set the name of the window to
265 Turn off automatic `marking' of changes, so a set of related changes
266 may be undone in a single
273 interactive command with no arguments; accepts no arguments.
276 Guarantee at least some of the selected text is visible on the display.
281 is used in conjunction with
283 for random access to the contents of the body.
284 The file offset is ignored when writing the
286 file; instead the location of the data to be read or written is determined by the state of the
289 Text, which must contain only whole characters (no `partial runes'),
292 replaces the characters addressed by the
294 file and sets the address to the null string at the end of the written text.
297 returns as many whole characters as the read count will permit starting
298 at the beginning of the
300 address (the end of the address has no effect)
301 and sets the address to the null string at the end of the returned
307 file appends to the body of the
311 is the directory currently named in the tag.
312 The window is created if necessary,
313 but not until text is actually written.
318 file is open, changes to the window occur as always but the
319 actions are also reported as
320 messages to the reader of the file. Also, user actions with buttons 2 and 3
325 which behave normally) have no immediate effect on the window;
326 it is expected that the program reading the
328 file will interpret them.
329 The messages have a fixed format:
330 a character indicating the origin or cause of the action,
331 a character indicating the type of the action,
332 four free-format blank-terminated decimal numbers,
333 optional text, and a newline.
334 The first and second numbers are the character addresses of the action,
336 and the final is a count of the characters in the optional text, which
337 may itself contain newlines.
338 The origin characters are
346 for actions through the window's other files,
348 for the keyboard, and
351 The type characters are
353 for text deleted from the body,
355 for text deleted from the tag,
357 for text inserted to the body,
359 for text inserted to the tag,
361 for a button 3 action in the body,
363 for a button 3 action in the tag,
365 for a button 2 action in the body, and
367 for a button 2 action in the tag.
369 If the relevant text has less than 256 characters, it is included in the message;
370 otherwise it is elided, the fourth number is 0, and the program must read
373 file if needed. No text is sent on a
385 the flag is always zero.
390 the flag is a bitwise OR (reported decimally) of the following:
391 1 if the text indicated is recognized as an
394 2 if the text indicated is a null string that has a non-null expansion;
395 if so, another complete message will follow describing the expansion
396 exactly as if it had been indicated explicitly (its flag will always be 0);
397 8 if the command has an extra (chorded) argument; if so,
398 two more complete messages will follow reporting the argument (with
399 all numbers 0 except the character count) and where it originated, in the form of
400 a fully-qualified button 3 style address.
406 the flag is the bitwise OR of the following:
409 can interpret the action without loading a new file;
410 2 if a second (post-expansion) message follows, analogous to that with
413 4 if the text is a file or window name (perhaps with address) rather than
416 For messages with the 1 bit on in the flag,
417 writing the message back to the
419 file, but with the flag, count, and text omitted,
420 will cause the action to be applied to the file exactly as it would
423 file had not been open.
426 holds contents of the window tag. It may be read at any byte offset.
429 is always appended; the file offset is ignored.
436 except that reads stop at the end address.
