From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15866@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>,
emacs@kosowsky.org
Subject: bug#15866: Gnutls elisp code doesn't properly check for file existence
Date: Sun, 07 Dec 2014 21:17:21 +0100 [thread overview]
Message-ID: <m3ppbvfc4u.fsf@stories.gnus.org> (raw)
In-Reply-To: <jwvvbzxbc65.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 12 Nov 2013 15:27:25 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Whereas in gnutls.el the issue is for the *code* to check that the
> libgnutls C code (which will not have access to the file name handlers)
> will be able to use the file name provided by the user.
Wouldn't a solution here be to introduce a variable like
`inhibit-file-handlers' that would really inhibit all Lisp-level file
handlers? Doesn't Emacs have that already? Hm...
`inhibit-file-name-handlers' doesn't quite seem to do the trick, I
guess?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2014-12-07 20:17 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 [this message]
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
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
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=m3ppbvfc4u.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=15866@debbugs.gnu.org \
--cc=emacs@kosowsky.org \
--cc=michael.albinus@gmx.de \
--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 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).