From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.bugs Subject: bug#15648: 24.2.50; gnutls SSL connection to IMAP server causes emacs to crash completely Date: Thu, 24 Oct 2013 20:59:06 -0400 Message-ID: References: <21089.32240.198931.971000@consult.pretender> <87y55kjayp.fsf_-_@flea.lifelogs.com> <21096.1667.116936.254737@consult.pretender> <83eh7bj1yq.fsf@gnu.org> <87ppqvke5u.fsf@flea.lifelogs.com> <87fvrun1pw.fsf@flea.lifelogs.com> <21093.32992.278229.646703@consult.pretender> <877gd5mo5x.fsf@flea.lifelogs.com> <21094.39055.449629.706850@consult.pretender> <21094.40085.664080.69561@consult.pretender> <21094.52645.645440.977584@consult.pretender> <21094.64459.131668.849138@consult.pretender> <21095.19949.639350.970770@consult.pretender> <21096.24492.292723.589004@consult.pretender> <87eh7bj5no.fsf_-_@flea.lifelogs.com> <21097.10816.221279.461499@consult.pretender> <21097.27136.910137.181740@consult.pretender> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1382662822 20462 80.91.229.3 (25 Oct 2013 01:00:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Oct 2013 01:00:22 +0000 (UTC) Cc: Ted Zlatanov , 15648@debbugs.gnu.org To: Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Oct 25 03:00:25 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VZVlH-0007DU-7m for geb-bug-gnu-emacs@m.gmane.org; Fri, 25 Oct 2013 03:00:23 +0200 Original-Received: from localhost ([::1]:56888 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZVlG-0005iS-Uo for geb-bug-gnu-emacs@m.gmane.org; Thu, 24 Oct 2013 21:00:22 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48243) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZVl6-0005h5-BK for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2013 21:00:19 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VZVky-0002ng-UX for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2013 21:00:12 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56404) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VZVky-0002mF-Ra for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2013 21:00:04 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VZVky-0000Pj-1r for bug-gnu-emacs@gnu.org; Thu, 24 Oct 2013 21:00:04 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Stefan Monnier Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 25 Oct 2013 01:00:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15648 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15648-submit@debbugs.gnu.org id=B15648.13826627681517 (code B ref 15648); Fri, 25 Oct 2013 01:00:03 +0000 Original-Received: (at 15648) by debbugs.gnu.org; 25 Oct 2013 00:59:28 +0000 Original-Received: from localhost ([127.0.0.1]:42190 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VZVkN-0000OO-An for submit@debbugs.gnu.org; Thu, 24 Oct 2013 20:59:27 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:42013) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VZVkK-0000O9-Ik for 15648@debbugs.gnu.org; Thu, 24 Oct 2013 20:59:25 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EABK/CFFFxIYv/2dsb2JhbABEuzWDWRdzgh4BAQQBViMFCws0EhQYDSSIHgbBLY1hgykDpHqBXoMT X-IPAS-Result: Av8EABK/CFFFxIYv/2dsb2JhbABEuzWDWRdzgh4BAQQBViMFCws0EhQYDSSIHgbBLY1hgykDpHqBXoMT X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="36299260" Original-Received: from 69-196-134-47.dsl.teksavvy.com (HELO ceviche.home) ([69.196.134.47]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 24 Oct 2013 20:59:16 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 6B15D660A2; Thu, 24 Oct 2013 20:59:06 -0400 (EDT) In-Reply-To: <21097.27136.910137.181740@consult.pretender> (emacs@kosowsky.org's message of "Thu, 24 Oct 2013 14:42:08 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:79618 Archived-At: >> Good point. The problem is the use of file-exists-p (which tests if >> Elisp code can reach this file) instead of another function along the >> lines of file-accessible-directory-p, which checks whether the file name >> is reachable to C-level system primitives. > Note that the predicate "file-accessible-directory-p" is also one of I didn't mean to say that file-accessible-directory-p is the right answer. Only that something *like it* should be used. I.e. a function specifically meant to give you some idea about whether that file is known to the OS primitives. >> expand-file-name is not the right function, even if in some cases it may >> happen to help. > Why isn't it the right one? > The function name describes it as "Convert filename NAME to absolute, > and *canonicalize* it." (emphasis added) You give too much meaning to "canonicalize": it does not imply that it's the name used outside of Emacs. It just means to try and remove things like "/../foo/". So the output will be a "somewhat canonicalized Elisp file name". Not necessarily an "OS-level file name". `cygwin-mount' happens to use expand-file-name to convert the name from one form to another, basically for pragmatic reasons: that's what exists and it is called often enough that it works OK in practice. > It seems that any proper Magic File handler should (by definition) > hook into expand-file-name to provide an absolute canonicalized path, Think of a magic file handler that provides access to members of a zip or tar archive or think of file name handlers for Tramp. These "canonical" file names still won't help you. > Alternatively, how else would you recommend generally and portably > canonicalizing a Magic file path? You'd first have to define what kind of "canonicalizing" you want to do. I think in the present case what you want is to turn an Elisp file name into a file name understood by OS-level primitives (or nil if that can't be done). We don't have such a function right now. So my recommendation is to add such a function. Stefan