On Wed, Jul 27, 2005 at 10:24:23AM -0300, Fernando Canizo wrote: > Cool, so i can discard that the problem comes from vim + libncurses. > > In other mails from the thread we've reached to the point of knowing > that mutt is reencoding the chars. Since you seem to know about > libraries and calls to functions, do you know a method to track this > issue? I've been thinking maybe an strace to mutt, but y don't know > what to search for, and strace gives lots of info.
strace gives lots of information, but sometimes you can reduce it by looking only at specific calls. Usually what I'm interested in from strace in this type of problem is the exec's and open's it shows. I'm not sure what mutt's doing either. But if it's recoding the information, it's doing either via runtime library or via an external program. Another tool is ltrace, which would (like strace, a lot of information) show the library calls mutt makes. That's useful in this sense to see if it's doing something with iconv. > So the question is: what would you do to track this problem? I'd probably poke at the strace and ltrace results enough to get a sense of generally what it's doing, then grep through mutt's sources to see where it's doing _that_. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net
pgpXjfZNjKztF.pgp
Description: PGP signature
