[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#49283: [PATCH] 27.2; `(call-process "program" null-device ...)' fail
bug#49283: [PATCH] 27.2; `(call-process "program" null-device ...)' fails over TRAMP from local MS Windows
Sat, 03 Jul 2021 10:02:32 +0300
> From: Jim Porter <email@example.com>
> Date: Fri, 2 Jul 2021 11:47:12 -0700
> Cc: Michael Albinus <firstname.lastname@example.org>, Lars Ingebrigtsen
> <email@example.com>, firstname.lastname@example.org
> > expand-file-name is not a problem, it can deal with encoded file
> > names. The problem is the calls to remove_slash_colon and
> > report_file_error: they should receive file names in their internal
> > representation.
> Right, I was just worried that if I relied on
> `encode_current_directory' returning an encoded path,
> `expand-file-name' might sometimes return an encoded path (e.g. if
> INFILE is a simple relative path like "foo") and sometimes an
> unencoded path (e.g. if INFILE is an absolute path). I might be wrong
> though, since I didn't look closely at the implementation...
> > How about adding a 'bool' argument to encode_current_directory, so
> > that the caller could control whether or not it encodes the directory
> > file name? Then you could in this case tell encode_current_directory
> > not to encode the directory file name.
> Ok, I did that (and renamed it to `get_current_directory' since it
> doesn't always encode anymore). How does the attached patch look?