Original author: email@example.com (June 27, 2009 22:35:23)
I believe this is another issue with the vty lib. I don't have easy access to a gnome terminal so
haven't been able to play around with it.
Original issue: http://code.google.com/p/hledger/issues/detail?id=4
From s.asta...@gmail.com on July 06, 2009 22:32:27
Also in xterm ui command corrupts all unicode strings (but in Gnome Terminal there is
also a “border” around). I suppose we are not encoding/decoding UTF-8 properly (as
From firstname.lastname@example.org on July 09, 2009 00:07:40
Sergey - do you mean hledger ui in xterm works, but with non-ascii characters appearing corrupted ?
For me, in xterm on mac osx, it dies with Prelude.chr: bad argument, issue #3.
Do you think the problem is something we can work around, so that vty would be happy ? I have been assuming
Also, is it time we switched to the new unicode-aware text library ?
From email@example.com on July 09, 2009 21:30:02
Re my last comment, hledger using text would not help this issue. utf8-string is still needed for doing I/O. I
think the only fix is to help the vty project which seems stalled, find an alternative lib or drop the ui command
for now. Focus on the command-line and web interfaces. Comments welcome.
From firstname.lastname@example.org on July 09, 2009 21:33:40
PS, I think the discussion above should continue on issue #3 which is about unicode. This issue, #4, is about
invocations of the ui command which work in xterm but fail in gnome-terminal.
From email@example.com on September 23, 2009 15:11:53
This should be fixed with latest hledger and vty 126.96.36.199.