Leo editor

Raised as a usability problem by 5 people on Hacker News over 5 years (2017–2021), in 4 threads.

People raised many different problems with Leo editor, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 8 complaints

File menu doesn't follow established conventions, relying on arbitrary layout2021-09-27
Too many overlapping purposes, so user can't figure out how to use it2021-09-26
Multi-megabyte XML file breaks git conflict resolution; sentinels pollute managed files2018-08-16
Many features work badly, don't work at all, or cause data loss2018-08-16
Help area can't be moved or closed, and the shown close shortcut doesn't work2018-08-16
Documentation is poor and outdated, so examples often won't work2018-08-16
Documentation is poor and tutorials are lacking, so it's hard to use day-to-day2017-07-16
Documentation and website are opaque, forcing users to search mailing lists and code2017-02-06