forked from pushcx/sup
-
Notifications
You must be signed in to change notification settings - Fork 2
/
ReleaseNotes
102 lines (69 loc) · 3.86 KB
/
ReleaseNotes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
Release 0.11:
The deprecated Ferret index has been removed.
Remote sources (IMAP, IMAPS, and mbox+ssh) have been deprecated and will be
removed in 0.12. Tools like offlineimap, fetchmail, and rsync provide a much
better user experience for these mail sources than Sup would ever be able to by
itself.
If your terminal supports it you can now use 256 colors in your colorscheme. Run
the contrib/colorpicker.rb program to get the color names to put in colors.yaml.
Saved searches are now supported. Hit '%' in search-results-mode to save the
current search, and enter an empty search string to open the list of saved
searches.
Release 0.10:
The Xapian backend is now the default. Convert your old, crash-prone Ferret
index to Xapian by running sup-convert-ferret-index.
Using a Ferret backend will produce a deprecation notice, and will not be
supported in 0.11.
Many thanks to Rich Lane.
Release 0.9.1:
This is mainly a bugfix release, with a couple minor new features rolled up.
If you are using the Ferret backend, consider convering soon. I will probably
add a deprecation notice in 0.10, and you support will be dropped in 0.11.
Release 0.9:
There's a new Xapian backend as an alternative to the Ferret one. It's still in
a beta stage. It's much faster and much less prone to the random crashes than
Ferret, but certain things don't work yet, most noticeably the unread message
counts in label-list-mode.
You can switch back and forth between both indexes without harm, *except* any
new messages added to the one index won't be picked up by the other. Follow
these instructions:
To TRY the Xapian index, without screwing Ferret up:
1. sup-dump > dump # takes a while
2. export SUP_INDEX=xapian # or however you do it in your shell
3. sup-sync --all --all-sources --restore dump # takes a long time
4. sup -n # -n ensures that no polling is done. don't hit 'P' either
Step 1 will take a long time, and step 3 will take a very long time.
At this point, whenever you run Sup, the SUP_INDEX environment variable will
determine which index you use. If it's unset, or "ferret", you will use the
ferret index. If it's "xapian", the Xapian index. Make sure when you run sup
with the Xapian index, you use -n and don't hit 'P', to avoid loading new
messages into it.
If you want to switch to Xapian permanently, you can then:
1. rm -rf ~/.sup/ferret
2. permanently set SUP_INDEX=xapian according to your shell
3. Run sup as normal, i.e. without -n.
If you want to go back to Ferret, you can just rm -rf ~/.sup/xapian and make
sure your SUP_INDEX environment variable is unset.
Release 0.8.1:
A bugfix release with fixes for quote parsing (bad behavior in certain long
emails), multibyte display for non-utf8 locales, and reply-mode mode selection.
Release 0.8:
The big wins are undo support, mbox splitting fixes, and the various UI
speedups and bugfixes. Parsing new email should also be faster, although
IMAP remains tragically slow, as usual.
Release 0.7:
The big win in this release is that Ferret index corruption issues should now
be fixed, thanks to an extensive programming of locking and
thread-safety-adding.
The other nice change is that text entry will now scroll to the right upon
overflow, thanks to some arcane Curses magic that Steve Goldman discovered.
As always, this release includes many other bugfixes and enhancements.
Release 0.6:
Message attachment searchability automatically takes effect on new messages,
but if you want it on older ones, you'll have to reindex them. See the
instructions below, and the help for sup-sync, for how to do this.
Release 0.5:
Saving message state (pressing "$") has been sped up. However, this is only
automatically in effect for new messages. To make it effective for older
messages (i.e. messages indexed with versions of Sup before 0.5), you must
reindex them, e.g. by running sup-sync --all on a source.