Re: few questions
On Mon, Dec 02, 2013 at 11:35:51AM +0100, Andre Klärner wrote: > Gnome-terminal than disables its scroll back and reports mouse > scroll events as repeated presses of the up or down key. That definitely explains the behavior, thanks. > Your fix would involve just setting pager_stop in mutt, so that upon > reaching a messages end you won't touch other messages. pager_stop isn't enough, because in the pager and jump directly to the previous/next unread message. Now that I know what is being sent to mutt, if I also change some pager bindings it solves the problem and makes the wheel actually scroll the text: set pager_stop=yes bind pager next-line bind pager previous-line -Dave Dodge/dodo...@dododge.net
Re: few questions
Hi Dave, Actually mutt is just partly involved. It switches to the alternative screen in your terminal emulator. This switches in some terminals the behaviour. Gnome-terminal than disables its scroll back and reports mouse scroll events as repeated presses of the up or down key. The 9 lines/messages you experience come from the X11 wide setting for the mouse - the typical scroll distance. This alternates for example in mc. Mc uses the mouse reporting like aptitude also does, and if you disable it via the command line switch it chooses to ignore the received events. Your fix would involve just setting pager_stop in mutt, so that upon reaching a messages end you won't touch other messages. Alteratively you can disable (or remove from the coding) the switch of the mouse behaviour in your terminal emulator, but this might be a huge effort. I for myself decided a while ago to ditch the scroll back of my terminal (urxvt) and only use the one from the screen sessions I have running inside it anyway. This allows me to use the scroll wheel of my mouse nearly always as replacement for repeated long-distance scrolling in any app and doesn't bother me as much as the scroll back getting mixed up by the many screen windows I have open in each screen window. Regards, Andre Dave Dodge wrote: > >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 -- Andre Klärner Telefon: 0351/79666546 Fax: 0351/79688547 Mobil: 0172/9838653 Anschrift: Prohliser Allee 43 01239 Dresden
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
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: few questions
* Martin Vegter [11-29-13 15:27]: > On 2013-11-29 14:35, LEVAI Daniel wrote: > >On p, nov 29, 2013 at 14:07:18 +0100, Martin Vegter wrote: [...] > >>>This is how it works. You must sync the mailbox to purge the messages > >>>that were being marked for deletion. You can append the > >>> function to the macro (but then 'S' will of course > >>>purge any other messages marked for delete and all-in-all do > >>>everything that eg. '$' would have done). > >>I have modified my macro, but seems to make no > >>difference. I still see the message in inbox as marked deleted. > >> > >>macro index,pager S > >>"=archive" > > > >Oh, right. You must set delete=yes, if you want to > >actually purge the deleted mails. I forgot about this. > > > >muttrc(5): > >delete > > Type: quadoption > > Default: ask-yes > > > > Controls whether or not messages are really deleted when closing or > > synchronizing a mail‐ box. If set to yes, messages marked for > > deleting will automatically be purged without prompting. If set to > > no, messages marked for deletion will be kept in the mailbox. > > > > > >So eg.: > >macro index,pager S \ > > "=archive:set > > delete=yes:set delete=no" > > unfortunately, this still does not work: > 1) the messages-to-be-deleted are still in my inbox > 2) the at the end actually acts , so when I pres S, > I end up in the pager. A little trimming is in order or your posts really become somewhat confusing, and it is good netiquette. Some spacing might also be an improvement. Perhaps you should analyze a little of what you have done. You included in your macro "set delete=no", and have not read the resulting action according to the quoted doc, and that was not what the OP instructed. If I have read correctly -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535@ http://linuxcounter.net
Re: few questions
On 2013-11-29 14:35, LEVAI Daniel wrote: On p, nov 29, 2013 at 14:07:18 +0100, 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: hello, could somebody please advise on the following issues? 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. Not that I know of, but maybe someone more versed in Mutt can bring hope :) [...] This is how it works. You must sync the mailbox to purge the messages that were being marked for deletion. You can append the function to the macro (but then 'S' will of course purge any other messages marked for delete and all-in-all do everything that eg. '$' would have done). I have modified my macro, but seems to make no difference. I still see the message in inbox as marked deleted. macro index,pager S "=archive" Oh, right. You must set delete=yes, if you want to actually purge the deleted mails. I forgot about this. muttrc(5): delete Type: quadoption Default: ask-yes Controls whether or not messages are really deleted when closing or synchronizing a mail‐ box. If set to yes, messages marked for deleting will automatically be purged without prompting. If set to no, messages marked for deletion will be kept in the mailbox. So eg.: macro index,pager S \ "=archive:set delete=yes:set delete=no" unfortunately, this still does not work: 1) the messages-to-be-deleted are still in my inbox 2) the at the end actually acts , so when I pres S, I end up in the pager. ... that is 'no' at the end, or whatever value you've set for option 'delete' beforehand. And a fair warning to this macro: You would actually have to use two commands after '=archive', if it would ask you if you want to append the message to the =archive folder. If you have a setup not to ask you this, then one is sufficient. After one or two tries it'll work like a charm ;-) Daniel
Re: few questions
* 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: > >>hello, > >> > >>could somebody please advise on the following issues? > >> > >>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). Mutt has no influence on this -- you need to disable it in your term emulator. -- David Champion • d...@bikeshed.us
Re: few questions
On p, nov 29, 2013 at 14:07:18 +0100, 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: > >>hello, > >> > >>could somebody please advise on the following issues? > >> > >>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. Not that I know of, but maybe someone more versed in Mutt can bring hope :) [...] > >This is how it works. You must sync the mailbox to purge the messages > >that were being marked for deletion. You can append the > >function to the macro (but then 'S' will of course purge any other > >messages marked for delete and all-in-all do everything that eg. '$' > >would have done). > I have modified my macro, but seems to make no difference. I > still see the message in inbox as marked deleted. > > macro index,pager S "=archive" Oh, right. You must set delete=yes, if you want to actually purge the deleted mails. I forgot about this. muttrc(5): delete Type: quadoption Default: ask-yes Controls whether or not messages are really deleted when closing or synchronizing a mail‐ box. If set to yes, messages marked for deleting will automatically be purged without prompting. If set to no, messages marked for deletion will be kept in the mailbox. So eg.: macro index,pager S \ "=archive:set delete=yes:set delete=no" ... that is 'no' at the end, or whatever value you've set for option 'delete' beforehand. And a fair warning to this macro: You would actually have to use two commands after '=archive', if it would ask you if you want to append the message to the =archive folder. If you have a setup not to ask you this, then one is sufficient. After one or two tries it'll work like a charm ;-) Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
Re: few questions
On 2013-11-29 12:40, LEVAI Daniel wrote: On p, nov 29, 2013 at 12:24:33 +0100, Martin Vegter wrote: hello, could somebody please advise on the following issues? 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. What is the correct way to cancel an operation? For example, when I press 'm' in index by mistake, how do I exit from the 'new mail operation'. When I pres 'CTRL+c' mutt asks 'Exit mutt?' (with default yes), so I have to press n all the time. Is there no better way to undo a wrong key press? To cancel a question or anything that had put you into the Mutt command input, just press CTRL+g. Not sure what you mean by the new mail operation, but you can back out from the composer by exiting your editor, and exiting from the 'compose' screen (answering no to "postpone this message", if you wish). On any screen, just use the question mark to invoke the online key bingind help to figure out how to exit. I have a macro to move message to my archive folder: macro index,pager S "=archive" "move messages" it works, but there are two small problems: 1) It operates only on one (the current) message, not on all tagged messages. There is a generic binding: ; tag-prefix apply next function to tagged messages Pressing ';' before 'S' would execute 'S' on every tagged message. btw, this works with any function, of course. 2) it actually does not move the message immediately. It copies it to archive and tags it as deleted in the inbox. Is there a way to execute the "move" immediately (without having them in inbox selected as deleted)? This is how it works. You must sync the mailbox to purge the messages that were being marked for deletion. You can append the function to the macro (but then 'S' will of course purge any other messages marked for delete and all-in-all do everything that eg. '$' would have done). I have modified my macro, but seems to make no difference. I still see the message in inbox as marked deleted. macro index,pager S "=archive" thanks, Martin No problem, hope this helps; enjoy Mutt! :) Daniel
Re: few questions
On p, nov 29, 2013 at 12:24:33 +0100, Martin Vegter wrote: > hello, > > could somebody please advise on the following issues? > > 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). > What is the correct way to cancel an operation? For example, when I press > 'm' in index by mistake, how do I exit from the 'new mail operation'. When I > pres 'CTRL+c' mutt asks 'Exit mutt?' (with default yes), so I have to press > n all the time. Is there no better way to undo a wrong key press? To cancel a question or anything that had put you into the Mutt command input, just press CTRL+g. Not sure what you mean by the new mail operation, but you can back out from the composer by exiting your editor, and exiting from the 'compose' screen (answering no to "postpone this message", if you wish). On any screen, just use the question mark to invoke the online key bingind help to figure out how to exit. > I have a macro to move message to my archive folder: > macro index,pager S "=archive" "move messages" > it works, but there are two small problems: > 1) It operates only on one (the current) message, not on all tagged > messages. There is a generic binding: ; tag-prefix apply next function to tagged messages Pressing ';' before 'S' would execute 'S' on every tagged message. btw, this works with any function, of course. > 2) it actually does not move the message immediately. It copies it to > archive and tags it as deleted in the inbox. Is there a way to execute the > "move" immediately (without having them in inbox selected as deleted)? This is how it works. You must sync the mailbox to purge the messages that were being marked for deletion. You can append the function to the macro (but then 'S' will of course purge any other messages marked for delete and all-in-all do everything that eg. '$' would have done). > thanks, > Martin No problem, hope this helps; enjoy Mutt! :) Daniel -- LÉVAI Dániel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F
few questions
hello, could somebody please advise on the following issues? 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. What is the correct way to cancel an operation? For example, when I press 'm' in index by mistake, how do I exit from the 'new mail operation'. When I pres 'CTRL+c' mutt asks 'Exit mutt?' (with default yes), so I have to press n all the time. Is there no better way to undo a wrong key press? I have a macro to move message to my archive folder: macro index,pager S "=archive" "move messages" it works, but there are two small problems: 1) It operates only on one (the current) message, not on all tagged messages. 2) it actually does not move the message immediately. It copies it to archive and tags it as deleted in the inbox. Is there a way to execute the "move" immediately (without having them in inbox selected as deleted)? thanks, Martin
Re: Few questions about colors and regex
On Sat, Dec 01, 2012 at 11:50:48AM +0100, Rado Q wrote:
> > - does exist a non greedy version of * (0 or more) in mutt's regexp (In
> > vim is \{-})? I'd like to highlight *bla bla* but not *this*
>
> No, exclude '*' in greedy-relevant matches.
> See wiki - configlist - my wrapper script for HI_STAR.
Thanks, the link[*] to the pic is brocken.
[*] http://ghb-hamburg.de/rado/mutt/muttscr.gif
Re: Few questions about colors and regex
=- Marco Giusti wrote on Sat 1.Dec'12 at 11:34:45 +0100 -=
> - can I use `underline` with color? I think not, I tried but I
> failed but I also found on Internet some config files with this
> configuration;
Not yet, patches welcome.
> - does exist a non greedy version of * (0 or more) in mutt's regexp (In
> vim is \{-})? I'd like to highlight *bla bla* but not *this*
No, exclude '*' in greedy-relevant matches.
See wiki - configlist - my wrapper script for HI_STAR.
> - can I `highligh` only the header name and not the full header? i.e.:
> Subject: blablabla
Not yet, patches welcome.
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
Few questions about colors and regex
Hello, I have a few question about the use of color. Starting with the
simpler:
- can I use `underline` with color? I think not, I tried but I failed
but I also found on Internet some config files with this
configuration;
- does exist a non greedy version of * (0 or more) in mutt's regexp (In
vim is \{-})? I'd like to highlight *bla bla* but not *this*
^^^
this
should be not highlighted
This is what I have actually:
color body brightdefault default \
"(^| )\\*([-a-z0-9*]+\\*|[-a-z0-9*][-a-z0-9* ]*[-a-z0-9*]+)\\*[[:punct:]]?(
|$)"
- can I `highligh` only the header name and not the full header? i.e.:
Subject: blablabla
thanks
m.
Re: [newbie] a few questions
Leonardo Canducci ([EMAIL PROTECTED]) muttered: > I've just configured exim+procmail+fetchmail+mutt in my debian woody. > It works great but I still have a few questions I couldn't answer > reading howtos and docs. > > 1. attachments. is there some way in the index_format to show that a > message has an attachment? David Champion did a patch for this purpose. http://home.uchicago.edu/~dgc/mutt/#attach > 2. trash. I'd like to move messages marked with delete in my trash > mailbox instead of actually deleting them. how can I do that? You could use macros or Cedric Duval's thrashfolder patch. http://cedricduval.free.fr/mutt/ HTH, Michael -- I've run DOOM more in the last few days than I have the last few months. I just love debugging ;-) (Linus Torvalds) PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
[newbie] a few questions
I've just configured exim+procmail+fetchmail+mutt in my debian woody. It works great but I still have a few questions I couldn't answer reading howtos and docs. 1. attachments. is there some way in the index_format to show that a message has an attachment? 2. trash. I'd like to move messages marked with delete in my trash mailbox instead of actually deleting them. how can I do that? 3. mailboxes with old messages still marked new (I'm using unset mark_old) doesn't have the N flag. That's right if mutt checks mailboxes last-change-date, but I'd like these mailboxes to have the N flag since the contain unread messages. Is there some way to do that? thanks in advance! -- Leonardo Canducci, [EMAIL PROTECTED] on 13/09/2002
Re: A few questions
Hi, * John Iverson [02-07-10 23:48:07 +0200] wrote: > You might want to replace the "N" above with > "N", so it turns off the N flags instead of > toggling, thus making it work in the (probably rare) case > where it's run in a folder with no (N)ew messages. Hmm, in this case it only toggles the flag on the message the indicator is on. Anyway, thanks for the tip. bye, Rocco
Re: A few questions
* On Wed, 10 Jul 2002, Rocco Rutte wrote: > ,[ ~/.mutt/setup/macros ]- > | [...] > | ### remove ~N on all mail > | macro index ,n >"~NN~T" > "Remove ~N flag on all mail" > | [...] > `- You might want to replace the "N" above with "N", so it turns off the N flags instead of toggling, thus making it work in the (probably rare) case where it's run in a folder with no (N)ew messages. -- John
Re: A few questions
Hi, * jennyw [02-07-10 20:10:08 +0200] wrote: > 2. Is there a way to mark all messages as read for an >entire folder? Or marking all tagged messages as read? >I often do not sort by threads, and the only mark read >command I could find works only with threads. ,[ ~/.mutt/setup/macros ]- | [...] | ### remove ~N on all mail | macro index ,n |"~NN~T" | "Remove ~N flag on all mail" | [...] `- I have folder hooks which collapse all threads on entering; so this macro first of all un-collapses them, tags all messages with the ~N (New) flag, toggles it on all tagged ones, untags everything and collapses the threads again. Done. I know that the macro sequence could be much shorter, but hey, nobody gets younger as it's much more readable this way. ;-) bye, Rocco
Re: A few questions
* jennyw <[EMAIL PROTECTED]> wrote: > I have a few quick questions ... > > 1. Is there a way to add an address other than From: or Reply-To: to > aliases? For example, to: (common with mailin lists), cc:, or, when > there's a Reply-To:, From:? I did see the old message on saving the > message and then piping it to a script, but I was hoping there might be an > easier way ... You might want to take a look at the little brother's database at http://www.spinnaker.de/lbdb/. I use it and I'm very happy with it (but I gather data for my adressbook from some more datasources). > 3. Is there an IRC channel where mutt is discussed? #mutt on OPN (irc.openprojects.net), but 'discussed' is maybe not exactly the right word. It's more an idling contest there as far as I have seen :-). -- Lars 'darmok' Heiermann LANparty? => ['ju:nien] || http://www.junien.org
A few questions
I have a few quick questions ... 1. Is there a way to add an address other than From: or Reply-To: to aliases? For example, to: (common with mailin lists), cc:, or, when there's a Reply-To:, From:? I did see the old message on saving the message and then piping it to a script, but I was hoping there might be an easier way ... 2. Is there a way to mark all messages as read for an entire folder? Or marking all tagged messages as read? I often do not sort by threads, and the only mark read command I could find works only with threads. 3. Is there an IRC channel where mutt is discussed? Thanks! Jen
(at least) a few questions...
Why doesn't mutt use summary files like Netscape to reduce mbox load time? Is there a command to advance to the next unread message in any mailbox specified by the 'mailboxes' setting? When I send mail fcc-ed to one of the mailboxes in 'mailboxes', mutt reports new mail in that mailbox. Is there any way to avoid this? When I type ":set pgp_verify_sig no", mutt 1.2.4i says, "unknown variable", though this variable is listed in my manual.txt. mutt -v reports > Mutt 1.2.4i (2000-07-07) > Copyright (C) 1996-2000 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: Linux 2.2.5-15 [using slang 10202] > Compile options: > -DOMAIN > -DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK > -USE_IMAP -USE_GSS -USE_SSL -USE_POP +HAVE_REGCOMP -USE_GNU_REGEX > +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -ENABLE_NLS > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/spool/mail" > SHAREDIR="/usr/local/share/mutt" > SYSCONFDIR="/usr/local/etc" > ISPELL="/usr/bin/ispell" With PGP/MIME, is there any easy solution that allows people with PGP/MIME-capable mail clients to receive PGP/MIME and everybody else to receive traditional PGP messages? I'm thinking a procmail recipe that looks at incoming email and puts the sender's email address in /home/dan/.pgpmime-capable or /home/dan/.pgpmime-notcapable. If the email is PGP/MIME, the sender goes in .pgpmime-capable. If the email is PGP traditional, the sender goes in .pgpmime-notcapable . If the User-Agent or X-Mailer or From is one of those that deal really really horribly with PGP/MIME (Outlook (Express?), Hotmail, et al.), the sender goes in pgpmime-notcapable . Then, in .muttrc... sendhook . 'unset pgp_create_traditional' # If we don't know, send them PGP/MIME to encourage them to # use PGP/MIME. source "sed -e \"s/^\\(.*\\)$/send-hook '~t \1' 'set pgp_create_traditional'/\" < /home/dan/.pgpmime-notcapable" source "sed -e \"s/^\\(.*\\)$/send-hook '~t \1' 'unset pgp_create_traditional'/\" < /home/dan/.pgpmime-capable" # (The escaping of shell commands in .muttrc is miserable, btw). Is there any better solution? Are there any other clients that deal horribly with PGP/MIME? BTW, how do you verify PGP/MIME signatures with PGP 6 for Windows? -- Daniel J. Peng /"\ \ / ASCII Ribbon Campaign Who is John Galt?X Against Outlook & HTML Mail / \ http://www.thebackrow.net/ Q: How many surrealists does it take to change a light bulb? A: Two, one to hold the giraffe, and the other to fill the bathtub with brightly colored machine tools. [Surrealist jokes just aren't my cup of fur. Ed.]
Re: few questions...
On Sun, Sep 10, 2000 at 06:44:33AM -0500, Jeremy M. Dolan wrote: > For the following, I am running rxvt with a transparent background. > $TERM is set to rxvt, which is a proper entry in both the termcap and > terminfo databases. > > Problem 1: when I start mutt... the message list screen has a black > background. I don't have the slightest clue what causes this (its not are you using 'default' for the background color? -- Thomas E. Dickey <[EMAIL PROTECTED]> http://dickey.his.com ftp://dickey.his.com
few questions...
For the following, I am running rxvt with a transparent background. $TERM is set to rxvt, which is a proper entry in both the termcap and terminfo databases. Problem 1: when I start mutt... the message list screen has a black background. I don't have the slightest clue what causes this (its not just being in the alternate screen buffer, since Vim and other ncurses programs dont behave this way). If I set my $TERM to 'xterm', then the background isn't set to all black when mutt starts up. Problem 2: in the pager, there is a default binding of '' to 'previous-line'... by backspace and delete are most definatly set up correct, and matching my terminfo entry. Nothing else has a problem with it. But mutt seems to be assuming backspace = ^H, instead of asking terminfo. Problem 3: i have pgp_autosign set up, and a pgp_sign_as key id specified, but mutt seems to choose the 'wrong' MIC algorithm. (ie, if i pick my key from mutts menu, it will properly set the mic to pgp-sha1... but when just using pgp_sign_as, it sets the algo to pgp-md5). I assume this is because it doesn't even query pgp/gpg for info on what type of key pgp_key_id is. if this is the case, the manual should have a note under pgp_sign_as that you should also set your mic algo. otherwise, this is unexpected behaviour. Thanks in advance for any help! /jmd -- Jeremy M. Dolan <[EMAIL PROTECTED]> OpenPGP key = http://turbogeek.org/openpgp-key OpenPGP fingerprint = 494C 7A6E 19FB 026A 1F52 E0D5 5C5D 6228 DC43 3DEE
Re: a few questions
On Sun, Jan 30, 2000 at 10:50:34PM +0200, Marius Gedminas wrote: > I've just installed Mandrake 7.0 and noticed that mutt is linked with > slang there. Perhaps you should try recompiling mutt with slang? That did the trick, thanks a lot. Perhaps if I would take the time to figure out what slang, ncurses, and all of the other mysterious libraries actually _are_, I could answer these questions myself... :-) -- GPG Public Key: http://joshua.haberman.com/files/pubkey.pgp
Re: a few questions
Joshua Haberman [[EMAIL PROTECTED]] wrote: > On Sun, Jan 30, 2000 at 08:14:35PM +0200, Mikko Hänninen wrote: > > Can't help you with the Mandrake question, sorry -- I don't use RPMs. > > :-) > > I'm fairly certain it's _not_ a Mandrake question, I just included that > as backgroud information. > > I guess the gist of my first question is this: I upgraded from 0.85 or > so (I wish I could remember the exact version) to 1.0.1i and the colors > no longer work. I made no other changes to the system configuration in > the mean time (same terminal program, same .muttrc, etc...) It linked > with ncurses during the make, so I can't figure out why the colors don't > work. Verify that your $TERM supports colors. It's possible the mandrake installed version would have been calling a wrapper to deal with this. And as someone else pointed out, you may have more luck with S-lang, or you may not. If you do have better luck with S-lang one of the termcap/info experts can probably tell you what the problem was. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "If Microsoft can change and compete on quality, I've won." -- L. Torvalds
Re: a few questions
Mikko Hänninen <[EMAIL PROTECTED]>: > > 2. I found the documentation concerning mailboxes/folders (are they > > the same thing?) confusing. > > Generally, the terms "mailbox" and "(mail) folder" are used > interchangeably. Sometimes I've seen mailbox to refer to "your > incoming mailbox", leaving "mail folders" to be specifically > everything else but the incoming mailbox/folder. However I think > that the Mutt manual just uses the two words interchangeably. I suggested to Thomas that the documentation should perhaps be more consistent and use just one of the terms. I would guess "mailbox", as that's the term used in the RFCs. Edmund
Re: a few questions
On Sun, Jan 30, 2000 at 11:37:43AM -0800, Joshua Haberman wrote: > I guess the gist of my first question is this: I upgraded from 0.85 or > so (I wish I could remember the exact version) to 1.0.1i and the colors > no longer work. I made no other changes to the system configuration in > the mean time (same terminal program, same .muttrc, etc...) It linked > with ncurses during the make, so I can't figure out why the colors don't > work. What version of ncurses do you use? I had problems with pre-4.0 versions of ncurses; 4.2 and currently 5.0 seem to work fine (except for one little problem which I'm now trying to solve in ncurses mailing list). I've just installed Mandrake 7.0 and noticed that mutt is linked with slang there. Perhaps you should try recompiling mutt with slang? Note, that if you use stock version of slang, Alt+ will not work. See patch.slang-1.2.2.keypad.1 in contrib/ directory. (Mandrake comes with slang 1.3.8 and this problem is not yet fixed! Do slang maintainers know about this?) [... snip ...] > Just out of curiosity, do you generally have mail from different mailing > lists filtered into different folders? It seems like it'd be much easier > to manage that way... It seems most of people prefer it that way. Personally I use a couple of mutt macros that give me "virtual folders" by using the (l)imit command. So I can see all my incoming mail in one place (when there are just a couple of messages) or just hit ... and look at messages from different mailing lists ( is "no limits", is for personal messages). Sometimes I whish mutt would accept limit patterns which have no matching messages... After all, if you delete all visible messages and hit $, your limit patter does not magically go away. Also, sometimes I wish there were a command for inverting currently active pattern... Marius Gedminas -- Iki, If you are good, you will be assigned all the work. If you are real good, you will get out of it.
Re: a few questions
Joshua Haberman <[EMAIL PROTECTED]> wrote on Sun, 30 Jan 2000: > I guess the gist of my first question is this: I upgraded from 0.85 or > so (I wish I could remember the exact version) to 1.0.1i and the colors > no longer work. I don't think there's (m)any colour related changes in Mutt between those versions, but I don't actually know. Additionally, the only colouring I use is having "urgent" or "important" messages displayed in reverse. So someone else who is more knowledgeable than me needs to help you here. :-) > > I don't know what you mean with "edit folders". > > What if I wanted to change the name of a folder? Or change it from mbox > to another format? Or merge all of the contents of two folders into a > third folder? This is the kind of thing I meant... Changing the folder name can be done from shell (OS level). Mutt doesn't really support renaming a folder; the nearest you can do is select all messages from folder A and save (move) them to folder B. Depending on the $save_empty variable, empty folders get removed (I'm not sure if Maildirs ever get removed, even if $save_empty is unset). A similar procedure is needed also for folder type change (with suitable changing of the $mbox_type variable), or merging folders... Just learn to use the T(ag-pattern) command and then the ; (tag-prefix) followed by s(ave). These kind of operations get rather easy after that. For folder renaming, I'd just do it on the OS level. > Also, why does mutt insist on putting an equal sign at the beginning of > the names of mailboxes? It sucks to have to type in every time... The = is a shortcut of the $folder directory. Eg. if $folder is ~/Mail, then a mail folder called ~/Mail/mutt would be represented as =mutt . If it's any easier, you can use + instead of = everywhere. For folder operations, specifying a folder without = or + means that it's a path relative to the directory where Mutt started in (the current directory). So if your $folder is ~/Mail, and you started Mutt while being in that dir, then "=mutt" and "mutt" will refer to the same folder. Using = means the folder name is unambiguous, eg. "=mutt", whereas "mutt" will be relative to the current dir. > Just out of curiosity, do you generally have mail from different mailing > lists filtered into different folders? It seems like it'd be much easier > to manage that way... I do, and I know many others do. It depends on your tastes though. If you do, you may find that changing the %L reference in the default value of $index_format to a %F will give a nicer display. (Another FAQ there...) :-) > Thanks for all your help. I never thought I could like a terminal based > reader, but mutt's really starting to grow on me... :-) I'm glad to hear that. Mutt seems to have that effect on people. ;-) Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Happiness is always just a remembrance away.
Re: a few questions
On Sun, Jan 30, 2000 at 08:14:35PM +0200, Mikko Hänninen wrote: > Can't help you with the Mandrake question, sorry -- I don't use RPMs. > :-) I'm fairly certain it's _not_ a Mandrake question, I just included that as backgroud information. I guess the gist of my first question is this: I upgraded from 0.85 or so (I wish I could remember the exact version) to 1.0.1i and the colors no longer work. I made no other changes to the system configuration in the mean time (same terminal program, same .muttrc, etc...) It linked with ncurses during the make, so I can't figure out why the colors don't work. > I don't know what you mean with "edit folders". What if I wanted to change the name of a folder? Or change it from mbox to another format? Or merge all of the contents of two folders into a third folder? This is the kind of thing I meant... Also, why does mutt insist on putting an equal sign at the beginning of the names of mailboxes? It sucks to have to type in every time... > lists [EMAIL PROTECTED] [EMAIL PROTECTED] > > ... lets Mutt know that the two Mutt list addresses are mailing lists. > This is useful so that when you're reading mailing list messages, you > can press just use the L(ist-reply) command to send a reply that will > go to the mailing list. Specifying lists also means that a correct > Mail-Followup-To header gets generated for list emails. Cool, that works well. Just out of curiosity, do you generally have mail from different mailing lists filtered into different folders? It seems like it'd be much easier to manage that way... Thanks for all your help. I never thought I could like a terminal based reader, but mutt's really starting to grow on me... :-) Joshua -- GPG Public Key: http://joshua.haberman.com/files/pubkey.pgp
Re: a few questions
Joshua Haberman <[EMAIL PROTECTED]> wrote on Sun, 30 Jan 2000: > A few quick questions I hope someone can answer: Can't help you with the Mandrake question, sorry -- I don't use RPMs. :-) > 2. I found the documentation concerning mailboxes/folders (are they > the same thing?) confusing. Generally, the terms "mailbox" and "(mail) folder" are used interchangeably. Sometimes I've seen mailbox to refer to "your incoming mailbox", leaving "mail folders" to be specifically everything else but the incoming mailbox/folder. However I think that the Mutt manual just uses the two words interchangeably. > Does mutt filter mail into different > mailboxes, or is that procmail's job? Mutt doesn't filter mail; though you can make it do that with clever keyboard macros and hooks and such, generally it's suggested that you use a proper mail filtering too such as procmail to do that. > How do I create/edit different > mailboxes? Mutt will create mail folders for you, if you try to save/write an email to folder that doesn't exist. The $confirmcreate variable controls whether you get prompted for confirmation to create the folder or not. The default is set (confirm with a prompt). The type (mbox, MH, MMDF, Maildir) for the new mail folder depends on the $mbox_type setting. Default is mbox, the standard unix mail folder file. I don't know what you mean with "edit folders". You can change to a folder with the c(hange-folder) command, then browse the contents and delete any messages you like, or reply to them or whatever. You can also edit individual messages with the e(dit-message) function. > What exactly does the "list" directive do? First, it's "lists", not "list". It specifies a mailing list or lists, so Mutt knows that the particularly address is a mailing list. For example, lists [EMAIL PROTECTED] [EMAIL PROTECTED] ... lets Mutt know that the two Mutt list addresses are mailing lists. This is useful so that when you're reading mailing list messages, you can press just use the L(ist-reply) command to send a reply that will go to the mailing list. Specifying lists also means that a correct Mail-Followup-To header gets generated for list emails. If you're using Mutt 1.0, specifying a list with the lists command means that it's a subscribed mailing list. For the developement version (1.1.x), the behaviour is slightly different, there are separate "lists" and "subscribe" commands. "lists" specifies an unsubscribed list, "subscribe" a list to which you are subscribed. (As I've understood it, this distinction is necessary for setting up the MFT header correctly for unsubscribed lists as well.) Hope this helps, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / "If you're not impossible to tolerate, you're not trying hard enough."
a few questions
A few quick questions I hope someone can answer: 1. My installation of Mandrake 6.0 came with mutt installed as an RPM. I recently removed the RPM and upgraded to the last version, (with a tarball) and all of the sudden my colors don't work (it's all white.) My .muttrc wasn't changed at all, all the color setup is still there. 2. I found the documentation concerning mailboxes/folders (are they the same thing?) confusing. Does mutt filter mail into different mailboxes, or is that procmail's job? How do I create/edit different mailboxes? What exactly does the "list" directive do? Thanks, Joshua Haberman -- GPG Public Key: http://joshua.haberman.com/files/pubkey.pgp
