Bluefish 1.3.6 (which is in portage) has a nasty bug that prevents it from starting until you delete or modify adequately the session file in ~/.bluefish-unstable/session, this is fixed in 1.3.7 which has been just released. This thread in the mailing list illustrates the problem. http://permalink.gmane.org/gmane.comp.web.bluefish.user/658 Reproducible: Always Steps to Reproduce: 1. emerge bluefish 1.3.6 and user it 2. eventually, it will refuse to start with a segfault until you get rid of the session file, I have no concrete info on what the trigger is. For me it has been working for some time without exhibiting this problem
Thanks for report. Added to main tree. Also note that i am using the editor only few times in class while i show students how to write html, so i wont be proper maintainer, thus this is non-maintainer commit. :]
