From: David Masterson <dsmasterson92630@outlook.com>
To: emacs-orgmode@gnu.org
Subject: Re: Getting Org-Crypt to work (doc bug?)
Date: Sun, 13 Sep 2020 17:02:04 -0700 [thread overview]
Message-ID: <SJ0PR03MB5615191CC61BC45AABF6CDD39B230@SJ0PR03MB5615.namprd03.prod.outlook.com> (raw)
In-Reply-To: <87h7s2gjjz.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 13 Sep 2020 10:36:16 +0200")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> David Masterson <dsmasterson92630@outlook.com> writes:
>
>> I'm trying to get org-crypt to work, but I'm missing something.
>> Following the Org-Crypt Info page, I've set it up for symmetric
>> encryption and added a :crypt: tag to a header. When I try to save the
>> file, it reports that no key was specified, so it will do symmetric
>> encryption. And then it freezes. C-g will unfreeze, but the buffer is
>> slightly messed up like it started working on something, but waited for
>> an external command? GPG is installed. What am I missing?
>
> Could you explain more precisely what you did? For example, I encounter
> no problem crypting the following file:
>
> * Test :crypt:
>
> This is crypted.
>
> # Local Variables:
> # org-crypt-key: nil
> # End:
>
> Upon saving the file, I type the key twice, and the entry is encrypted.
>
> Note that I evaluated (org-crypt-use-before-save-magic) once beforehand.
I'm setting up Org this way:
(use-package org
:init (setq
org-tags-exclude-from-inheritance '("crypt")
org-crypt-key nil
)
:config (progn
(require 'org-crypt)
(org-crypt-use-before-save-magic)
)
)
I did essentially what you did (added :crypt: to a header in one of my
files) and tried to save the file.
Found it! I started Emacs on Linux via 'xterm -e emacs &' because
something else had done this to me (forget what). The thing is that GPG
is asking for the passphrase on the xterm window and not in the Emacs.
I didn't notice this because Emacs covered it. Someone else mentioned
the gpg-agent(?) to prevent this (is there another way?). Both things
should be mentioned in the Org-Mode Info pages for org-crypt.
--
David Masterson
next prev parent reply other threads:[~2020-09-14 0: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 [this message]
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
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=SJ0PR03MB5615191CC61BC45AABF6CDD39B230@SJ0PR03MB5615.namprd03.prod.outlook.com \
--to=dsmasterson92630@outlook.com \
--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).