From: Ted Zlatanov <tzz@lifelogs.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15866@debbugs.gnu.org, emacs@kosowsky.org
Subject: bug#15866: Gnutls elisp code doesn't properly check for file existence
Date: Sat, 16 Nov 2013 18:34:46 -0500 [thread overview]
Message-ID: <87y54ngbu1.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <jwv7gcdcs2r.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 12 Nov 2013 15:02:40 -0500")
On Tue, 12 Nov 2013 15:02:40 -0500 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> So I think we should do ii], but not i].
SM> Please go ahead, yes.
>> Btw, I think many Emacs packages don't make sense with remote files,
>> so they should also ignore file handlers. IOW, this is not specific
>> to gnutls.el.
SM> Not sure how widespread this problem is. At least the gnutls case is
SM> rather special since most other C calls that manipulate files are
SM> wrapped with a magic file handler.
I am also thinking now about the FFI work (yes, it's somewhere on my
TODO list) and how these issues will be handled there. It seems that
the FFI glue may have to tag filenames distinctly from plain strings and
may even have some file existence checks and hooks.
Ted
next prev parent reply other threads:[~2013-11-16 23:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 0:20 bug#15866: Gnutls elisp code doesn't properly check for file existence emacs
2013-11-12 17:48 ` Eli Zaretskii
2013-11-12 18:12 ` emacs
2013-11-12 19:41 ` Ted Zlatanov
2013-11-12 19:52 ` Michael Albinus
2013-11-12 20:27 ` Stefan Monnier
2014-12-07 20:17 ` Lars Magne Ingebrigtsen
2014-12-07 21:08 ` Eli Zaretskii
2014-12-07 21:15 ` Lars Magne Ingebrigtsen
2014-12-08 3:32 ` Eli Zaretskii
2014-12-08 7:40 ` Michael Albinus
2014-12-08 18:14 ` Lars Magne Ingebrigtsen
2014-12-08 7:34 ` Michael Albinus
2013-11-12 20:02 ` Stefan Monnier
2013-11-16 23:34 ` Ted Zlatanov [this message]
2013-11-17 1:51 ` Stefan Monnier
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=87y54ngbu1.fsf@flea.lifelogs.com \
--to=tzz@lifelogs.com \
--cc=15866@debbugs.gnu.org \
--cc=emacs@kosowsky.org \
--cc=monnier@iro.umontreal.ca \
/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.