4 Q: Can I recall the old value in editor?
6 A: Yes, use up arrow to recall the old value.
9 Q: How to query all addresses when I press 'Q' in mutt?
11 A: Type "all" to the prompt.
14 Q: Can I mark multiple addresses in mutt after a query?
16 A: You can tag addresses with 't'. When ready, type ";m" (press first ';'
17 and then 'm') and all tagged addresses will appear to your "To:"
21 Q: How to insert an address (or many) with abook when I'm forwarding
22 a message in mutt? ("To:" and "Cc:" prompts)
24 A: When "To:" or "Cc:" prompt appears press ^t for query. (After query
25 you can tag multiple addresses with 't')
28 Q: Can I add addresses to the abook addressbook from mutt?
30 A: Yes, it is possible starting from abook version 0.4.15. See --add-email
31 command line option and README.
34 Q: How can I import my abook entries to my PalmOS addressbook?
36 A: Export to palmcsv format, and import from there. Several GUI
37 applications such as jpilot can do this, but the simplest way is to
38 use pilot-addresses from the pilot-link package. Just export to
39 addresses.palmcsv, then run this:
41 pilot-addresses -d abook -c abook -r addresses.palmcsv
43 This will delete everything in the abook category and replace it with
44 the latest information from your abook database. By keeping your
45 abook entries in a separate category, you can continue to add and
46 modify entries in other categories manually, and pilot-addresses will
47 not change or delete them.
48 (This entry was contributed by Jeff Covey)
50 Q: Can I use abook in UTF-8 terminal emulator?
52 A: Yes, the version 0.5.2 added a multibyte character support.
54 There are currently some issues:
56 - Addressbook files must have the same encoding as you use with abook.
57 If you have used abook previously with ISO-8859-1 encoding you can
58 convert the addressbook files with iconv(1). For example:
60 $ iconv -f ISO-8859-1 -t UTF-8 < ~/.abook/addressbook.old > \
61 ~/.abook/addressbook.new
63 - Filters will output strings using multibyte representation of the used
64 locale. This is incorrect for (most of) filters. You can again use
65 iconv to convert between encodings. Same goes with input filters. If
66 you use UTF-8 charset the input is expected to be UTF-8 encoded.