summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/wishlist__58___optionally_print_key_in_output_of_checkpresentkey_batch_mode/comment_1_f95f2c92a46c1bd00c627aa19b08c875._comment13
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/todo/wishlist__58___optionally_print_key_in_output_of_checkpresentkey_batch_mode/comment_1_f95f2c92a46c1bd00c627aa19b08c875._comment b/doc/todo/wishlist__58___optionally_print_key_in_output_of_checkpresentkey_batch_mode/comment_1_f95f2c92a46c1bd00c627aa19b08c875._comment
new file mode 100644
index 000000000..db469b88e
--- /dev/null
+++ b/doc/todo/wishlist__58___optionally_print_key_in_output_of_checkpresentkey_batch_mode/comment_1_f95f2c92a46c1bd00c627aa19b08c875._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-07-11T16:36:11Z"
+ content="""
+Hmm, my assumption is that use of checkpresentkey --batch is in some kind
+of loop, or function call, where you'd write a key to it, read a response
+back, and now you know whether that key is present.
+
+Does your use case involve something like shell scripting? I suppose if you
+have a big list of keys and want to narrow it to only keys that are present
+or missing, you could be trying to pipe it through checkpresentkey --batch.
+"""]]