Re: viewing URLs (muttils or lynx?)
On Mon, Feb 18 2008, Christian Ebert wrote: > >> I only know how this would work with w3m. > > > > Could you tell me how? > > See Gary's message. Thanks to you and Gary. Indeed, w3m seems to be better that I thought in the beginning. But I'm a bit difficult (I've been using pine for about 10 years): - it would be nice, if MARK_URL was called automatically at start-up - "keymap RET EXTERN_LINK" does not work, I have to use another key (RETURN and ENTER do not work neither) - it's not the built-in pager, so I cannot take advantage of all the mutt features But shouldn't it be easy to implement, since the built-in pager can already highlight URLs? Cheers, Peter -- http://pmrb.free.fr/contact/
hooks from aliases
Hello, For my personal needs I've written a script to generate hooks from aliases: Input: alias a1 [EMAIL PROTECTED] (Name) alias a2 [EMAIL PROTECTED] (Name) alias a3 [EMAIL PROTECTED] (Name) alias a3 [EMAIL PROTECTED] (Name) alias a1a2 a1,a2 alias a4 [EMAIL PROTECTED] \ (Name) alias -group mygroup a5 [EMAIL PROTECTED] (Name) alias -group mylists list1 [EMAIL PROTECTED] (Name) alias -group mylists list2 [EMAIL PROTECTED] (Name) Output: fcc-hook '~C [EMAIL PROTECTED] ~C [EMAIL PROTECTED]' +a1a2 save-hook '~L [EMAIL PROTECTED] ~L [EMAIL PROTECTED]' +a1a2 fcc-save-hook [EMAIL PROTECTED] +a1 fcc-save-hook [EMAIL PROTECTED] +a2 fcc-save-hook [EMAIL PROTECTED] +a3 fcc-save-hook [EMAIL PROTECTED] +a3 fcc-save-hook [EMAIL PROTECTED] +a4 fcc-save-hook [EMAIL PROTECTED] +a5 set my_list_folders = /list1$|/list2$ mailboxes =list1 =list2 subscribe [EMAIL PROTECTED] [EMAIL PROTECTED] Usage: source "alias-hooks.php $alias_file|" folder-hook . 'special settings' folder-hook $my_list_folders 'other special settings' Perhaps it can be useful for other users. You can download it here: http://pmrb.free.fr/tmp/alias-hooks.txt Cheers, Peter -- http://pmrb.free.fr/contact/
folder browser, check-new and all that
Hi all In connection to my earlier postings, I did some more testing and I'm pretty sure that I tracked down a kind of pathological test case to reproduce the issue. I also found that the source of the problem I'm seeing is actually connected to my first post about the check-new function. Here is what I did. Set up two mailboxes foo/, bar/. Enter foo/ and leave back to the browser (important). While having mutt open *and* being in the browser, send mail to the two boxes. Just for the record, I did echo lala | mail -s to_foo @ echo lala | mail -s to_bar @ and in my .procmailrc as first entries :0 * ^Subject:.*to_foo.* foo/ :0 * ^Subject:.*to_bar.* bar/ Now, invoke check-new (in my case hit `n': 'bind browser n check-new'). And now the thing: (1) The 'N' flag appears *only* for bar/, not for the last-visited foo/. (2) Choose any mailbox but foo/, hit Return to enter it, and find yourself in foo/. This works vice versa if bar/ was visited last. I also have set timeout=2 set mail_check=20 The issue turns up always, regardless of whether I wait $timeout+$mail_check seconds before invoking check-new or not, but *only* if I do use check-new. So, from what I see, mutt (at least mine) does not flag the last-visited mailbox correctly when I use check-new and does open it, although I selected another one. And now here another, related problem. After reading some more docs I began to imagine that actually most users seem to work like so: have one mailbox open (not the browser) and change directly to other mailboxes, not via the browser. I tried that and I was surprised. That works exactly as I expected. I got informed by a message "New mail in ..." after $timeout+$mail_check seconds automatically and without pressing a key. This brings me back to my fist posting. Apparently mutt's check-for-new-mail-and-inform-me machinery works like a charm ... but from what I see only if I'm in the message index of an open mailbox, and not in the browser, i.e. the 'N' flag does not appear "automatically" just as the "New mail in ..." messages do. Why is this so. Is this intended behavior? Does anybody else have this issue (besides Raffi Khatchadourian) or am I just not using mutt the "mutt way"? Thanks. s.
Re: message index: new mail, mutt doesn't open right folder
On Mon, Feb 18, 2008 at 11:33:07AM +0100, Steve S wrote: > Suppose I have three mailboxes > > mailboxes +foo +bar +stuff > > and mutt is open all the time. The last mailbox I visited is foo/. Now mail > arrives for all three boxes. I'm in the message index and navigate to bar/, > press Return to enter the mailbox. But instead of opening bar/, I'm ending up > in foo/, i.e. the box which (1) also has new mail and (2) was the last mailbox > that was open. > Hi all Sorry, I just found that I caused big confusion here. In my writing I ment to speak about the "browser", but always said "message index". That has confused the people answering me. Sorry again. Please ignore this thread. I did some more testing and will post the results in a new thread. s.
Re: How to send mail with a sign gpg in attachment like
Kyle Wheeler <[EMAIL PROTECTED]> writes: > On Monday, February 18 at 09:04 PM, quoth Dave Evans: >> On Fri, Feb 15, 2008 at 10:35:07AM -0600, Kyle Wheeler wrote: >>> Where is that header defined? Why not use the OpenPGP header (defined >>> here: http://josefsson.org/openpgp-header/) >> >> Is it just me, or does the example on that page not match the draft spec? >> The spec AFAICT requires "id=" before the ID; the example omits "id=". >> >> It also seems odd that the id is allowed to be empty (zero or more HEXDIG). > > That is rather odd. Why not ask the author? Indeed, the web page was missing a 'id='. Earlier versions of the idea allowed the 'id=' string to be optional, but that is no longer the case. I have changed the key id field to be at least 8 hex characters long. The reason it isn't hard coded to a particular length is that openpgp fingerprints may be of different lengths. Still, 8 hex characters appear to be the minimum length in use today. I'm going to submit an updated -03 version of the document soon, so if any of you have any comments on the latest protocol, now would be a perfect time to send them. The latest document is available from: http://josefsson.org/openpgp-header/draft-josefsson-openpgp-mailnews-header.txt Thanks, /Simon
