I want to call a script which will pass back a file to source like this:
source `path-to/script.sh`
I would like to set the path to the script in my muttrc with a mutt
user-defined variable. This doesn't work because mutt doesn't appear to
expand the variable before passing the part in
David T-G [EMAIL PROTECTED] wrote on Mon, 05 Jun 2000:
I'm not sure I understand what you're asking, but I'll take a whack at
it.
I didn't understand it either, but your guess does seem to make sense...
You want mutt to have a save-hook that will specify a directory of
mailboxes which
Mikko Hänninen:
Actually, you could embed `mkdir -p dirname` in any command -- it gets
expanded but the result is an empty string. However the command does
run. :-)
whowherewhat? where are commands like this allowed like this?
--
clemens
I found this in the procmailex man page:
Store all the messages about meetings in a folder that is
in a directory that changes every month. E.g. if it were
January 1994, the folder would have the name `94-01/meet
ing' and the locallockfile would be
Jason --
...and then [EMAIL PROTECTED] said...
% I found this in the procmailex man page:
Good enough...
%
...
% :0:
% * meeting
% `date +%y-%m`/meeting
...
% :0 Wic
% * ? test ! -d $MONTHFOLDER
% | mkdir
Eric Smith [EMAIL PROTECTED] wrote on Mon, 08 May 2000:
How may I check on the current state of a mutt variable? (likeis possible
in vi?
Either
:set ?var
or
:set var=tab
where tab is a keypress.
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] //
