I want to get familiar with making my own bash complition functions and spend some time over a bash completion file for makenemo and would like to share it:). 

I know that probably only 1% of the time makenemo is called interactivly (not from script) but for people like me wich seems to forget the avaliable options it could be usefull.

There several tricks that one have to know about this function(s):

• currently an "echo -e" is used for multiline print which AFAR is not posix, so porting it to non linux(AIX for example) systems needs the use of "printf" instead (but I'm too lazy to do it now :) );
• if makenemo is in the $PATH it should be located in NEMOGCM/CONFIG (the default) and all the complition is done relatively to this directory, using $(dirname $(which ${COMP_WORDS[0]})) ), so that it really could be runned from anyware (as it is now);
• the "add_key" and "del_key" compliton follows the makenemo logic (as I understand it :) ) - if "-r ANYTHING" is given its argument is used, if not - the argument of "-n OTHER_THING" is used. In case non of them is given the default ( last of cfg.txt) is used;
• if ones wants to use the add_key completion functionality a file called NEMOGCM/CONFIG/YourConfigName/cpp_all_YourConfigName.fcm  have to be created containing a space separated list of all possible keys for YourConfigName. If fact I don't see any easy way to get all the possible keys in one configuration except greping recursively. It will be great if makenemo generates such file.
• the function can complete multiple keys (add_key, del_key) and several folders (-d) but one have to press backspace and delete the closing quotes(") in order to start the completion mechanism for the n-th key;
• there are some features that can make you not so happy - if the written text doesnt mach the complition it could be removed... I left it only for some cases that I knew the option/argument is wrong.

Regards:)!

Opening of a branch for 2012 development of the TOP interface with complex BGC models like the BFM.

http://forge.ipsl.jussieu.fr/nemo/svn/branches/2012/dev_r3379_CMCC6_topbfm

Create a branch for the merge of CMCC developments in 2012 :

dev_r3365_CMCC1_BDYOBCopt dev_r3379_CMCC6_topbfm