On 2013-08-21, Volker Braun 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
On Wed, 21 Aug 2013 at 04:48PM +0200, Jeroen Demeyer wrote:
> Not everything is UTF-8, the relevant setting here is LC_CTYPE.
Setting LC_CTYPE to en_US.utf8 (and variants) didn't change anything.
Same for LC_ALL.
Dan
--
--- Dan Drake
- www.math.wisc.edu/~ddrake/
---
signature.asc
De
Dan, what worked for me was to make sure that the locale settings were
utf8 (and not reset to something else in a startup file such as
.bashrc) and then I had to log out and in again. It was not enough to
start a new gnome-terminal as it seemed to "remember".
John
On 21 August 2013 15:48, Jeroen
On 2013-08-21 16:43, Dan Drake wrote:
If I may go back to the regular terminal stuff...I am seeing the "weird"
banner even though I try to have everything set to UTF-8.
Not everything is UTF-8, the relevant setting here is LC_CTYPE.
--
You received this message because you are subscribed to the
Hi Volker,
On 2013-08-21, Volker Braun 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 wit
Hmm doesn't work with slrn 1.0.1 but works with slrn pre1.0.2-9. I guess
its a cutting-edge feature.
On Wednesday, August 21, 2013 3:13:53 PM UTC+1, Simon King wrote:
>
> Hi Volker,
>
> On 2013-08-21, Volker Braun > wrote:
> > Most messages in sage-devel are actually base64-encoded, and slrn
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
m
Hi Volker,
On 2013-08-21, Volker Braun wrote:
> --=_Part_9509_16842449.1377077319452
> Content-Type: text/plain; charset=ISO-8859-1
>
> Slnr decodes base64 in bodies by default since version 0.9.6.4. Which is at
> least 10 years old by now. Which version are you using?
I use this (on openSu
On 2013-08-21, Volker Braun wrote:
> --=_Part_9509_16842449.1377077319452
> Content-Type: text/plain; charset=ISO-8859-1
>
> Slnr decodes base64 in bodies by default since version 0.9.6.4. Which is at
> least 10 years old by now. Which version are you using?
pre1.0.0-26
I guess Simon, who ask
Slnr decodes base64 in bodies by default since version 0.9.6.4. Which is at
least 10 years old by now. Which version are you using?
On Wednesday, August 21, 2013 4:01:49 AM UTC+1, Dima Pasechnik wrote:
>
> > So, could you (or someone else) please tell me how to configure slrn so
> > that I can
On 2013-08-20, Simon King wrote:
> Dear William,
>
> I am reading the sage mailing lists with slrn. I can not properly read
> your post I am replying to. My original guess was that your post uses
> UTF-8, and I did not configure my slrn accordingly. But now, I have
> uncommented the line
> chars
On 20 August 2013 21:58, William Stein wrote:
>
> On Aug 20, 2013 12:12 PM, "Jason Grout" wrote:
>>
>> On 8/20/13 1:54 PM, John Cremona wrote:
>>>
>>> No doubt no-one is still reading this thread but I will post one more
>>> entry when am back in the office tomorrow.
>>
>>
>> I am :).
>>
>> I sur
On Aug 20, 2013 12:12 PM, "Jason Grout" wrote:
>
> On 8/20/13 1:54 PM, John Cremona wrote:
>>
>> No doubt no-one is still reading this thread but I will post one more
>> entry when am back in the office tomorrow.
>
>
> I am :).
>
> I sure hope this cosmetic change that is causing so much headache
On 8/20/13 1:54 PM, John Cremona wrote:
No doubt no-one is still reading this thread but I will post one more
entry when am back in the office tomorrow.
I am :).
I sure hope this cosmetic change that is causing so much headache
doesn't turn away many people. Personally, I don't think the cha
I think that this:
http://unix.stackexchange.com/questions/60551/utf-8-works-in-gnome-terminal-only-after-selecting-already-selected-encoding
might hold the answer. Certainly when I now log into my office
machine from home and then run gnome-terminal, all is well. I had a
non-utf8 locale setti
At least you see that you have a problem with UTF8 immediately and not only
after you send in patches with the wrong encoding
On Tuesday, August 20, 2013 5:53:37 PM UTC+1, Snark wrote:
>
> Le 20/08/2013 18:27, Dima Pasechnik a écrit :
> > And you people didn't believe me when I said that UTF
Le 20/08/2013 18:27, Dima Pasechnik a écrit :
> And you people didn't believe me when I said that UTF-8 banners are evil
> ;–)
I think they're more trouble than they're worth, which is a bit
different even if the conclusion is the same: "It's a bad idea!".
Snark on #sagemath
--
You received th
And you people didn't believe me when I said that UTF-8 banners are evil
;–)
On Tuesday, 20 August 2013 21:14:41 UTC+8, John Cremona wrote:
>
> 5.12 introduced a new encoding for the Sage header. I remember some
> discussion on this list of whether it was a good idea or not. I
> probably can
On 20 August 2013 17:01, Volker Braun wrote:
> Does it work if you start the terminal on your desktop with
>
> LANG=en_GB.UTF8 gnome-terminal
>
> (or whatever other UTF8 locale you have installed)
>
No. On my desktop, locale shows
LANG=en_GB.utf8
LC_CTYPE="en_GB.utf8"
LC_NUMERIC="en_GB.utf8"
L
Does it work if you start the terminal on your desktop with
LANG=en_GB.UTF8 gnome-terminal
(or whatever other UTF8 locale you have installed)
On Tuesday, August 20, 2013 3:04:19 PM UTC+1, John Cremona wrote:
>
> On 20 August 2013 14:58, Volker Braun >
> wrote:
> >
> >
> > On Tuesday, Augus
On 20 August 2013 14:58, Volker Braun wrote:
>
>
> On Tuesday, August 20, 2013 2:51:41 PM UTC+1, John Cremona wrote:
>>
>> It is GNOME Terminal 2.28.2. The banner looks fine on my laptop --
>> running ubuntu 12.04 -- but not when I log into a remote machine
>> (ubuntu 12.04) from my desktop .
>
>
On 08/20/2013 09:53 PM, John Cremona wrote:
On 20 August 2013 14:50, William Stein wrote:
On Aug 20, 2013 6:45 AM, "David Loeffler"
wrote:
Hi John,
Are you maybe using Sage inside a screen session? Apparently screen
doesn't play nicely with UTF-8 characters, unless you invoke it with
"scre
On 20 August 2013 14:55, William Stein wrote:
>
> On Aug 20, 2013 6:53 AM, "John Cremona" wrote:
>>
>> On 20 August 2013 14:50, William Stein wrote:
>> >
>> > On Aug 20, 2013 6:45 AM, "David Loeffler"
>> > wrote:
>> >>
>> >> Hi John,
>> >>
>> >> Are you maybe using Sage inside a screen session?
Dear William,
I am reading the sage mailing lists with slrn. I can not properly read
your post I am replying to. My original guess was that your post uses
UTF-8, and I did not configure my slrn accordingly. But now, I have
uncommented the line
charset display utf8
in ~/.slrnrc, and I still see y
On Tuesday, August 20, 2013 2:51:41 PM UTC+1, John Cremona wrote:
>
> It is GNOME Terminal 2.28.2. The banner looks fine on my laptop --
> running ubuntu 12.04 -- but not when I log into a remote machine
> (ubuntu 12.04) from my desktop .
>
What are you running on your desktop? The terminal
On Aug 20, 2013 6:53 AM, "John Cremona" wrote:
>
> On 20 August 2013 14:50, William Stein wrote:
> >
> > On Aug 20, 2013 6:45 AM, "David Loeffler"
> > wrote:
> >>
> >> Hi John,
> >>
> >> Are you maybe using Sage inside a screen session? Apparently screen
> >> doesn't play nicely with UTF-8 chara
On 20 August 2013 14:50, William Stein wrote:
>
> On Aug 20, 2013 6:45 AM, "David Loeffler"
> wrote:
>>
>> Hi John,
>>
>> Are you maybe using Sage inside a screen session? Apparently screen
>> doesn't play nicely with UTF-8 characters, unless you invoke it with
>> "screen -U".
>
> If so, time to
It is GNOME Terminal 2.28.2. The banner looks fine on my laptop --
running ubuntu 12.04 -- but not when I log into a remote machine
(ubuntu 12.04) from my desktop .
In the Terminal menu for the terminal under "Set character encoding"
it is set to UTF-8.
I'm not running inder screen (but thanks f
On Aug 20, 2013 6:45 AM, "David Loeffler"
wrote:
>
> Hi John,
>
> Are you maybe using Sage inside a screen session? Apparently screen
> doesn't play nicely with UTF-8 characters, unless you invoke it with
> "screen -U".
If so, time to switch to tmux!!!
>
> David
>
> On 20 August 2013 14:24, Volk
Hi John,
Are you maybe using Sage inside a screen session? Apparently screen
doesn't play nicely with UTF-8 characters, unless you invoke it with
"screen -U".
David
On 20 August 2013 14:24, Volker Braun wrote:
> You need a UTF-8 capable terminal (independently of Sage it would be a good
> time
You need a UTF-8 capable terminal (independently of Sage it would be a good
time to switch). See also screenshots at:
http://boxen.math.washington.edu/home/vbraun/UTF8/
On Tuesday, August 20, 2013 2:14:41 PM UTC+1, John Cremona wrote:
>
> 5.12 introduced a new encoding for the Sage header. I
31 matches
Mail list logo
