On 2013-08-21, Volker Braun <[email protected]> wrote:
> Hmm doesn't work with slrn 1.0.1 but works with slrn pre1.0.2-9. I
> guess its a cutting-edge feature.
>
Thanks for pointng this out. The git version of slang needs a patch (see
below) on OSX, but otherwise it's all well (I can read these solid
blocks of base64=encoded text which I couldn't before) if I install the
git version of slang and then the git version of slrn. (and add
interpret "mime.sl" to ~/.slrnrc)
Dima
diff --git a/src/slstd.c b/src/slstd.c
index 4d5e2b7..820bc3c 100644
--- a/src/slstd.c
+++ b/src/slstd.c
@@ -1140,7 +1140,12 @@ static void clear_error_intrin (void)
}
#ifdef HAVE_ENVIRON
+#ifdef __APPLE__
+#include <crt_externs.h>
+#define environ (*_NSGetEnviron())
+#else
extern char **environ; /* POSIX and ??? */
+#endif
static void get_environment (void)
{
unsigned int num;
>
>
> On Wednesday, August 21, 2013 3:13:53 PM UTC+1, Simon King wrote:
>>
>> Hi Volker,
>>
>> On 2013-08-21, Volker Braun <[email protected] <javascript:>> wrote:
>> > Most messages in sage-devel are actually base64-encoded, and slrn
>> displays
>> > them fine. What slrn trips over is content/multipart. RFC1341 is only
>> from
>> > 1992, so its understandable that slrn hasn't caught up yet :-P
>> Actually,
>> > it does ship with support for it but its disabled by default for some
>> > mysterious reason. You need to add
>> >
>> > interpret "mime.sl"
>> >
>> > to your .slrnrc
>>
>> Doesn't work at all for me (slrn won't even start).
>>
>> Note that on some of the sage lists (don't recall which one) slrn asks
>> me if I want the posts to read it with a mime reader.
>>
>> Cheers,
>> Simon
>>
>>
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/groups/opt_out.
