unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: bug: epg send unencrypted data in trash
Date: Fri, 11 Feb 2011 19:23:06 -0500	[thread overview]
Message-ID: <87mxm285jp.fsf@stupidchicken.com> (raw)
In-Reply-To: <87oc6iw75t.fsf@lifelogs.com> (Ted Zlatanov's message of "Fri, 11 Feb 2011 16:14:22 -0600")

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Fri, 11 Feb 2011 22:05:09 +0100 Thierry Volpiatto
> <thierry.volpiatto@gmail.com> wrote:
>
> TV> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> According to the docs for `delete-file' it shouldn't matter what
>>> `delete-by-moving-to-trash' says because this is called
>>> non-interactively (TRASH is nil when delete-file is called
>>> non-interactively).  Or is this funcall interactive somehow?
> TV> I don't know, but actually without delete-by-moving-to-trash let-bound
> TV> to nil, non--encrypted data goes to trash.
>
> I think this is because in the C source (fileio.c) TRASH is set to
> "(null current-prefix-arg)" which is not equivalent to
> `called-interactively-p' AFAIK.  IOW I think your fix is masking the
> underlying problem.  But I don't know the C source so well so I could be
> misunderstanding things.  Perhaps Chong Yidong, who created revision
> 100462 and introduced the TRASH parameter, can check it.

I think TV is using the emacs-23 branch, where the TRASH parameter is
not present.  I've changed EPA and EPG to bind delete-by-moving-to-trash
to nil there.  No fix is necessary for the trunk, IIUC.



  reply	other threads:[~2011-02-12  0:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  7:29 bug: epg send unencrypted data in trash Thierry Volpiatto
2011-02-11 18:16 ` Thierry Volpiatto
2011-02-11 19:54   ` Ted Zlatanov
2011-02-11 21:05     ` Thierry Volpiatto
2011-02-11 22:14       ` Ted Zlatanov
2011-02-12  0:23         ` Chong Yidong [this message]
2011-02-12  7:08           ` Thierry Volpiatto
2011-02-12 12:56           ` Ted Zlatanov
2011-02-12 18:49             ` Chong Yidong
2011-02-12 19:06               ` Ted Zlatanov

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=87mxm285jp.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.com \
    /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).