Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
Subject: Re: EasyPG 0.0.1, yet another GnuPG interface for Emacs
Date: Wed, 10 May 2006 15:14:32 +0200	[thread overview]
Message-ID: <8764keqax3.fsf@mat.ucm.es> (raw)
In-Reply-To: <3d4dd9a5-9554-45ad-8317-99fa21e34142@well-done.deisui.org>

[-- Attachment #1: Type: text/plain, Size: 763 bytes --]

>>>>> "DU" == Daiki Ueno <ueno@unixuser.org> writes:

   DU> Hello,
   DU> Let me announce the initial release of EasyPG, yet another GnuPG
   DU> interface for Emacs.  It consists of two parts:

Hello 

Thanks for that. I tried for a long time to implement the feature to
encrypt/decrypt files in dired mode. Thanks again!

There are 2 problems:

    -  The README file  talks about (or M-x epg-dired-do-encrypt),
       however I only have (M-x epa-dired-do-encrypt) so I think this
       is a typo.

    -  More seriously how to include epg into gnus. According to the
       webpage, this is done by
       (setq pgg-scheme 'epg)
       however when I then want to sign a message, I obtain an error
       which I attach.

What is the problem?

Uwe Brauer 


[-- Attachment #2: epg-bug --]
[-- Type: application/octet-stream, Size: 1536 bytes --]

Debugger entered--Lisp error: (file-error "Cannot open load file" "pgg-epg")
  load-internal("pgg-epg" nil t nil nil nil)
  load("pgg-epg" nil t nil)
  apply(load ("pgg-epg" nil t nil))
  dired-handler-fn(load "pgg-epg" nil t nil)
  load-internal("pgg-epg" nil t nil nil nil)
  load("pgg-epg" nil t nil)
  si:require(pgg-epg nil)
  require(pgg-epg)
  pgg-invoke("sign-region" epg 1 2 nil nil)
  pgg-sign-region(1 2)
  mml2015-pgg-sign((part (sign . "pgpmime") (tag-location . 453) (contents . "")))
  mml2015-sign((part (sign . "pgpmime") (tag-location . 453) (contents . "")))
  mml-pgpmime-sign-buffer((part (sign . "pgpmime") (tag-location . 453) (contents . "")))
  mml-generate-mime-1((part (sign . "pgpmime") (tag-location . 453) (contents . "")))
  mml-generate-mime()
  message-encode-message-body()
  message-send-mail(nil)
  message-send-via-mail(nil)
  message-send(nil)
  message-send-and-exit(nil)
  call-interactively(message-send-and-exit)
  recursive-edit()
  byte-code("..." [buffer-read-only noninteractive debugger-buffer middlestart debugger-args debugger-batch-max-lines pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output] 3)
  debug(error (error "Object type has no properties" (lambda nil find-file "~/tex/publicationen/technion-karmiel/add/moser-broken.tex")))
  first-unscrollable-command-p()
  scroll-up(nil)
  scroll-up-command(nil)
  call-interactively(scroll-up-command)

  parent reply	other threads:[~2006-05-10 13:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-29  0:09 Daiki Ueno
2006-04-29  3:26 ` Steve Youngs
2006-04-30 10:42   ` Lars Magne Ingebrigtsen
2006-05-10 13:14 ` Uwe Brauer [this message]
2006-05-11  1:45   ` Daiki Ueno
2006-05-11  6:29     ` Elias Oltmanns
2006-05-11  7:06       ` Daiki Ueno
2006-05-11  8:03         ` Elias Oltmanns
2006-05-11  8:00     ` Simon Josefsson
2006-05-11 14:48     ` Uwe Brauer
2006-05-12  4:23       ` Daiki Ueno

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=8764keqax3.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    /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.
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 NNTP newsgroup(s).