I just realized that you can do "refile 1 +" and it works perfectly well,
that is: It does the only consistent thing to do and puts the message
directly into ~/Mail
That could very well be the most sensible behaviour. The semantics of
the +folder syntax are an absolute folder path, meaning that "+"
indicates the root of the dirtree containing the folders. At least,
that's what I understand by the contrast with the (undocumented?) @folder
syntax, which indicates a relative folder path.
Actually it seems that most commands work fairly well on "+" but there
is one anomaly: The current folder always gets set to "+inbox", no matter
where you start from! That is: "scan +" displays the contents of
~/Mail but sets the current folder to ~/Mail/inbox
That kind of inconsistency is undesirable. Do we want to change the
context to the folder root or make the "+" with no folder name a special
case?
But if for some odd reason you want to set you current folder to ~/Mail
you still can do it by specifying "+inbox/..".
I'm more disturbed by the possibility that one could go outside the
folder tree with enough double dots.
In fact, there looks to be a host of inconsistent behaviour. "+/" will
scan the root *directory*. "+.." does *not* scan the directory above
the folder root, but rather the directory above that. "+." scans the
directory above the folder root.
However "folders" will neither find "+" nor "+inbox/.." nor any
equivalent (for obious reasons you'll say) thus making ~/Mail
(and everything upwards in the hierarchy) an invisible folder.
Not quite.
If a +folder is given along with the -all switch, folder will, in addi-
tion to setting the current folder, list the top-level subfolders for
the current folder (with -norecurse) or list all sub-folders under the
current folder recursively (with -recurse). In this case, if a msg is
also supplied, it will become the current message of +folder.
succubus: {340} folders +
FOLDER # MESSAGES RANGE; CUR (OTHERS)
+ has no messages ; (others).
/altroot has no messages.
/bin has no messages ; (others).
/dev has no messages ; (others).
/etc has no messages ; (others).
/home has no messages ; (others).
/kern has no messages ; (others).
/lib has no messages ; (others).
/libexec has no messages ; (others).
/mnt has no messages.
/proc has no messages.
/rescue has no messages ; (others).
/root has no messages.
/sbin has no messages ; (others).
/stand has no messages.
/tmp has no messages ; (others).
/usr has no messages ; (others).
/var has no messages ; (others).
TOTAL = 0 messages in 18 folders.
So the behaviour is odd here, but presumably it's still possible to
see these other "folders".
What are everyone's thoughts on the best way to clean up these semantics?
Cheers,
- Joel
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers