From: Jason Lewis <jason@dickson.st>
To: 16679@debbugs.gnu.org
Subject: bug#16679: 24.3.50; can't create a newly encrypted gpg file with easypg in cygwin emacs
Date: Fri, 07 Feb 2014 15:45:05 +1100 [thread overview]
Message-ID: <52F464D1.7070804@dickson.st> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1038 bytes --]
Creating a new file that is to be encrypted in emacs with easypg fails
with the error: Opening output file: stringp, nil
Steps to reproduce:
emacs -Q
(require 'epa-file)
(epa-file-enable)
C-x C-f somefile.gpg <enter>
type some text and try and save the file with C-x C-s
observe error: Opening output file: stringp, nil
and file is not saved.
I expect it should ask me which gpg key I want to encrypt the file for
rather than throwing an error.
I tested this with emacs -Q under cygwin and got the error
emacs compiled today from git. version "24.3.50.1"
checkout: fa431ad4a3f3040f6cc4535627c4d6f48ede9a94
I also tested on linux emacs v. 24.3.50.1
where it seems to work as expected.
backtrace seems to include some control characters, i presume because
the el files are compiled to elc
unfortunately I was unable to determine which files I should change to
.el files so it would have a proper backtrace
included here in case that's of use?
Jason Lewis
http://emacstragic.net
[-- Attachment #1.2: easypg-backtrace.gz --]
[-- Type: application/x-gzip, Size: 402 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 834 bytes --]
next reply other threads:[~2014-02-07 4:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 4:45 Jason Lewis [this message]
2014-02-08 1:42 ` bug#16679: 24.3.50; can't create a newly encrypted gpg file with easypg in cygwin emacs Glenn Morris
2014-02-08 8:54 ` Eli Zaretskii
2014-02-08 10:05 ` Jason Lewis
2014-02-08 14:18 ` Eli Zaretskii
2014-02-10 23:04 ` Jason Lewis
2014-02-11 3:46 ` Eli Zaretskii
2014-02-11 5:15 ` Jason Lewis
2014-02-11 16:05 ` Eli Zaretskii
2014-02-12 2:38 ` Jason Lewis
2019-08-30 10:59 ` Lars Ingebrigtsen
2019-08-30 11:44 ` Jason Lewis
2019-09-04 13:00 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52F464D1.7070804@dickson.st \
--to=jason@dickson.st \
--cc=16679@debbugs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.