headers
belg4mit | 16 May 2009 17:50

Sent draft filenames

Hello all,

What's responsible for the production of files named ",X"? I get them in
my regular folders, and posted drafts are renamed to this style as well.
My system used to instead name sent messages ".#X", which is compatible
wth Athena delete, but has recently reverted to clogging my folders with
the comma files.

I've read through whatnow, send, post and mh-draft but no joy...

My rmmproc is rm; but rmm is aliased to 'refile +Trash'

Thanks in advance,

Jerrad
--

-- 
Free map of local environmental resources: http://CambridgeMA.GreenMap.org
--
MOTD on Sweetmorn, the 63rd of Discord, in the YOLD 3175:
Economics is a disease --Hazel Henderson

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 2 comments |
headers
Peter Maydell | 16 May 2009 19:34
Picon

Re: Sent draft filenames

belg4mit <at> pthbb.org wrote:
>What's responsible for the production of files named ",X"? I get them in
>my regular folders, and posted drafts are renamed to this style as well.
>My system used to instead name sent messages ".#X", which is compatible
>wth Athena delete, but has recently reverted to clogging my folders with
>the comma files.

The backup prefix is a compile time option (configure --with-hash-backup
will make it use '#' rather than ','; for anything more complicated you
probably need to modify the sources). The function m_backup() creates a
file with this prefix, and it's used in various bits of nmh that want
to create a backup file.

Have you upgraded your nmh recently and accidentally lost a local
configuration, perhaps?

-- PMM

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 1 comment |
headers
Jerry Peek | 16 May 2009 19:53
Gravatar

Re: Sent draft filenames

Peter Maydell wrote:
> The backup prefix is a compile time option (configure --with-hash-backup
> will make it use '#' rather than ','; for anything more complicated you
> probably need to modify the sources).
>   

For people can't compile and configure nmh -- maybe because they install 
it from a pre-compiled package -- I wonder if this should be different.  
I can't even guess how many people use nmh on systems with more than one 
user, where software is installed and maintained by an administrator 
instead of the user... though it can't be near as many as when I started 
using MH.  Still, people could have good reasons to choose a different 
prefix -- including prefixes that have more than one character, like 
Jerrad's ".#".

Would it be reasonable to let users set the backup prefix in their 
.mh_profile files?  Any security or other problems I'm not thinking of?  
I guess that "/" shouldn't be allowed in the prefix... and probably not 
whitespace or newline (because that'd be tricky to parse in the 
.mh_profile).  Comments, anyone?

Jerry

_______________________________________________
Nmh-workers mailing list
Nmh-workers <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers
Permalink | Reply | 0 comments |

Gmane