Alternately, if you wish for rmm to really remove the files representing these messages, you can use the `-unlink' switch. But messages removed by this method cannot be later recovered.
If you prefer a more sophisticated method of `removing' messages, you can define the rmmproc profile component. For example, you can add a profile component such as
then instead of simply renaming the message file, rmm will call the named program or script to handle the files that represent the messages to be deleted.
Some users of csh prefer the following:
alias rmm 'refile +d'
where folder +d is a folder for deleted messages, and
alias mexp 'rm `mhpath +d all`'
is used to ``expunge'' deleted messages.
The current message is not changed by rmm, so a next will advance to the next message in the folder as expected. ^$HOME/.mh_profile~^The user profile ^Path:~^To determine the user's nmh directory ^Current-Folder:~^To find the default current folder ^rmmproc:~^Program to delete the message refile(1), rmf(1) `+folder' defaults to the current folder `msgs' defaults to cur `-nounlink' If a folder is given, it will become the current folder. Since refile uses your rmmproc to delete the message, the rmmproc must NOT call refile without specifying `-normmproc', or you will create an infinte loop.