I've started getting ^@^@> in my xterms w/mutt
I recently updated my system (base OS and ports) that I read mail on using mutt (accessed via an xterm on a separate system) and am now seeing this sort of character string ^@^@> rather than the much more user friently characters I used to get. Anyone know what I can do to get back the more readable stuff? Is there some setting that I need to perform? Thanks, Bob -- Bob Willcox| If everything is coming your way, you're in the b...@immure.com | wrong lane. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: I've started getting ^@^@> in my xterms w/mutt
Hi! > I recently updated my system (base OS and ports) that I read mail on using > mutt (accessed via an xterm on a separate system) and am now seeing this sort > of character string ^@^@> rather than the much more user friently characters I > used to get. > > Anyone know what I can do to get back the more readable stuff? Is there some > setting that I need to perform? I had the same problem. Since then I use the SLANG option instead of NCURSES to build mutt. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208659 -- p...@opsec.eu+49 171 3101372 2 years to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: I've started getting ^@^@> in my xterms w/mutt
On Wed, 3 Jan 2018, Kurt Jaeger wrote: I had the same problem. Since then I use the SLANG option instead of NCURSES to build mutt. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208659 Hmmm... I wonder if that's related to something I found in Alpine 2.21? After upgrading from 2.20, I found that UTF-8 characters were displaying as "??" despite having "display-character-set=UTF-8" set. I asked the maintainer on record some months ago, with no response. I fixed it by adding "LANG=en_US.UTF-8" to the environment. Funny; it worked all the way up to 2.20 without it... Oh, and still no response from "mb...@xs4all.nl"; is he/she/it still alive? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: I've started getting ^@^@> in my xterms w/mutt
On Wed, Jan 03, 2018 at 08:45:48AM -0800, David Wolfskill wrote: > On Wed, Jan 03, 2018 at 10:19:09AM -0600, Bob Willcox wrote: > > ... > > Hi David, > > > > Thanks for your responses, but by setting the environment variables that you > > are using I'm still not getting the special chars I used to get (something > > that looks like a modified capital 'L' and a long dash (I think). > > IIRC, that one is a Polish character -- as in the first letter of > "??ukasiewicz" (the surname of the guy credited for "Polish notation"). > > One other -- possibly relevant -- thing I've noted is that with my > default xterm font (6x10), I do *not* get Chinese & Arabic characters, > but if I change the xterm (Ctl+Right button) to a larger font, they > show up OK. > > > Strangely, this behavior began suddenly on the several of my systems that I > > access mutt via an xterm at the same time. Two of them I had updated > > recently > > but the third hasn't been updated since October. > > > Hmm.. How independent are these systems from one another? In > particular, do you arrange to either share or sync your home directory > among them? > > > Thanks, > > Bob > > . > > I hope this helps > > Peace, > david > -- > David H. Wolfskillda...@catwhisker.org > If you want the best Fake News, go to the best source of it: Donald J. Trump. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. I just tried some changes to my .muttrc file and by adding this setting: set ascii_chars # use ASCII instead of ACS chars for threads I now get these characters displayed for thread continuations for example from the frebsd-ports mail: 14640 O Jan 02 Roger Marquis ( 26) DEFAULT_VERSIONS conflicts 14641 O Jan 02 Adam Weinberger ( 38) `-> 14642 O Jan 02 Roger Marquis ( 19) `-> 14643 Os Jan 03 Mathieu Arnold ( 70) `-> Which isn't as good as what I was previously getting, but better than the ^@ ones before that looked like this: 14640 O Jan 02 Roger Marquis ( 26) DEFAULT_VERSIONS conflicts 14641 O Jan 02 Adam Weinberger ( 38) ^@^@> 642 O Jan 02 Roger Marquis ( 19) ^@^@> 643 Os Jan 03 Mathieu Arnold ( 70) ^@^@> I still have no idea what changed to cause this...sigh... Thanks, Bob -- Bob Willcox| If everything is coming your way, you're in the b...@immure.com | wrong lane. Austin, TX | ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
