public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Charles Curley <ccurley@wyoming.com>
To: John Mamer <jmamer@anderson.ucla.edu>
Cc: gnu-win32@cygnus.com
Subject: Re: upper/lower case question
Date: Mon, 13 Oct 1997 19:00:00 -0000	[thread overview]
Message-ID: <3.0.2.32.19971013172034.00907da0@mailhost.wyoming.com> (raw)
In-Reply-To: <Pine.HPP.3.95q.971012211842.22762A-100000@risc.anderson.ucla.edu>

At 09:25 PM 10/12/97 -0700, John Mamer wrote:
>Hi!
>  Another newbie question:  I have a bunch of files,
>originally written under UNIX, that have arrived at my
>gnu-win32 directory via DOS (am running on Windows NT
>4.0-sp3).  The problem is that in the process the file names
>have all been translated to upper case.  I tried the obvious
>thing: 
>
>cp FILE.C file.c
>
>but it didn't work.  I wound up reading each file into
>emacs, and then copying it into a new directory using the
>lower case name.  This worked, but it seems, somehow,
>inelegant.  
>
>I know that this is the result of a DOS/UNIX
>incompatibility, and not strictly speaking gnu-win32's
>fault, but is there a neater way to do this? (I anticipate
>having to do this in the future).
>thanks

Quick & dirty (from BASH):

mv FILE.C foo.c; mv foo.c file.c

You can probably put together a quick alias to do that in one command.

A little more development would be a perl script to do the same for the
entire directory or tree.


		-- C^2

Looking for fine software and/or web pages?
http://web.idirect.com/~ccurley
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  reply	other threads:[~1997-10-13 19:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-12 21:25 John Mamer
1997-10-13 19:00 ` Charles Curley [this message]
1997-10-15  7:51   ` Lassi A. Tuura
1997-10-13  1:45 Sergey Okhapkin
1997-10-13  5:07 Earnie Boyd
1997-10-13  5:16 Earnie Boyd
1997-10-13 10:17 Earnie Boyd

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=3.0.2.32.19971013172034.00907da0@mailhost.wyoming.com \
    --to=ccurley@wyoming.com \
    --cc=gnu-win32@cygnus.com \
    --cc=jmamer@anderson.ucla.edu \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).