On Thursday Apr 24 2014, Alexis <[email protected]> wrote: > i've been using the modified version of mu4e-draft.el, which doesn't > apply the read-only property to mail-header-separator, for around a week > now, and have had no further "Can't touch this" errors. > > i'd be interested to know if this change helps Rajagopalan also. If it > does, might this change be made in the master branch, or would that > probably create more problems than it solves? Alternatively, perhaps a > defcustom could be added which would allow users to disable the > application of the read-only property if required? > > If it turns out that this change eliminates the problem only for me, > i'll just create a new branch of my machine, and regularly rebase that > on master.
Thanks for testing this! I don't think the change could break anything, it's only read-only right now to prevent people from accidentally changing that string (which shouldn't happen, really). I'll take the change in, once I'm back home (traveling right now). Cheers, Dirk. -- Dirk-Jan C. Binnema Helsinki, Finland e:[email protected] w:www.djcbsoftware.nl pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C -- You received this message because you are subscribed to the Google Groups "mu-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
