From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Christoph Michelbach Newsgroups: gmane.emacs.bugs Subject: bug#31272: 25.3; Directory with weird name cannot be opened via SFTP Date: Thu, 26 Apr 2018 21:39:14 +0200 Message-ID: <1524771554.24497.9.camel@gmail.com> References: <1524738365.3814.0.camel@gmail.com> <83fu3hvm0m.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1524771488 9595 195.159.176.226 (26 Apr 2018 19:38:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 26 Apr 2018 19:38:08 +0000 (UTC) Cc: 31272@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu Apr 26 21:38:03 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fBmiP-0002NP-3k for geb-bug-gnu-emacs@m.gmane.org; Thu, 26 Apr 2018 21:38:01 +0200 Original-Received: from localhost ([::1]:44195 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fBmkW-0003YW-2c for geb-bug-gnu-emacs@m.gmane.org; Thu, 26 Apr 2018 15:40:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44346) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fBmkQ-0003Xs-4e for bug-gnu-emacs@gnu.org; Thu, 26 Apr 2018 15:40:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fBmkN-0001Fy-1M for bug-gnu-emacs@gnu.org; Thu, 26 Apr 2018 15:40:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:32803) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fBmkM-0001FW-UT for bug-gnu-emacs@gnu.org; Thu, 26 Apr 2018 15:40:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fBmkM-0007Tt-HQ for bug-gnu-emacs@gnu.org; Thu, 26 Apr 2018 15:40:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Christoph Michelbach Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 26 Apr 2018 19:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31272 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31272-submit@debbugs.gnu.org id=B31272.152477156328709 (code B ref 31272); Thu, 26 Apr 2018 19:40:02 +0000 Original-Received: (at 31272) by debbugs.gnu.org; 26 Apr 2018 19:39:23 +0000 Original-Received: from localhost ([127.0.0.1]:40700 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fBmji-0007Sz-Ok for submit@debbugs.gnu.org; Thu, 26 Apr 2018 15:39:22 -0400 Original-Received: from mail-wr0-f177.google.com ([209.85.128.177]:38216) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fBmjh-0007Sm-D3 for 31272@debbugs.gnu.org; Thu, 26 Apr 2018 15:39:21 -0400 Original-Received: by mail-wr0-f177.google.com with SMTP id h3-v6so57922034wrh.5 for <31272@debbugs.gnu.org>; Thu, 26 Apr 2018 12:39:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=pQ4CSwWptBK10Pk/BDIDsmsawRwAGKFp/pvN+aG1E70=; b=FvFcx+5YE/kS/9AKSQTNHPqu2C+gKWsLpDjBpcCi1ttEZSMk2DoVXKUY11qJQpOCUw yqMua81d7CRDXrT+AZoZ2aHYt9s1pFnqHC5SKHCVDzUOQI5sG2i64mGfhzLkcBZ6SSAg exJQU0cEJicIIZqxSX+4AdWlRqkeOuG5HSpq6KRlqefSW9kp3ij63Dx4UCB1k2C8PCMy nYOqzppbEXf7ynNANpFPg10vHxecBqQnH1yeWiuvEVgZtNvmh/ZPhosTej6igP6W5VWI 89TJT8nKqy6msV+7d4lltLgWFvyjXcZwg+y3gpfmJ8YpqqhExDx1ru/7Ao/hz+gMMF42 w7UA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=pQ4CSwWptBK10Pk/BDIDsmsawRwAGKFp/pvN+aG1E70=; b=NysygFLxricgoa3xuugBsnSuzCE3l/dJMZ5kDH6mf4iUv8/iKKSafuFOGlqoTa9rC+ 90VQSUUdltUU+g+3TAzTpOzx76e2FYlAR448srrfhQ0vT0a8h0OxD7NaO64x2LD4fpom oGPX/Lf69NMOvSGTgExsTHDUCQt1lO0e2D0eTDUvJf1lIIdfD+PSHor2g35KLTb5Yl99 2Vr8FUbKRS3xfKkDwEHOzWMfZyVsMVDJJuiHepOYErIN4gujORN5vFo5NJ5DXeRYSGGY 516rvoVF+xxcf3Z67WpnHTyx1I5qopsMQ1NJwH+TCbHS7+4kE3crxtEM8G5ao+8rSJHd eXww== X-Gm-Message-State: ALQs6tCLpjekSAvvzev9jpg9fT/OxekZOG9PIHUvwot9aSsoGGJwfMep L18JhY0bADLH0wIEq8pWHWs= X-Google-Smtp-Source: AIpwx4+TlyjIhVXW4Vi9Zbz59vIOCslCQwQeg7LxfT6iVg27Q8EmwhKyM0LGzIJWAObB63PTgUUreg== X-Received: by 2002:adf:b0c1:: with SMTP id j1-v6mr27427134wra.3.1524771555604; Thu, 26 Apr 2018 12:39:15 -0700 (PDT) Original-Received: from ?IPv6:2a02:8071:3185:fe00:d87c:eb93:1433:d685? ([2a02:8071:3185:fe00:d87c:eb93:1433:d685]) by smtp.googlemail.com with ESMTPSA id i30-v6sm37689691wra.38.2018.04.26.12.39.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 12:39:15 -0700 (PDT) In-Reply-To: <83fu3hvm0m.fsf@gnu.org> X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.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" Xref: news.gmane.org gmane.emacs.bugs:145770 Archived-At: On Thu, 2018-04-26 at 21:51 +0300, Eli Zaretskii wrote: > Can you try the release candidate of Emacs 26.1 and see if the problem > is still there?  RC1 is available from alpha.gnu.org. Thanks for providing the link. In 26.1 RC1, the problem still exists. However, it's different from how I described it at first. I only discovered this after running my installed version of Emacs with -Q after I checked whether the bug exists in 26.1 RC1 for which I used -Q. Instead of opening an empty buffer, both Emacs 26.1 RC1 and the version I use daily (25.3.2) by default print "File no longer exists; type 'g' to update Dired buffer" to the mini buffer. Apparently, something about the configuration I use changes the behavior to what I described in my initial bug report. The directory still showed up in dired after pressing 'g'. It can be accessed without problems via other applications (e.g. via Nautilus).