{"shas":[["3f0d3dabfcec3e1e1bed7a5108372601b3240037","64e5defaed355eedb42b1edffaa6659adacce553@anche.no","fixed issue #3: a simple file check on the key is now performed before creating the tomb","Anathema"],["d4de059e3926fccd10bc00d7cf331de2ebc3d964","64e5defaed355eedb42b1edffaa6659adacce553@anche.no","added cryptsetup and pinentry binary checks to check_bin()","Anathema"],["7b2fc78b1974297b3278e21e0784a4542640f115","7435d1ab04b493cf38d07d3a8a560e42337e7f58@dyne.org","Merge pull request #17 from davinerd/fix_issue3\n\nfix issue #3\r\ncreate now avoids ovewriting an existing tomb key: quits with error.","DJR"],["58e2b26694b1ed73d04e61722295653cc94957cb","7435d1ab04b493cf38d07d3a8a560e42337e7f58@dyne.org","Merge pull request #16 from davinerd/dependencies\n\nall dependencies are checked for at startup","DJR"],["c71bd81af238fbb76269e940d8217c8839abed9f","018b104ba2ae0efe13b5c3b43cf0dfdf7be2a099@gmail.com","New optparsing, with zparseopts\n\n* parameters can be added where you want\n* it's possible to use long options\n* you can have \"synonim\" options\n* it has potential for a recursive implementation","BoySka"],["89d4b8d8d0770bb0a52cf14ff72661ff91280d03","28cb93e60517febc1ae50f3b16b023e80136c0ca@logorroici.org","Optparsing: add other commands\n\nNow all commands should have been ported","boyska"],["d0e004412d31ae13b05b4ccbdccda7ee3b201840","28cb93e60517febc1ae50f3b16b023e80136c0ca@logorroici.org","Changing optparsing, tomb-open needs changes\n\nIt was putting the option BEFORE the subcommand.\nHowever, the new method supports this only partially:\n* Boolean options can be put before the subcommand\n* Subcommand-specific options that take an argument can be put before the\n  subcommand, only in the\n  form  -kvalue ; using -k value gives an error\n* Global options can always be put before the subcommand\n\nTherefore, we'll say that options MUST go after the subcommand (to stay sure)","boyska"],["6495099344300db1e6e7d24b8825cd7735656f97","28cb93e60517febc1ae50f3b16b023e80136c0ca@logorroici.org","[Optparsing] Support options in whatever position\n\nHowever, it has a precondition that developers MUST respect:\n  An option CAN'T have differente meanings/behaviour in different subcommands.\n  For example, \"-s\" means \"size\" and accept an argument. If you are tempted to add\n  an option \"-s\" (that means, for example \"silent\", and doesn't accept an argument)\nThis, however, make sense even from an usability point of view.\nAlso, option with optional argument are prohibited.\n\nThe technique is a \"double scan\": first, we scan options passing\n_every_ possible subcommand options to zparseopts.\nThis way, we can distinguish between option argument and parameters.\nSo, we recognize which is the subcommand.\nThen, parse again","boyska"],["d5ca1885ca71dfb7d562ae7aeef97f08f090ce52","28cb93e60517febc1ae50f3b16b023e80136c0ca@logorroici.org","[Optparsing] do a shift to delete subcommand","boyska"],["a252f62fba4ca366f150952d8842d1c766201ff1","28cb93e60517febc1ae50f3b16b023e80136c0ca@logorroici.org","Fix #14: problems with spaces in option arguments","boyska"],["21be9e204e7eead1f67ce6cf454e71591b311954","7435d1ab04b493cf38d07d3a8a560e42337e7f58@dyne.org","Merge pull request #18 from boyska/only_optparsing\n\nNew CLI option parsing supports contextual options following commands.\r\n\r\nZSH functions are used to parse options. Further testing will follow.","Jaromil"]],"ref":"refs/heads/master","size":11,"head":"21be9e204e7eead1f67ce6cf454e71591b311954","push_id":38766886}