unfortunately, it still does not build on Solaris :-)

what's the error now? i applied your patch...

hm.. for some reason my local version of the configure script sets INTLLIBS but the shipped version doesn't. lemme fiddle with it a bit...

In "about dialog" there is (c)2000-2004 - may be there must be 2000-2005 ?

After installing sqlite3, and the dep tcl, I STILL couldn't get --with-sqlite3 to work until I removed sqlite3 and re-configured THAT build with a --prefix=/usr. Then everything worked.

BTW: that "make test" for sqlite3 runs tens of thousands of tests, almost 15 minutes' worth.

Could you send me more information (like error messages or config.log) from when it failed?

I see 4.5.1 no longer has an accelerator bound to Insert Image at all. Is there a reason not to use <ctl>I for this? LogJam doesn't use <ctl>I for anything else.

FYI, I also bind <ctl>D (which LogJam also does not otherwise use) to Open Draft.

Oh, BTW, I confirm fix of the final-link problem.

Evan, can you please accept this tiny patch? It makes it possible to post backdated entries from files using command line. It is sometimes needed when you export your diary from some other place to LJ, and this was the reason I wrote this.

I'm using 4.4.0 (ubuntu hasn't updated the package yet). I have a minor improvement to make: support amaroK for music detection in the pull down menu. The necessary command is dcop amarok player nowPlaying.

I've added this, so it'll be in the next release. Thanks!

Cool!

Sorry for asking this here - I hope it is appropriate still - but is the Windows version at all available still?
A friend of mine, unlike me a Windows user (which is why I don't have that version stored on my system), wanted to make look into it, specifically since he urgently wants to make a backup of his LJ offline.

I hope you can help me with this, thank you.

-Rofu

Found something...

http://neugierig.org/software/logjam/windows/

This is still functional, isn't it?

Thank you again, and if just for providing a community that one could find help with problems if needed.

-Rofu

That might be functional, but it's old enough that I wouldn't trust it being bug-free.

I haven't yet built a version for Windows, but it shouldn't be too hard (I hope!).

Here's what's left of the Debian patches to LogJam 4.5.1. These were all introduced before 4.5 except the Makefile.in patch (the wrong files are being cleaned on make distclean), and I guess I either never submitted them to you or they got lost along the way.
http://people.debian.org/~ari/patches/logjam_4.5.1-2.diff

committed, thanks.

Patch for bug http://bugs.debian.org/328767:
http://people.debian.org/~ari/patches/logjam_4.5.1-2-3.diff

This patch breaks clearing the tags on an existing entry.
(That is why the existing code always sends the metadata: to clear it out.)

However, something like it would probably be a good solution.

hrm, then I don't have a good fix. Does the LJ server return a list of capabilities?

Unfortunately, I don't think it does.

I guess the fix would be to change LogJam's model, so that NULL means "don't send", and an empty string means "send, but clear". So the values would default to NULL, but if you remove one of the values on an old entry, you'd set it to "".

You'd have to be careful that turning on the tags thingy, typing some stuff in, and then closing it would not send the tags junk, while opening an old entry and closing the tags thingy would. Sounds like a lot of effort.

Yeah, I had thought of a couple of solutions along those lines, but they all seemed too hackish and like a lot of effort for nothing, especially if it would only be done for one field and wouldn't apply to any newer fields in the protocol. I'm amazed the LJ protocol has no way of querying for supported metadata.