Re: mutt hanging on sending
On 12/01/2013 04:43 PM, LEVAI Daniel wrote: >> Traces that are useful include, well, eg. symbol names ;) You must >> compile mutt with debug symbols and not stripping it. Then, I think >> this should be reported on trac[1], where it will be probably >> ignored, like it would have been here :D Nonetheless, at least >> there would be a record of it :) Whoops! Hah, sorry, I'm learning a lot as I go on here. I didn't compile Mutt myself; it was in the Debian repos. But I've now installed mutt-dbg and the backtrace looks different now, although before it started I got this message: Starting program: /usr/bin/mutt -d2 warning: Could not load shared library symbols for linux-vdso.so.1. Do you need "set solib-search-path" or "set sysroot"? [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Debugging at level 2. I'll register with the Mutt Trac page next, but, at least for posterity's sake on this mailing list, here's what I got with the backtrace now; the crash was on sending an email. (gdb) backtrace #0 0x75d87f5d in __libc_recv (fd=8, buf=0xdd6950, n=5, flags=-1) at ../sysdeps/unix/sysv/linux/x86_64/recv.c:29 #1 0x76d92ccf in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26 #2 0x76d9359d in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26 #3 0x76d8ff34 in _gnutls_recv_int () from /usr/lib/x86_64-linux-gnu/libgnutls.so.26 #4 0x00493b94 in tls_socket_read (conn=, buf=0x7f0040 "* STATUS Drafts (MESSAGES 6)\r\na0052 OK Completed\r\nY 1178819290 UNSEEN 0)\r\na0042 OK Completed\r\n* STATUS Drafts (RECENT 0 UIDNEXT 6130 UIDVALIDITY 1178819290 UNSEEN 3)\r\na0043 OK Completed\r\n* STATUS \"Fol"..., len=1024) at ../mutt_ssl_gnutls.c:112 #5 0x00495dca in mutt_sasl_conn_read (conn=0x7efef0, buf=0x7f0040 "* STATUS Drafts (MESSAGES 6)\r\na0052 OK Completed\r\nY 1178819290 UNSEEN 0)\r\na0042 OK Completed\r\n* STATUS Drafts (RECENT 0 UIDNEXT 6130 UIDVALIDITY 1178819290 UNSEEN 3)\r\na0043 OK Completed\r\n* STATUS \"Fol"..., len=1024) at ../mutt_sasl.c:552 #6 0x004930d7 in mutt_socket_readchar (conn=conn@entry=0x7efef0, c=c@entry=0x7fff9fdf "") at ../mutt_socket.c:172 #7 0x00493218 in mutt_socket_readln_d (buf=0xabbdb0 "a0052 OK Completed", buflen=512, conn=0x7efef0, dbg=dbg@entry=2) at ../mutt_socket.c:202 #8 0x0049acc8 in imap_cmd_step (idata=idata@entry=0x7a9e90) at ../../imap/command.c:113 #9 0x004a1c30 in imap_append_message (ctx=ctx@entry=0x7fffafe0, msg=msg@entry=0xd8faf0) at ../../imap/message.c:677 #10 0x004475f4 in mx_commit_message (msg=0xd8faf0, ctx=ctx@entry=0x7fffafe0) at ../mx.c:1553 #11 0x0046a777 in mutt_write_fcc (path=path@entry=0x7fffb790 "imaps://u...@domain.com:passw...@server.net/Sent", hdr=0xd8f580, msgid=msgid@entry=0x0, post=post@entry=0, fcc=fcc@entry=0x0) at ../sendlib.c:2846 #12 0x004637a4 in ci_send_message (flags=, flags@entry=0, msg=0xd8f580, msg@entry=0x0, tempfile=tempfile@entry=0x0, ctx=, cur=cur@entry=0x0) at ../send.c:1738 #13 0x00422f1b in mutt_index_menu () at ../curs_main.c:1992 #14 0x00408869 in main (argc=1, argv=) at ../main.c:1026 And I apologize for dumb or incomplete questions; I got a lot of learning processes going on at the same time now with Linux, but thanks in advance for helping me up tot he next plateau. Best regards, Rick -- Rick Valenzuela Videojournalist Phnom Penh, Cambodia +855 92 470 702 r...@rickv.com :: www.rickv.com GnuPG ID: 0xD5644029 -- Rick Valenzuela Videojournalist Phnom Penh, Cambodia www.rickv.com GnuPG ID: 0xD5644029
Re: few questions
* On 01 Dec 2013, Dave Dodge wrote: > On Fri, Nov 29, 2013 at 11:10:11AM -0600, David Champion wrote: > > * On 29 Nov 2013, Martin Vegter wrote: > > > On 2013-11-29 12:40, LEVAI Daniel wrote: > > > >On p, nov 29, 2013 at 12:24:33 +0100, Martin Vegter wrote: > > > >>when in run mutt in terminal emulator, it reacts to the scroll wheel of > > > >>my > > > >>mouse. Is it possible to disable mouse entirely? There is no mention of > > > >>the > > > >>word "mouse" in man mutt. > > > > > > > >Well, not sure if this is Mutt specific, but terminal emulator specific. > > > >If you're on a tty, perhaps gpm is running? If you're on a pseudo > > > >terminal, just disable the mouse input in your terminal emulator (xterm, > > > >urxvt etc... see their corresponding manuals). > > > > > > I had similar problem with midnight commander and I solved it by using mc > > > --nomouse. So I was hoping for similar command line option for mutt. > > > > Midnight Commander has support for mouse input events, so they can be > > disabled. Mutt does not read mouse events. What you see is probably > > your terminal emulator's scrollback buffer (the scrollbar). > > If it's the same thing that happens to me, it's not the scrollback > buffer. Mutt actually reacts to the scroll wheel, intentionally or > not. Interesting - admittedly I don't use an X desktop. I just scanned mutt's source code for mouse, click, and button events. Maybe these events translate into something else at a lower layer of the window system? In any case I don't think mutt is specifically responding to the mouse; it's responding to a signal that a mouse generate for some unclear reason, but that could be generated in another way. -- David Champion • d...@bikeshed.us
w3m HTML displays
As I understand it, gnus uses w3m to display html messages if it's available.
I have my .mailcap file setup to use w3m to display html messages in mutt, but
they don't look like the same messages do in gnus. There's less use of color,
italics and bold and other text features. Also, column layouts in the html
appear in gnus but not in mutt.
Here's my .mailcap entry:
text/html; w3m -I %{charset} -dump %s -cols $COLUMNS; copiousoutput;
description=HTML Text; nametemplate=%s.html
text/*; more
Is there anything I can do to get mutt's w3m display to look more like that in
gnus?
Thanks!
-pd
Re: few questions
On Fri, Nov 29, 2013 at 11:10:11AM -0600, David Champion wrote: > * On 29 Nov 2013, Martin Vegter wrote: > > On 2013-11-29 12:40, LEVAI Daniel wrote: > > >On p, nov 29, 2013 at 12:24:33 +0100, Martin Vegter wrote: > > >>when in run mutt in terminal emulator, it reacts to the scroll wheel of my > > >>mouse. Is it possible to disable mouse entirely? There is no mention of > > >>the > > >>word "mouse" in man mutt. > > > > > >Well, not sure if this is Mutt specific, but terminal emulator specific. > > >If you're on a tty, perhaps gpm is running? If you're on a pseudo > > >terminal, just disable the mouse input in your terminal emulator (xterm, > > >urxvt etc... see their corresponding manuals). > > > > I had similar problem with midnight commander and I solved it by using mc > > --nomouse. So I was hoping for similar command line option for mutt. > > Midnight Commander has support for mouse input events, so they can be > disabled. Mutt does not read mouse events. What you see is probably > your terminal emulator's scrollback buffer (the scrollbar). If it's the same thing that happens to me, it's not the scrollback buffer. Mutt actually reacts to the scroll wheel, intentionally or not. For example I might be in the pager reading a long message and instinctively roll the the wheel a bit to try to scroll the text. Mutt responds by moving through 9 messages forward/backward for every wheel event, so at least 9 nearby messages flicker on the screen and also get marked read. Then I have to go back to the folder and figure out which ones I haven't seen yet and manually re-mark them "U". If I'm in the folder itself and use the mouse wheel, the position in the folder jumps 9 messages forward/backward in the list for each wheel event. That's not so bad; it's the pager reaction that causes problems. For example earlier today I was reading a message and went to copy/paste a URL with the mouse, and accidentally touched the wheel sending me several messages away and marking them all read along the way. If I use the wheel while composing a message in emacs in the same terminal window, it scrolls 9 lines forward/backward for each wheel event. I don't know if the 9 is significant or just a coincidence. Emacs does know that it's getting mouse events, for example C-h k reports that it's seeing "mouse-4" and "mouse-5" from the wheel. I've seen this sort of thing happen in both gnome-terminal and xfce4-terminal, both locally and over ssh. -Dave Dodge/dodo...@dododge.net
Re: mutt hanging on sending
On v, dec 01, 2013 at 12:17:24 +0700, Rick Valenzuela wrote: [...] > #1 0x76d92ccf in ?? () from > /usr/lib/x86_64-linux-gnu/libgnutls.so.26 > #2 0x76d9359d in ?? () from > /usr/lib/x86_64-linux-gnu/libgnutls.so.26 > #3 0x76d8ff34 in _gnutls_recv_int () from > /usr/lib/x86_64-linux-gnu/libgnutls.so.26 > #4 0x00493b94 in ?? () > #5 0x00495dca in ?? () > #6 0x004930d7 in ?? () > #7 0x00493218 in ?? () > #8 0x0049acc8 in ?? () > #9 0x004a1c30 in ?? () > #10 0x004475f4 in ?? () > #11 0x0046a777 in ?? () > #12 0x004637a4 in ?? () > #13 0x0044d305 in ?? () > #14 0x004163a7 in ?? () > #15 0x00423082 in ?? () > #16 0x00408869 in ?? () > #17 0x75cbf995 in __libc_start_main (main=0x407950, argc=2, > ubp_av=0x7fffe2a8, init=, fini=, > rtld_fini=, > stack_end=0x7fffe298) at libc-start.c:276 > #18 0x00408b97 in ?? () [...] Traces that are useful include, well, eg. symbol names ;) You must compile mutt with debug symbols and not stripping it. Then, I think this should be reported on trac[1], where it will be probably ignored, like it would have been here :D Nonetheless, at least there would be a record of it :) That being said, you could try compiling mutt with openssl instead of gnutls, and see if that solves your problem (it seems it hangs when gnutls is trying to read something). Daniel [1] http://dev.mutt.org/trac/ -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
