On Thu, 22 Dec 2011 09:29:55 -0500, Aaron Ecay wrote:
> Would the problem you had with previous-s-c-prop-change be fixed by the
> patch to the original function I sent in the thread starting at
> id:"m2y5u5cykp.fsf at kcals.intra.maillard.im" ?
AFAIK it does.
/Xavier
On Thu, 22 Dec 2011 09:29:55 -0500, Aaron Ecay wrote:
> Would the problem you had with previous-s-c-prop-change be fixed by the
> patch to the original function I sent in the thread starting at
> id:"m2y5u5cykp.fsf at kcals.intra.maillard.im" ?
I think so, yes. Re-writing the new version I
The advance/rewind functions had become complex, which made it hard to
determine who they are expected to behave. Re-implement them simply in
order to poll user-experience and expectation.
---
Re-introduce the detection of invisible trailers. Using
`previous-single-char-property-change' just
David,
Would the problem you had with previous-s-c-prop-change be fixed by the
patch to the original function I sent in the thread starting at
id:"m2y5u5cykp.fsf at kcals.intra.maillard.im" ?
--
Aaron Ecay
The advance/rewind functions had become complex, which made it hard to
determine who they are expected to behave. Re-implement them simply in
order to poll user-experience and expectation.
---
Re-introduce the detection of invisible trailers. Using
`previous-single-char-property-change' just
David,
Would the problem you had with previous-s-c-prop-change be fixed by the
patch to the original function I sent in the thread starting at
id:m2y5u5cykp@kcals.intra.maillard.im ?
--
Aaron Ecay
___
notmuch mailing list
notmuch@notmuchmail.org
