Re: Getting color on FreeBSD

[tech-lists]

On Thu, Aug 22, 2019 at 07:14:28PM -0500, Tim Chase wrote:

I'm a bit stuck trying to figure out why colors aren't working for me
on FreeBSD (where I understand that termcap is used rather than
terminfo).


How are you invoking mutt?

The only way I can get a mono mutt display is by invoking mutt with an empty
config file (as I have a .muttrc with color statements already):

touch .argaerg
mutt -F .argaerg

Have you tried copying the supplied sample.muttrc to $HOME/.muttrc and then
running mutt? It'll at least show you colour if $TERM is xterm-256color

If you installed mutt with pkg, colour will be enabled. Here's my mutt -v :

Mutt 1.12.1 (2019-06-15)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: FreeBSD 12.0-RELEASE-p10 (amd64)
ncurses: ncurses 5.9.20140222 (compiled with 5.9)
libiconv: 1.14
libidn2: 2.2.0 (compiled with 2.2.0)
hcache backend: Berkeley DB 5.3.28: (September  9, 2013)

Compiler:
FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM
6.0.1)
Target: x86_64-unknown-freebsd12.0
Thread model: posix
InstalledDir: /usr/bin

[...]

Compile options:
-DOMAIN
-DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  -USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  +USE_SMTP  
+USE_SSL_OPENSSL  -USE_SSL_GNUTLS  +USE_SASL  -USE_GSS  +HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  +HAVE_FUTIMENS  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  +CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  +LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_LIBIDN2  +HAVE_GETSID
+USE_HCACHE  
+USE_SIDEBAR  +USE_COMPRESSED  -USE_INOTIFY  
-ISPELL


--
J.


signature.asc
Description: PGP signature

Re: Getting color on FreeBSD

[Derek Schrock]

On Thu, Aug 22, 2019 at 08:14:28PM EDT, Tim Chase wrote:
> I'm a bit stuck trying to figure out why colors aren't working for me
> on FreeBSD (where I understand that termcap is used rather than
> terminfo).

According to the configure script it appears all you need for color is
start_color() from ncurses which should be there in the base system.

Can you provide 'mutt -v' output?  Does it have +HAVE_COLOR?

Are you building mutt from source or using ports/pkg? If so can you
provide the output off 'pkg info -f mutt' 

> So the terminal is doing color as expected, but somehow mutt/neomutt
> doesn't seem to recognize that.  Is there some trick that I've missed
> for getting mutt/neomutt to play well with termcap/FreeBSD?

I'm doing nothing special in ports/pkg or from source and colors just
works with macOS Terminal/iTerm2, or cygwin xterm.

Do you get color unknown command when you try to use 'color ...' in a
.muttrc?

Getting color on FreeBSD

[Tim Chase]

I'm a bit stuck trying to figure out why colors aren't working for me
on FreeBSD (where I understand that termcap is used rather than
terminfo).

Things should be set correctly:

  $ echo $TERM
  xterm
  $ tput Co pa
  8
  64

I've also tried setting $TERM to xterm-256color 

  $ echo $TERM
  xterm-256color
  $ tput Co pa
  256
  32767

Attempting to set the color in mutt with

  color status blue white

works as expected on my Linux boxes but does nothing on my FreeBSD
box.

Colors work fine in vim and weechat.  Likewise

  $ tput AF 4; echo hello ; tput me

works, as does

  $ printf '\e[31mHello\e[0m'

So the terminal is doing color as expected, but somehow mutt/neomutt
doesn't seem to recognize that.  Is there some trick that I've missed
for getting mutt/neomutt to play well with termcap/FreeBSD?

Thanks,

-tim