summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKyle Meyer <kyle@kyleam.com>2014-03-16 17:56:51 -0400
committerKyle Meyer <kyle@kyleam.com>2014-03-16 17:56:51 -0400
commitd367273cbc85911c520a6c513f7bcbd0773ba2c6 (patch)
tree3d3aea9cd49b13ef3e24dd2ee53902bacbf8f41b
parentc858383c5870c7715b8f086316f7f60fdb228570 (diff)
downloadbog-d367273cbc85911c520a6c513f7bcbd0773ba2c6.tar.gz
DOC: Remove incorrect line in README
If locating fails, an error will be given. Currently, the user is only prompted if function-specific and only when the prefix argument is given.
-rw-r--r--README.md3
-rw-r--r--bog-readme.org3
2 files changed, 2 insertions, 4 deletions
diff --git a/README.md b/README.md
index b529363..5b3b51b 100644
--- a/README.md
+++ b/README.md
@@ -63,8 +63,7 @@ settings can be modified.
Many Bog functions take the citekey from the notes context. If the point
is on a citekey (like "another1999study" above), then that citekey will
be used. Otherwise, the citekey will be taken from the first parent
-heading that is a study. If one isn't found, the user will be prompted
-for the citekey.
+heading that is a study.
## Opening a PDF file for a citekey
diff --git a/bog-readme.org b/bog-readme.org
index 3a334a4..1f3b858 100644
--- a/bog-readme.org
+++ b/bog-readme.org
@@ -48,8 +48,7 @@ settings can be modified.
Many Bog functions take the citekey from the notes context. If the point
is on a citekey (like "another1999study" above), then that citekey will
be used. Otherwise, the citekey will be taken from the first parent
-heading that is a study. If one isn't found, the user will be prompted
-for the citekey.
+heading that is a study.
** Opening a PDF file for a citekey