From: David Masterson <dsmasterson92630@outlook.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Getting Org-Crypt to work (doc bug?)
Date: Wed, 16 Sep 2020 23:16:21 -0700 [thread overview]
Message-ID: <SJ0PR03MB5615EC27454378480CDEEE129B3E0@SJ0PR03MB5615.namprd03.prod.outlook.com> (raw)
In-Reply-To: <SJ0PR03MB5615A2ACB8EF1EF0AC8ED0E79B230@SJ0PR03MB5615.namprd03.prod.outlook.com> (David Masterson's message of "Mon, 14 Sep 2020 14:24:31 -0700")
David Masterson <dsmasterson92630@outlook.com> writes:
> David Masterson <dsmasterson92630@outlook.com> writes:
>
>> Bastien <bzg@gnu.org> writes:
>>
>>> Hi David,
>>>
>>> David Masterson <dsmasterson92630@outlook.com> writes:
>>>
>>>> Both things should be mentioned in the Org-Mode Info pages for
>>>> org-crypt.
>>>
>>> Can you please provide a patch for this?
>>>
>>> Thanks,
>>
>> I'm not very good with this yet, but, when I figure it out, I will
>> certainly consider a patch. Never having done a patch before, could you
>> list the steps for providing a patch?
>
> Nevermind -- here's the patch:
>
> -----------------
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 3eb745b5d..775af7a13 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19650,8 +19650,9 @@ an Org file that is part of a publishing project.
:END:
Org Crypt encrypts the text of an entry, but not the headline, or
-properties. Behind the scene, it uses the Emacs EasyPG library to
-encrypt and decrypt files.
+properties. Behind the scene, it uses the [[info:epa][Emacs EasyPG Library]] to
+encrypt and decrypt files. Also, pay attention to the installation
+and setup of [[info:gnupg][GnuPG]]
#+vindex: org-crypt-tag-matcher
Any text below a headline that has a =crypt= tag is automatically
> -----------------
I didn't see a reply -- does the above patch work? Have you applied it?
--
David Masterson
next prev parent reply other threads:[~2020-09-17 6:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 2:09 Getting Org-Crypt to work (doc bug?) David Masterson
2020-09-13 8:32 ` Gregor Zattler
2020-09-14 0:11 ` David Masterson
2020-09-14 8:42 ` Gregor Zattler
2020-09-14 11:19 ` tomas
2020-09-13 8:36 ` Nicolas Goaziou
2020-09-14 0:02 ` David Masterson
2020-09-14 11:18 ` Colin Baxter
2020-09-14 11:25 ` tomas
2020-09-14 14:17 ` Colin Baxter
2020-09-15 9:15 ` Robert Pluim
2020-09-14 20:31 ` David Masterson
2020-09-14 12:50 ` Bastien
2020-09-14 20:35 ` David Masterson
2020-09-14 21:24 ` David Masterson
2020-09-17 6:16 ` David Masterson [this message]
2020-09-17 7:06 ` Bastien
2020-09-23 9:05 ` Bastien
2020-09-23 21:33 ` David Masterson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR03MB5615EC27454378480CDEEE129B3E0@SJ0PR03MB5615.namprd03.prod.outlook.com \
--to=dsmasterson92630@outlook.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).