Re: filename ends with a space, cannot use the --targets option.
Branko Čibej <[email protected]> Tue, 17 Jun 2025 18:26:10 +0200
| Newsgroups | gmane.comp.version-control.subversion.user |
|---|---|
| Organization | The Apache Software Foundation |
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--------------bmNzhfN4qS500EldQC9obfXX
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
On 17. 6. 25 09:45, Daniel Sahlberg wrote:
> I personally think it should be possible to specify any legal
> filenames in the --targets file. Files with preceding or trailing
> whitespace is possible under Linux. It seems NTFS also allow this but
> the Windows shell trim both ends, cmd.exe allow creating files with
> preceding whitespace. I haven't checked macOS.
I forgot about this example:
brane@zulu:~/src/bs$ touch "$(echo fileXname | tr 'X' '\n')"
brane@zulu:~/src/bs$ /bin/ls -wl
total 0
-rw-r--r-- 1 brane staff 0 Jun 17 18:09 file
name
You were saying, about "legal" filenames? Will you support this in the
--targets file as well? It is, after all, no more an exception than the
trailing spaces.
And, finally:
brane@zulu:~/src/bs$ touch "$(echo 'fileX[1;31mnameX[0;m' | tr 'X' '\033')"
brane@zulu:~/src/bs$ /bin/ls -wl
total 0
-rw-r--r-- 1 brane staff 0 Jun 17 18:19 filename
This one doesn't even have any hidden whitespace. And we do already
support this in --targets. :)
-- Brane
--------------bmNzhfN4qS500EldQC9obfXX
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 17. 6. 25 09:45, Daniel Sahlberg
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMHy98OxB5ek9GsOcV7QXNUi=CAgQymD8d1MfAtTprtJcvX4wA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">
<div dir="ltr">I personally think it should be
possible to specify any legal filenames in the
--targets file. Files with preceding or trailing
whitespace is possible under Linux. It seems NTFS
also allow this but the Windows shell trim both
ends, cmd.exe allow creating files with preceding
whitespace. I haven't checked macOS.</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I forgot about this example:<br>
<br>
<blockquote>
<pre><font color="#008e00">brane@zulu</font>:<font color="#0432ff">~/src/bs</font>$ touch "$(echo fileXname | tr 'X' '\n')"
<font color="#008e00">brane@zulu</font>:<font color="#0432ff">~/src/bs</font>$ /bin/ls -wl
total 0
-rw-r--r-- 1 brane staff 0 Jun 17 18:09 file
name
</pre>
</blockquote>
<br>
You were saying, about "legal" filenames? Will you support this in
the <font face="monospace">--targets</font> file as well? It is,
after all, no more an exception than the trailing spaces.<br>
<br>
And, finally:<br>
<br>
<blockquote>
<pre><font color="#008e00">brane@zulu</font>:<font color="#0432ff">~/src/bs</font>$ touch "$(echo 'fileX[1;31mnameX[0;m' | tr 'X' '\033')"
<font color="#008e00">brane@zulu</font>:<font color="#0432ff">~/src/bs</font>$ /bin/ls -wl
total 0
-rw-r--r-- 1 brane staff 0 Jun 17 18:19 file<font color="#ff2600">name</font>
</pre>
</blockquote>
<br>
This one doesn't even have any hidden whitespace. And we do already
support this in <font face="monospace">--targets</font>. :)<br>
<br>
-- Brane<br>
<br>
</body>
</html>
--------------bmNzhfN4qS500EldQC9obfXX--