annotate src/point.h @ 67313:2ae99b10dd40
* mh-comp.el (mh-forward): Went over all uses of the word "RANGE" in
the docstrings and made usage consistent. Generally speaking,
"messages in range" and "range of messages" is redundant and just
"range" can be used in most circumstances. Also ensured that
mh-interactive-range was mentioned in all interactive functions that
use a range which describes the range argument for both users and
programmers.
* mh-e.el (mh-delete-msg-no-motion, mh-refile-msg)
(mh-refile-or-write-again, mh-rescan-folder, mh-undo)
(mh-visit-folder, mh-scan-folder, mh-regenerate-headers)
(mh-notate-user-sequences, mh-delete-msg-from-seq, mh-catchup): Ditto.
* mh-funcs.el (mh-copy-msg, mh-pack-folder, mh-pack-folder-1): Ditto.
* mh-junk.el (mh-junk-blacklist, mh-junk-whitelist): Ditto.
* mh-print.el (mh-ps-print-range, mh-ps-print-msg)
(mh-ps-print-msg-file, mh-print-msg): Ditto.
* mh-seq.el (mh-put-msg-in-seq, mh-range-to-msg-list)
(mh-narrow-to-range, mh-toggle-tick): Ditto.
| author |
Bill Wohler <wohler@newt.com> |
| date |
Sun, 04 Dec 2005 22:34:49 +0000 |
| parents |
695cf19ef79e |
| children |
375f2633d815 |
| rev |
line source |
|
484
|
1 #define point_width 5
|
|
|
2 #define point_height 19
|
|
|
3 static char point_bits[] = {
|
|
|
4 0x1f, 0x0e, 0x0e, 0x04, 0x04, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
|
|
|
5 0x00, 0x00, 0x04, 0x04, 0x0e, 0x0e, 0x1f};
|
|
52401
|
6
|
|
|
7 /* arch-tag: a8dad510-7254-4964-b71e-bb6f81cce572
|
|
|
8 (do not change this comment) */
|
