unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Evan MacTaggart <evan.mactaggart@gmail.com>
Cc: 55855@debbugs.gnu.org
Subject: bug#55855: "Invalid file name" error with tramp-smb filename check
Date: Thu, 09 Jun 2022 14:51:00 +0200	[thread overview]
Message-ID: <875ylahuff.fsf@gmx.de> (raw)
In-Reply-To: <CAGLo8Wy1dW7SYBJu1dw3q_5UbQ-m6jjNS1jfYMvFqWRi-KsZhg@mail.gmail.com> (Evan MacTaggart's message of "Wed, 8 Jun 2022 11:55:21 -0600")

Evan MacTaggart <evan.mactaggart@gmail.com> writes:

Hi Evan,

> So after tramping into an SMB file server, I'm trying to find-file
> into a directory whose name is as so: "/smb:username%DOMAIN@fsname:/my
> path/1234. Some Name".  The problem with this filename is that the
> filename contains a ". ", which throws a tramp-error. And as per the
> code comment is "not supported", however it seems as though, at least
> for the server I'm connected to, this is supported.

Thanks for the report and the analysis!

> I'm certainly not the most well versed on the samba protocol, but
> perhaps look into this and see if the once invalid file names are now
> valid. Or perhaps describe specifically what is not supported about
> this filename. I'd imagine/assume this is due to a newer SMB version
> than what the following code was initially written for.

I've digged into this, and you are right: There is no SMB protocol
problem. There is an error in tramp-smb-handle-write-region, which
didn't quote tmpfile when sending "put ...". Since it wasn't detected
earlier, it was regarded as problem of SMB, resulting in the wrong
check.

I've fixed this now, and I've also adapted the check in
tramp-smb-get-localname. Pushed to the emacs-28 git branch. Will appear
with Emacs 28.2 as well as with the next GNU ELPA Tramp release (2.5.3
or 2.6.0, not decided yet).

> Thanks in advance, and let me know if there's anything else you need
> from me.

You could test with the emacs-28 git branch. For the master branch, I
haven't pushed a fix yet, because I'd like to rework it for being more
robust. If you don't use a git clone, you can consult the patch at
<https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-28&id=3fd08543782d0d417eaa2dda0727ea16b3271710>. Does
it work for you as well?

> Cheers,
> Evan MacTaggart

Best regards, Michael.





  reply	other threads:[~2022-06-09 12:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 17:55 bug#55855: "Invalid file name" error with tramp-smb filename check Evan MacTaggart
2022-06-09 12:51 ` Michael Albinus [this message]
2022-06-09 16:24   ` Evan MacTaggart
2022-06-09 16:48     ` 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

  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=875ylahuff.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=55855@debbugs.gnu.org \
    --cc=evan.mactaggart@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 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).