If doc:step moves back further than we expect, search_backwards can loop
forever. So check for that possibility and abort.
Signed-off-by: NeilBrown <neil@brown.name>
Bugs to be fixed
----------------
+- [ ] transparent images appear in email with horiz lines
+- [ ] Replying to w3m/html mail results in unsightly markup in reply
+- [ ] redefining doc:char but not doc:content in mail-compose causes
+ search to get confused. What should we do?
- [ ] why doesn't doc-to-text auto-load
- [ ] use mimetypes.guess_type() to interpret filenames in email attachments??
- [ ] don't allow non-text email parts to appear as text. Maybe hex??
if (mark_ordered_not_same(end, ss.endmark))
break;
ret = maxlen;
+ if (endmark != ss.endmark &&
+ mark_ordered_or_same(ss.endmark, endmark))
+ /* Didn't move forward!! Presumably
+ * buggy doc:step implementation.
+ */
+ break;
+
mark_to_mark(endmark, ss.endmark);
ss.endmark = m;
mark_to_mark(start, endmark);