[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .

Policy Of Command Creation

fml8 provides a different command for each function. Its policy makes the number of commands infinite. So, except for some special cases, we should unify all functions into makefml/fml command since such commands can be shared among CUI, GUI and commmnd mail.

Operation May Modify The Specific ML (Read + Write)

We should implement sub-command of makefml/fml when some operation may modify the specific ML.

Operation For Read Only Data Of The Specific ML (Read Only)

We should implement it as a makefml/fml command since it is related to the specific ML.

Show The General Data (Read Only)

If the data is not related to the specific ML, for example, see the module manual, aliases on the host, we implement specific commands other than makefml/fml. This command name begins with "fml" prefix.

fmladdr	 [-n]
fmlalias [-n]
fmldoc   MODULE
fmlconf  [-n] ML

ML Specific But A Command Wrapper

PGP / GPG related command (e.g. fmlpgp) is very command speicific. So, it looks difficult to incorporate them into "makefml" and "fml" framework. So we implement it as another command such as fmlpgp, fmlgpg, ...

Misc

We implement specific commands other than makefml/fml. This command name begins with fml prefix.

For example, "fmlhtmlify" is a conveter from text to html form. This command is used to convert both fml spool and MH folders.

fmlhtmlify [-I DIR] $src_dir $dst_dir

[HOME] [NSRG] [インフラ] [fml4] [fml8] [北海道] [おすすめの本] Powered by NetBSD and [nuinui.net] .
Copyright (C) 1993-2017 Ken'ichi Fukamachi mail:< fukachan at fml.org >