17 Jan
2013
17 Jan
'13
6:16 p.m.
On Thu, 17 Jan 2013 12:10:20 +0100
Johannes Kroll <jkroll(a)lavabit.com> wrote:
Sorry, I was wrong about that... I played some more with Phasex and I
found another badly encoded directory in the working directory...
These files
and directories are created when a session is saved via
LASH, JACK Session, or native session management. I've seen this
behavior once before, when first working on LASH support, and it
turned out to be a character encoding problem with LASH supplied
directory names. The only thing I can think of here is to use the
"C" locale instead of obtaining locale from the user's environment,
so I've made this change in v0.14.97-dev. Could you try the latest
in git, and let me know how it goes?
I'm not using LASH, but I did save sessions in Phasex "natively". I
tried the latest git and I don't see the strange directories in the
working directory where I started Phasex. I don't know if they popped
up somewhere else, but I think they were in the WD, so I guess that
fixed it!