all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daiki Ueno <ueno@unixuser.org>
To: "Андрей Парамонов" <cmr.pent@gmail.com>
Cc: emacs-pretest-bug@gnu.org, rfrancoise@debian.org,
	3829@emacsbugs.donarmstrong.com
Subject: bug#3829: 23.0.96; Cannot read gpg file
Date: Mon, 13 Jul 2009 06:44:28 +0900	[thread overview]
Message-ID: <f24aaa9c-2c39-497f-be34-971403b7b804@broken.deisui.org> (raw)
In-Reply-To: <5f0660120907120547o33e6480an6eab53a9a79b4a2e@mail.gmail.com> ("Андрей Парамонов"'s message of "Sun, 12 Jul 2009 16:47:28 +0400")

>>>>> In <5f0660120907120547o33e6480an6eab53a9a79b4a2e@mail.gmail.com> 
>>>>>	Андрей Парамонов <cmr.pent@gmail.com> wrote:
> To reproduce:

> 0) emacs -Q

> 1) C-x C-f attached file

> 2) Emacs says:
> File exists, but cannot be read

That is because the file contains only public keys instead of encrypted
content.  Handling such a file in a fancy way would be a feature request
after the release.

How about M-x find-file-literally if you just want to see the binary
content?

Regards,
-- 
Daiki Ueno





  reply	other threads:[~2009-07-12 21:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 12:47 bug#3829: 23.0.96; Cannot read gpg file Андрей Парамонов
2009-07-12 21:44 ` Daiki Ueno [this message]
2009-07-13  7:01   ` Андрей Парамонов
2009-07-14  3:06     ` Daiki Ueno
2009-07-14  7:17       ` Glenn Morris
2009-07-14  7:25         ` Processed: " Emacs bug Tracking System
2009-07-14 10:51       ` Андрей Парамонов
2009-07-14 19:59         ` Stefan Monnier
2019-08-30 11:19 ` Lars Ingebrigtsen
2020-08-04 19:27   ` Lars Ingebrigtsen
2020-08-04 19:43     ` Lars Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2009-07-12 17:34 Chong Yidong

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=f24aaa9c-2c39-497f-be34-971403b7b804@broken.deisui.org \
    --to=ueno@unixuser.org \
    --cc=3829@emacsbugs.donarmstrong.com \
    --cc=cmr.pent@gmail.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=rfrancoise@debian.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.