On Mon, Aug 10, 2009 at 10:38:10AM -0500, Kyle Wheeler wrote:
> On Sunday, August  9 at 09:14 PM, quoth Robert Holtzman:
>> The problem was that I stupidly modified the list of mail lists to  
>> duplicate the list of mailboxes. When I went back and realized what I 
>> had done I restored both lists from my backup (let's hear it for  
>> backups!)and added the rkhunter and sounder lists. Now I'm getting  
>> this error message:
>>
>> Error in /home/holtzm/.muttrc, line 298: +saved-slrn-user: unknown  
>> command source: errors in /home/holtzm/.muttrc Press any key to 
>> continue...
>
> Generally speaking, that means that you have a line that starts with  
> “+saved-slrn-usr”, rather than with a regular command.
>
>> #mailboxes ! +mutt-dev +mutt-users +open-pgp +wmaker +hurricane +vim
>> +ietf \
>> 287 #       +drums
>> 288
>> 289
>> 290 mailboxes ! +INCOMING +list-Chevelle +list-PLUG-discuss
>> +list-alpine-info \
>> 291             +list-clamav +list-debian-users +list-exim-users
>> +list-firefox-support \
>> 292             +list-gnupg-users +list-mondo-devel +list-mutt-users
>> +list-openoffice-discuss \
>> 293             +list-openoffice-users +list-procmail +list-slrn-user
>> +list-ubuntu-users +spam \
>> 294             +list-rkhunter +list-sounder +list+saved-alpine
>> +saved-Chevelle +saved-clamav \
>> 295             +saved-debian-users +saved-firefox-support
>> +saved-gnupg-users +saved-mondo-devel \
>> 296             +saved-mutt-users +saved-openoffice-users +saved-PLUG
>> +saved-procmail \
>> 297             +saved-slrn-user +saved-ubuntu-users +saved-messages \
>> 298 #mailboxes `echo $HOME/Mail/*`
>
> Two things: first, I think you have a space at the end of line 295  
> (after the backslash), which breaks the line wrapping. Second, you told 
> mutt to connect lines 297 and 298 (with the backslash at the end), so 
> mutt identifies the whole line by it’s last line number.

That nailed it. I never would have caught it.


>> The line wrapping is weird but you can follow it.
>
> When I get into trouble like that, I always first glue the wrapped lines 
> back together. You have no idea how often (or in how many different 
> programs) doing that has revealed to me that I had a simple  
> line-wrapping error, rather than some other problem.

That tip is worth a lot of beer if you're ever in the area.

>>> (Do you know what the + is there for?)
>>
>> As a matter of fact no. Explain, please.
>
> I thought not - lots of folks get tripped up by that. It’s actually a  
> shortcut for a mailbox specification. Both the + symbol and the = symbol 
> can be used when specifying a mailbox name as a shorthand for the value 
> of $folder.
>
> Think of it this way (I’m using example names here): the mailboxes  
> command expects FULL PATHS to mailboxes, like this:
>
>     mailboxes /home/myname/mail/inbox /home/myname/mail/lists
>
> But that’s a lot to type, and can make the list of mailboxes hard to  
> read. BUT, you can do this instead:
>
>     set folder=/home/myname/mail
>     mailboxes +inbox +lists
>
> The equals sign is a synonym for the plus sign in this context, and can 
> be used as well, if you prefer it:
>
>     set folder=/home/myname/mail
>     mailboxes =inbox =lists
>
> This can be especially useful when using things like imap, where $folder 
> is something big and ugly like  
> “imaps://user:passw...@imap.server.com/INBOX”.
>

That's the kind of information I have never bee able to get running
searches and reading docs.

>>>>> What, specifically, are you trying to do? I mean, you can  
>>>>> literally start a www browser in an external program by doing  
>>>>> this:
>>>>>
>>>>>      !firefox
>>>>
>>>> Not sure where in ~/.muttrc to put this.
>>>
>>> I didn’t say you put that in your muttrc, I said you’d “do” that, by  
>>> which I mean “this is a key sequence to press while running mutt.” 
>>> Sorry if I was unclear. By default, the exclamation mark (pressed 
>>> while mutt is running) tells mutt to get ready to run a shell 
>>> command. Once you press that, type in “firefox” (or whatever command 
>>> to launch a web browser), and hit return. That will cause mutt to run 
>>> that command.
>>>
>>> But that’s just a way to “launch a web browser”, not a way to send 
>>> URLs from your email to that browser.
>>
>> Pardon my seeming ingratitude but from your description, it doesn't 
>> seem to do any more than if I switched workspaces, opened FF and pasted 
>> in the url. Did I miss something?
>
> Nope, that’s exactly right. I didn’t quite understand what you were  
> trying to do, so that seemed as good an answer as any other.
>

I was hoping to duplicate slrn's capability of showing a menu with all
the urls in the message allowing you to highlight one and hit <return>.
That opens the browser in the ~/.slrnrc file and loads the selected url.

I ran across the urlscan package in the repository and installed it. The
description indicates that it is at least close to what I want. Haven't
had a chance to play with it yet.

I  noticed that I had inadvertantly replied directly to you a couple of
times instead of to the list. My apologies.

Many thanks for walking me thru all this. Coming over from pine/alpine,
mutt's rc file is a little weird but I'm slowly getting it.

Take care. 

-- 
Bob Holtzman
"If you think you're getting free lunch,
 check the price of the beer"

Reply via email to