Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Shankar Unni" To: "'Yu Wang'" , Subject: RE: Question about Running GNU Utilities on Windows XP Date: Mon, 7 Oct 2002 14:14:32 -0700 Organization: CotageSoft, Inc. Message-ID: <000f01c26e46$87faec90$6a0aa8c0@HQSHANKAR> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal In-Reply-To: <20021007210147.38713.qmail@web13114.mail.yahoo.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g97LF6x21340 Yu Wang writes: > Did you met any problem when you use tail.exe on a > file with long filename. > The command: tail paratestdatalog.out Works. > The command: tail paratestdatalog.gold Works. > The command: tail parate~1.gold Does not work. If part of the filename is using the "short notation", the other part shouldn't. The file is either a short name, or a long name. You can't pick and choose a short prefix and a long suffix. > The command: tail parate~1.out Works, because "out" is the same in both short and long forms. Here are my attempts with "paratestdatalog.gold": bash-2.05b$ echo foo > paratestdatalog.gold bash-2.05b$ tail paratestdatalog.gold foo bash-2.05b$ tail parate~1.gol foo bash-2.05b$ tail parate~1.gold tail: parate~1.gold: No such file or directory bash-2.05b$ tail parate~1.* tail: parate~1.*: No such file or directory The last one is because I guess the cygwin layer does not attempt to treat a filename as a "short" prefix for the purposes of filename expansion (i.e. filename expansion is always done on the long variants). -- Shankar. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/