README.claws 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346
  1. README.claws
  2. ------------
  3. Summary:
  4. 1. What is Sylpheed Claws?
  5. 2. Switching between Sylpheed Claws and Sylpheed
  6. * From Sylpheed to Sylpheed Claws
  7. * From Sylpheed Claws to Sylpheed
  8. 3. Things Claws does different
  9. * auto address replacement in summary view
  10. * manual selection of MIME types for attachments
  11. * sharing mail folders
  12. * default to address for folders
  13. * threading mode per folder
  14. * simplify subject string
  15. * pixmap themes
  16. * user definable actions
  17. * spell checking (with installation instructions)
  18. 4. How to contribute
  19. 5. How to request features
  20. 6. Installing Claws from CVS
  21. 7. History
  22. 1. What is Sylpheed Claws?
  23. --------------------------
  24. Sylpheed Claws is a bleeding edge branch of Sylpheed, a light weight mail
  25. user agent for UNIX. Features in this branch may (or may not) end up in
  26. Sylpheed.
  27. Hiroyuki's ChangeLog is also included in the claws-branch distribution,
  28. so it should be easy to spot which features were merged with Sylpheed
  29. (and which features were not).
  30. For brevity Sylpheed Claws is referred to as Claws, and Sylpheed as either
  31. Sylpheed or Main.
  32. 2. Switching between Sylpheed Claws and Sylpheed
  33. ------------------------------------------------
  34. From Sylpheed to Sylpheed Claws
  35. -------------------------------
  36. From the user perspective Claws is just a fancy Sylpheed, so it uses the
  37. same sylpheed setting files located in ~/.sylpheed.
  38. It's always a good idea to back up all files in ~/.sylpheed in case
  39. you want to switch back to Sylpheed. (You don't have to backup the
  40. directories.)
  41. There are some things that frequently come up when switching to Claws:
  42. * Why does the advanced filtering system not work?
  43. Claws uses the new filtering system as soon as you define a new rule for it.
  44. Your old sylpheed filter rules will not be used. In subdirectory tools/ of
  45. the distribution there is a Perl script called filter_conv.pl which convers
  46. old filter rules to the claws filtering system.
  47. * What happened to the compose email and compose news buttons?
  48. There's a composite button for both composing mail and news. You can toggle
  49. between composing mail and news by clicking on the button with the triangle.
  50. * And to the Preferences and Execute buttons?
  51. Sorry, they're not there.
  52. From Sylpheed Claws to Sylpheed
  53. -------------------------------
  54. Moving from Claws to Sylpheed is also simple. Sylpheed should neglect the things
  55. Claws put in the settings files. This also means that the old rules will work
  56. again.
  57. If you want to switch back to Claws at a later time, make sure you back up at least
  58. ~/.sylpheed/filteringrc (the Claws filtering rules), and ~/.sylpheed/sylpheedrc
  59. (which may have some claws specific settings).
  60. When switching back to Sylpheed you will not lose messages or message flags (color
  61. labels, read / unread status of messages).
  62. 3. Things Claws does different
  63. ------------------------------
  64. Claws does a lot of things different. Here a quick run-down of things that
  65. are hardly noticable, but deserve mentioning:
  66. * auto address replacement in summary view
  67. This matches a plain email address with a person in the address book. This
  68. feature is enabled in Common Preferences | Tab Display | SummaryView Group |
  69. Display sender using addressbook
  70. * manual selection of MIME types for attachments
  71. You can change the MIME type of an attachment by right-clicking in the
  72. attachment list, selecting Property in the menu. The MIME type list
  73. is a combo box with the known MIME types.
  74. * sharing mail folders
  75. You can also share or use shared mail folders. Right-click a folder and
  76. select Property. Change the Folder chmod setting.
  77. * default to address for folders
  78. Most people filter mailing list mails to separate folders. Claws allows
  79. you to associate a folder with a mailing list or a person. Right-click a
  80. folder, select Property and change the Default To setting. When you
  81. compose a new mail, when this folder is selected the recepient address
  82. will be set to this address.
  83. (NOTE: this is also a shoot-yourself-in-the-foot-setting! If you want
  84. to send a private mail, don't have a folder selected with this setting
  85. set.)
  86. * pixmap themes
  87. To use different icon sets you need to create a directory:
  88. mkdir ~/.sylpheed/themes
  89. Icon sets should be placed in this directory in their own sub-directory.
  90. They are then selectable from Pixmap Theme on the Interface tab of Commmon
  91. Preferences.
  92. * user definable actions
  93. Actions can be executed on message text view, or on the message's file.
  94. To configure new actions use Configuartion->Actions. Your actions are
  95. then available from Edit->Actions in the main window and compose window.
  96. * Spell checker for Sylpheed-Claws
  97. a. Requirements
  98. b. Configuration and installation
  99. c. Usage
  100. d. Known problems
  101. a. Requirements
  102. ---------------
  103. The spell checker in sylpheed requires the Portable Spell Checker
  104. Interface Library pspell (http://pspell.sourceforge.net), version
  105. 0.12.2 or newer.
  106. You will need also the actual spell checker. There are two alternatives:
  107. i) ispell (http://fmg-www.cs.ucla.edu/fmg-members/geoff/ispell.html),
  108. which is found on quasi every distribution. You have then to
  109. install the pspell-ispell module found at the pspell site.
  110. ii) aspell (http://aspell.sourceforge.net). This spell checker
  111. must be installed after installing pspell. The version tested
  112. is .33.7 alpha. It has three different suggestion modes (fast
  113. -default- , normal, bad spellers), has the ability to learn
  114. from mistakes (default).
  115. And, last but not least, do not forget to install the dictionaries. Check
  116. the corresponding spell checker home page for more information on this.
  117. b. Configuring Sylpheed
  118. -----------------------
  119. Spell checking is enabled if you configure sylpheed appropriately. Add
  120. the option '--enable-pspell' when configuring. E.g.:
  121. ./configure --enable-pspell
  122. The configure script needs 'pspell-config' in your path. If it is
  123. in weird places, use '--with-pspell-prefix' to tell the path to
  124. pspell-config. E.g., if pspell-config is really
  125. /foo/bar/pspell-config, then use:
  126. ./configure --enable-pspell --with-pspell-prefix=/foo/bar
  127. If you have problems with not found includes or libraries, check
  128. first where these are located, and add either options:
  129. --with-pspell-includes=/foo/bar/include
  130. or
  131. --with-pspell-libs=/foo/bar/lib
  132. as appropriate.
  133. Configure script summarizes the options compiled in. Check that
  134. configure lists 'Pspell = yes'.
  135. Then proceed as usual, with 'make' and 'make install'.
  136. c. Usage
  137. --------
  138. NOTE: if you upgraded from 0.7.0claws, please reselect your default
  139. dictionary in the preferences.
  140. After successful compiling, you need to tell sylpheed where your
  141. dictionaries reside. First run 'pspell-config pkgdatadir' on the
  142. shell to get their path.
  143. Then run sylpheed and go to Configuration -> Common preferences ->
  144. Spell Checker. Check the box 'Enable spell checker (EXPERIMENTAL)' and
  145. use the file selector ('...' button) to select the path where the
  146. dictionaries reside. Within the file selector, go to that directory
  147. and select *any* file in the file lists. Click ok. You should then
  148. be able to select your default dictionary.
  149. When composing, misspelled words are highlighted. Click on any
  150. highlighted word with the right mouse button to get a list of
  151. suggestions. The first entry of the menu just displays the unknown
  152. word. Selecting "Accept in this session" (or hitting MOD1-Space,
  153. where MOD1 is usually the ALT key), will ignore this word and accept
  154. it in this message. Selecting the next entry "Add to dictionary", which
  155. is bound to MOD1-Enter combination will add the unknown word to the
  156. dictionary to learn it. The next entries are the suggested words.
  157. The first 15 suggestions can be accessed typing one of the first letters
  158. of latin alphabet (if this does not suit your language, please send
  159. a mail to melvin.hadasht@free.fr). If you are using an aspell
  160. dictionary, you can use its 'learn from mistake' feature, by pressing
  161. the MOD1 key and selecting the suggestion (with the keyboard or with
  162. the mouse). See pspell manual §4.7.1 for an explanation of this
  163. feature.
  164. If you click with the right mouse button everywhere else, or if you
  165. shift-right-click even on a misspelled word, you get the
  166. configuration menu. 'Check all' highlights all misspelled words.
  167. With this menu, you can also change the dictionary while editing.
  168. FInally, you can change the suggestion mode misktakes 'feature'
  169. (useful only with aspell).
  170. Spell checking can also be done using keyboard shortcuts. In the
  171. "Edit" menu of the compose window, there are two menus "Check backwards
  172. misspelled word" and "Forward to next misspelled word". Add to them
  173. appropriate keyboard shortcuts. "Check backwards misspelled word"
  174. checks backwards from cursor position for the first misspelled word.
  175. If it finds one, it displays the suggestions lists which can be handled
  176. with the keyboard as described before. When the suggestion menu is
  177. closed, the cursor returns to its original position to be able to
  178. continue editing. The "Forward to next misspelled word" do the same
  179. thing in the other direction but moves the cursor at the end of the
  180. misspelled word. This way, you can spell check easily a whole message
  181. starting from its beginning and using the "Forward to next misspelled
  182. word" keyboard short cut.
  183. d. Known problems
  184. -----------------
  185. i) libtool
  186. The only real known problems until now are configuration and
  187. compilation problems due to libtool interaction with pspell.
  188. If you do not compile pspell/aspell/pspell-ispell yourself, you
  189. need to install them with their devel packages.
  190. Pspell work with dynamic linking of libraries and thus uses the
  191. libltdl library of libtool. If you have weird problems when
  192. configuring showing 'libtool', chances are the libtool used when
  193. compiling the pspell package is not compatible with what you have
  194. on your system. The best solution, is to install the latest
  195. libtool AND compile yourself pspell package. I can't help more
  196. than that in this issue.
  197. After successfully compiled and used sylpheed with spell checking,
  198. the same problem can appear if you upgrade your libtool to a
  199. version which libltdl is incompatible to your older one. The
  200. symptoms are a crash when starting to compose. Disabling spell
  201. checking avoids the problem. The solution should be to recompile pspell.
  202. ii) New installed ispell dictionary are not detected
  203. Installing a new ispell dictionary needs an additional step. Go
  204. to the 'pkgdatadir' and run 'make-ispell-pwli'. You may need to
  205. su root.
  206. * simplify subject string
  207. It is possible to remove parts of string from the subject line.
  208. Example: [Sylpheed-claws-users] This is a test
  209. becomes: This is a test
  210. This is a per folder property. Right click on a folder and select
  211. property, enable Simplify Subject RegExp check box. Example
  212. regexp for the above is: \[Sylpheed-claws-(devel|users)\]
  213. Another example for the Sylpheed mailing list (not claws!) is:
  214. \[sylpheed:[0-9]{5}\]
  215. There are a lot more options. If you find one, don't hesitate to
  216. mention it.
  217. 4. How to contribute
  218. --------------------
  219. Sylpheed Main:
  220. submit it to the Sylpheed ML, Hiroyuki, or Paul Mangan
  221. (for incorporation on the Sylpheed Patches page)
  222. Sylpheed Claws:
  223. It is highly recommended to use the sourceforge project page
  224. of claws. Check:
  225. http://sourceforge.net/tracker/?atid=384600&group_id=25528&func=browse
  226. If that's too troublesome, either contact Paul Mangan or consider
  227. posting to the sylpheed claws users mailing list.
  228. Bugs can be reported in the same way; the recommended web page:
  229. http://sourceforge.net/tracker/?group_id=25528&atid=384598
  230. Ofcourse you can also post to the sylpheed claws users
  231. mailing list.
  232. Also, we really try to incorporate good contributions, but sometimes we
  233. don't have enough time. If the contribution is really big, or requires
  234. a long time to stabilize, send a mail to Paul Mangan. We can probably
  235. arrange access to the Claws branch.
  236. 5. How to request features
  237. --------------------------
  238. Ask around in both Sylpheed ML and Sylpheed Claws Users ML. Note
  239. that some developers may already thought about your feature, may
  240. perhaps be implementing it - or the feature was already discussed
  241. and rejected for whatever reason. You might want to go ahead and
  242. hack a patch for it. (That would be very cool!) Another
  243. possibility is to use the Feature Request Tracker at the
  244. sourceforge project page.
  245. 6. History
  246. ----------
  247. TODO