all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Michelbach <michelbach94@gmail.com>
Cc: 31272@debbugs.gnu.org
Subject: bug#31272: 25.3; Directory with weird name cannot be opened via SFTP
Date: Thu, 26 Apr 2018 21:51:53 +0300	[thread overview]
Message-ID: <83fu3hvm0m.fsf@gnu.org> (raw)
In-Reply-To: <1524738365.3814.0.camel@gmail.com> (message from Christoph Michelbach on Thu, 26 Apr 2018 12:26:05 +0200)

> From: Christoph Michelbach <michelbach94@gmail.com>
> Date: Thu, 26 Apr 2018 12:26:05 +0200
> 
> When I try to open a directory with some weird character in its name on
> an SSH resource via dired, Emacs does not show the contents of the
> directory but instead opens a buffer for a new (empty) text file.
> 
> One of these directory names is "šbung" (without the quotes). Because
> this weird character might not make it to you via email: The name is
> "\232bung" or "C2 9A 62 75 6E 67" (in hexadecimal).
> 
> Opening a directory named like this via dired is no problem when its on
> my local hard drive. On an SFTP resource, the problem always
> occurs. It's not inherent to the directory where I discovered the
> problem but inherent in the directory's name.

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.





  reply	other threads:[~2018-04-26 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-26 10:26 bug#31272: 25.3; Directory with weird name cannot be opened via SFTP Christoph Michelbach
2018-04-26 18:51 ` Eli Zaretskii [this message]
2018-04-26 19:39   ` Christoph Michelbach
2018-04-27  6:25     ` Eli Zaretskii
2018-04-27  7:22       ` Michael Albinus
2018-05-06 12:52         ` Michael Albinus
2018-05-06 14:19           ` Christoph Michelbach
2018-05-06 14:43             ` Michael Albinus

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=83fu3hvm0m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31272@debbugs.gnu.org \
    --cc=michelbach94@gmail.com \
    /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.