Re: bug: epg send unencrypted data in trash

[Chong Yidong]

Ted Zlatanov <address@hidden> writes:

> How does TRASH get set based on called-interactively-p, as claimed by
> the docstring?
>
> DEFUN ("delete-file", Fdelete_file, Sdelete_file, 1, 2,
>        "(list (read-file-name \
>                 (if (and delete-by-moving-to-trash (null current-prefix-arg)) 
> \
>                     \"Move file to trash: \" \"Delete file: \") \
>                 nil default-directory (confirm-nonexistent-file-or-buffer)) \
>               (null current-prefix-arg))",
>        doc: /* Delete file named FILENAME.  If it is a symlink, remove the 
> symlink.
> If file has multiple names, it continues to exist with the other names.
> TRASH non-nil means to trash the file instead of deleting, provided
> `delete-by-moving-to-trash' is non-nil.
>
> When called interactively, TRASH is t if no prefix argument is given.
> With a prefix argument, TRASH is nil.  */)
>
> I don't see anything in the body of the function to set TRASH, either.
> Is it claimed because we assume `current-prefix-arg' is always null
> non-interactively and `universal-arg' is always called interactively?

Er, I'm not sure I understand what the confusion is about.  The above
interactive spec is run if and only if delete-file is called
interactively.  That's what interactive specs do---provide the arguments
for an interactive call.