From: "Alejandro Néstor Vargas" <anv@xnetcuyo.com.ar>
To: Bart Oldeman <bartoldeman@users.sourceforge.net>
Cc: linux-msdos@vger.kernel.org
Subject: uppercase filenames: the problem is in rename
Date: Wed, 13 Aug 2003 14:25:49 -0300 [thread overview]
Message-ID: <oprtutdbweg5addp@mail.xnetcuyo.com.ar> (raw)
In-Reply-To: <Pine.LNX.4.44.0308131152530.22341-100000@pg5.enm.bris.ac.uk>
On Wed, 13 Aug 2003 12:05:46 +0100 (BST), Bart Oldeman
<bartoldeman@users.sourceforge.net> wrote:
> it's most likely a bug that was introduced in 1.1.5.5. I will
> investigate and post a fix later.
I was creating a test program and discovered that the problem is when you
rename a file. The test programs are in
http://www.xnetcuyo.com.ar/linux/test_dosemu/lower.pas
http://www.xnetcuyo.com.ar/linux/test_dosemu/lower.exe
It creates a lowercase file (lower1.txt) correctly. Then it renames it as
lower2.txt and the result is LOWER2.TXT.
This is the test program. You can download the compiled exe if you want.
var f:text;
begin
assign(f,'lower1.txt');
rewrite(f);
writeln(f,'lowercase');
Writeln('The file lower1.txt has bin created. This is lowercase in the unix
filesystem.');
Writeln('Check this and press enter to continue');
readln;
rename(f,'lower2.txt');
Writeln('lower1.txt renamed as lower2.txt. This should be lowercase but
isn'#39't.');
close(f);
end.
--
Alejandro Néstor Vargas
Departamento de Desarrollo
X Net Cuyo S.A.
e-mail: anv@xnetcuyo.com.ar
jabber: anv@xnetcuyo.com.ar
next prev parent reply other threads:[~2003-08-13 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 23:43 uppercase filenames Alejandro Néstor Vargas
2003-08-13 10:51 ` Ryan Underwood
2003-08-13 11:28 ` Bart Oldeman
2003-08-13 11:05 ` Bart Oldeman
2003-08-13 15:31 ` Alejandro Néstor Vargas
2003-08-13 17:25 ` Alejandro Néstor Vargas [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-14 9:05 uppercase filenames: the problem is in rename Bart Oldeman
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=oprtutdbweg5addp@mail.xnetcuyo.com.ar \
--to=anv@xnetcuyo.com.ar \
--cc=bartoldeman@users.sourceforge.net \
--cc=linux-msdos@vger.kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox