Rob 'Feztaa' Park wrote:
> Alas! Benjamin Smith spake thus:
> > The ways that script works is by outputting the muttrc to a tempory
> > file, the name of which is outputted for source, but what you can do is
> > just to put:
> >
> > `~/bin/do-whatever.sh`
> >
> > In the muttrc and mutt will int
On Sun, Jan 06, 2002 at 01:30:35AM -0700, Rob 'Feztaa' Park wrote:
> Alas! Benjamin Smith spake thus:
> > The ways that script works is by outputting the muttrc to a tempory
> > file, the name of which is outputted for source, but what you can do is
> > just to put:
> >
> > `~/bin/do-whatever.sh`
Alas! David T-G spake thus:
> % The .muttrc is fairly robust. You can put almost any shell command into
> % backticks (``), and it will be as though the output of that command is
> % actually in the .muttrc file. This is why mutt is so much better than
> % pine :)
>
> Um, yeah; that's the *only*
Alas! Benjamin Smith spake thus:
> The ways that script works is by outputting the muttrc to a tempory
> file, the name of which is outputted for source, but what you can do is
> just to put:
>
> `~/bin/do-whatever.sh`
>
> In the muttrc and mutt will interpret the output of the shell script
> wi
Rob --
...and then Feztaa said...
%
...
% The .muttrc is fairly robust. You can put almost any shell command into
% backticks (``), and it will be as though the output of that command is
% actually in the .muttrc file. This is why mutt is so much better than
% pine :)
Um, yeah; that's the *only
On Sat, Jan 05, 2002 at 10:11:10AM -0700, Rob 'Feztaa' Park wrote:
> Alas! Gerhard Siegesmund spake thus:
> > > > > > You could put that in a script such as the one I've attached, and run
> > > > > > it from .muttrc like this:
> > > > > > source `$HOME/bin/mutt-prep folders=$HOME/mail`
> > > > Tha
Alas! Gerhard Siegesmund spake thus:
> > > > > You could put that in a script such as the one I've attached, and run
> > > > > it from .muttrc like this:
> > > > > source `$HOME/bin/mutt-prep folders=$HOME/mail`
> > > Thanks for your help, guys, this is what I've come up with:
> > > my .muttrc con
> > > > You could put that in a script such as the one I've attached, and run
> > > > it from .muttrc like this:
> > > > source `$HOME/bin/mutt-prep folders=$HOME/mail`
> > Thanks for your help, guys, this is what I've come up with:
> > my .muttrc contains this line:
> > source `~/bin/mbox-hooks`
Alas! Gary Johnson spake thus:
> > cd - > /dev/null 2>&1
>
> This is not necessary. The command within `s is executed as a child
> process of mutt. Unix child processes cannot affect the working
> directory of their parent. So, none of the cd'ing within the mbox-hooks
> command will have any e
On Fri, Jan 04, 2002 at 07:04:12PM -0700, Rob 'Feztaa' Park wrote:
> Alas! Rob 'Feztaa' Park spake thus:
> > > I'm into overkill today.
> > >
> > > You could put that in a script such as the one I've attached, and run
> > > it from .muttrc like this:
> > >
> > > source `$HOME/bin/mutt-prep folde
Alas! Rob 'Feztaa' Park spake thus:
> > I'm into overkill today.
> >
> > You could put that in a script such as the one I've attached, and run
> > it from .muttrc like this:
> >
> > source `$HOME/bin/mutt-prep folders=$HOME/mail`
Thanks for your help, guys, this is what I've come up with:
my .
Alas! David Champion spake thus:
> > > and just source .muttrc-auto from .muttrc. Ugly but would work.
> >
> > Interesting idea. I'm sure I've seen a better way to do it, though.
> > Perhaps I'll have to search the archives :)
>
> I'm into overkill today.
>
> You could put that in a script such
On 2002.01.04, in <[EMAIL PROTECTED]>,
"Rob 'Feztaa' Park" <[EMAIL PROTECTED]> wrote:
> Alas! Cameron Simpson spake thus:
> > | I'm pretty sure I've seen this done somewhere, but I can't find it.
> >
> > Well, it's indirect, but you could wrap mutt in a script which said:
> >
> > #!/
Alas! Cameron Simpson spake thus:
> | I'm pretty sure I've seen this done somewhere, but I can't find it.
>
> Well, it's indirect, but you could wrap mutt in a script which said:
>
> #!/bin/sh
> ( cd $HOME/mail
> when=`date +%Y-%m`
> for mbox in *
> do echo "
On Tue, Jan 01, 2002 at 11:07:08PM -0700, Rob 'Feztaa' Park <[EMAIL PROTECTED]> wrote:
| Hey all. I was just wondering if there was some way that I could get
| mutt to automatically set up my mbox hooks for every folder in my ~/mail
| directory, so that way I can subscribe to a new mailing list wi
Alas! David T-G spake thus:
> It's untested, but what about
>
> mbox-hook . "=archives/`date +%Y-%m`-%O"
Sorry, doesn't work. It sees %O as the literal string, doesn't expand it
into anything.
--
Rob 'Feztaa' Park
[EMAIL PROTECTED]
--
"The wireless music box has no imaginable commercial valu
Rob --
...and then Feztaa said...
%
% Hey all. I was just wondering if there was some way that I could get
% mutt to automatically set up my mbox hooks for every folder in my ~/mail
% directory, so that way I can subscribe to a new mailing list without
% having to edit my .muttrc.
%
% Right now
Hey all. I was just wondering if there was some way that I could get
mutt to automatically set up my mbox hooks for every folder in my ~/mail
directory, so that way I can subscribe to a new mailing list without
having to edit my .muttrc.
Right now I've got this set up:
mbox-hook =spam "=archives
18 matches
Mail list logo
