Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 102558 - muttng tree (thread, attachment) display is ascii only
Summary: muttng tree (thread, attachment) display is ascii only
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High trivial (vote)
Assignee: Aron Griffis (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-14 17:53 UTC by Jason King
Modified: 2005-08-17 14:09 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason King 2005-08-14 17:53:13 UTC
After upgrade from 20050325 to 20050809-r1 my thread and attachment trees are
ascii only, ie. they are using the '>' char and space indentation in the index
view to show threading depth.

Reproducible: Always
Steps to Reproduce:
1. Switch to threaded view of your index.
2. Look at the index thread character for the thread tree.
3. Or, look at the attachments view of an email with attachments.

Actual Results:  
I get plain ASCII '>' chars in my index thread tree view and attachments tree
view, despite a setting of ascii_chars of no.

Expected Results:  
To have pretty super-ascii chars showing thread tree, as it was in 20050325.
Comment 1 Aron Griffis (RETIRED) gentoo-dev 2005-08-15 06:18:24 UTC
Please post emerge info.  Non-ascii tree is working fine here
Comment 2 Jason King 2005-08-15 17:16:50 UTC
I fixed it, -slang!!  FYI, here was what I was about to send (before trying
-slang as a stab in the dark)...

While collecting info and so forth, I noticed that you'd put out a new one, so I
upgraded to that - same problem persists (which I'm sure is not surprising). 
I've triple checked my .muttngrc and re-confirmed that I don't have ascii_chars
set (which I don't).

Something else interesting is that during that check I set it manually from
within the muttng client, and the tree chars changed from plain '>'s to a
combination of '>', '-', '|' and '`' characters, so I had previously thought
that it was mistakenly reverting to ascii_chars being on somehow, but actually
it's not because setting ascii_chars changes the look entirely.

So, it's like a character set problem, which makes me wonder that maybe I needed
+cjk or something??  Anyway, I've included both the emerge -vp line below, and
the emerge info, anything you can think of would be great.


[ebuild   R   ] mail-client/muttng-20050814  +berkdb -buffysize -cjk +crypt
-debug +gdbm -gnutls +gpgme -idn -imap +mbox +nls -nntp +pop -qdbm -sasl +slang
-smime -smtp +ssl 0 kB 


Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130,
glibc-2.3.5-r0, 2.6.11-gentoo-r5 i686)
=================================================================
System uname: 2.6.11-gentoo-r5 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Gentoo Base System version 1.12.0_pre3
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -fforce-addr
-momit-leaf-frame-pointer -ftracer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config
/usr/share/config /usr/share/vim /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
CXXFLAGS="-O3 -march=pentium4 -fomit-frame-pointer -fforce-addr
-momit-leaf-frame-pointer -ftracer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://mirror.isp.net.au/pub/gentoo
ftp://mirror.aarnet.edu.au/pub/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X acpi aim alsa apache2 apm avi bash-completion berkdb bitmap-fonts
bzlib crypt cups curl curlwrappers dio eds emboss encode esd ethereal evo fam
fbcon foomaticdb freetds ftp gd gdbm gif gpgme gpm gstreamer gtk gtk+ gtk2 iconv
icq imagemagick imlib innodb ipv6 ithreads jabber java jpeg junit kdexdeltas
kerberos krb4 lcms ldap lesstif libg++ libwww mad mbox mcal mikmod mime mono
motif mozilla mp3 mpeg msn mssql mysql mysqli ncurses nls nptl offensive ofx ogg
oggvorbis openal opengl oscar oss pam pcntl pcre pdflib perl php png pop posix
ppds pthreads python qt quicktime readline samba sdl session shared sharedmem
simplexml slang slp sndfile sockets spell spl sse sse2 ssl svga symlink sysvipc
tcpd tetex threads tidy tiff truetype truetype-fonts type1-fonts unicode usb
userlocales vorbis wmf xml xml2 xmlrpc xpm xv yahoo zlib userland_GNU
kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
Comment 3 Jason King 2005-08-15 17:19:35 UTC
Anyway, yeah...

  USE=-slang emerge muttng

Fixed it right up.  I hadn't disabled it prior to that because with my setup
(aterms) muttng was still doing transparent background properly even with
+slang, so I didn't think about it.

So anyway, perhaps another 'hint' to add to the emerge output, to disable slang
if you have trouble with the non-ascii threading tree.  Thanks for your
comments, it forced me to look harder.
Comment 4 Aron Griffis (RETIRED) gentoo-dev 2005-08-17 14:09:18 UTC
ok, mutt-1.5.10 now ignores USE=slang, preferring to always use ncurses.  That
should fix this problem...