unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Winkler <winkler@gnu.org>
To: 8792@debbugs.gnu.org
Subject: bug#8792: 23.3; EasyPG: do not create empty buffers if file cannot be read
Date: Thu, 02 Jun 2011 19:13:36 -0500	[thread overview]
Message-ID: <87aadzvkjz.fsf@lukas.physics.niu.edu> (raw)

If a gpg-encrypted file cannot be read for whatever reason (see,
e.g., bug#8791) one gets the error message

  File exists, but cannot be read

and just an empty buffer. This empty buffer can be dangerous because
emacs believes it is really visiting the file. Say, if this empty
buffer gets modified and saved automatically, this will just
override the original file. I suggest that EasyPG should be more
cautious here (or: provide a means to be more cautious if desired).


In GNU Emacs 23.3.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.12.9)
 of 2011-06-02 on lukas

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: C
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: en_GB.utf8
  value of $LANG: en_US.ISO-8859-15
  value of $XMODIFIERS: nil
  locale-coding-system: iso-latin-9-unix
  default enable-multibyte-characters: t






             reply	other threads:[~2011-06-03  0:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03  0:13 Roland Winkler [this message]
2011-06-03  3:40 ` bug#8792: 23.3; EasyPG: do not create empty buffers if file cannot be read Daiki Ueno
2011-06-04  2:12   ` Roland Winkler

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87aadzvkjz.fsf@lukas.physics.niu.edu \
    --to=winkler@gnu.org \
    --cc=8792@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).