On Thu, 5 Jul 2012 22:14:21 -0700 (PDT) felix74 <[email protected]> wrote:
> I've just searched through the bugs and found this > https://bugs.launchpad.net/leo-editor/+bug/882243 > So I guess that this is a known issue. Unfortunately, It doesn't appear to > be considered to be a serious bug and will not be fixed anytime soon. I've just switched it from Wishlist to Medium and posted this comment on the bug: I think this bug should be revisited. I've switched it from Wishlist to Medium - let's either get it fixed to do what people expect, or switch it to Invalid with a definite ruling on why it's invalid. It seems that unless there's a definite reason not to change it, i.e. changing it would break some existing workflow, it should be changed on the "avoid surprising the user" principle. I know changes to the read/write code are a big deal, but it seems this could be changed at least to see if it breaks any unit tests - after that it might be a case of letting it out in the wild to see what happens. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
