public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: 'touch filename.ext' will touch 'filename.ext.exe' or 'filename.ext.lnk' or 'filename.ext.exe.lnk' if they exist when there's no 'filename.ext'
Date: Sun, 7 Aug 2022 14:36:44 +0200	[thread overview]
Message-ID: <74593e91-20c2-dfe4-86e2-55dad3721fbc@gmail.com> (raw)
In-Reply-To: <77a27ddf-2771-76bf-bbaa-374efbf296d7@mail.ru>

On 02.08.2022 15:45, Mike Kaganski wrote:
> Hi!
> 
> Using cygwin 3.3.4-2 and 3.3.5-1:
> 
> 
> Create a file named 'file.ext.exe'.
> 
> In cygwin, run:
> 
>  > touch file.ext
> 
> 
> Examine the directory. The 'file.ext' wasn't created; the file 
> 'file.ext.exe' timestamp was updated.
> 

Hi Mike,
it is an expect behaviour as "file.ext.exe" has as alias "file.ext"

see User Guide

https://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-exe

Regards
Marco



      reply	other threads:[~2022-08-07 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-02 13:45 Mike Kaganski
2022-08-07 12:36 ` Marco Atzeri [this message]

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=74593e91-20c2-dfe4-86e2-55dad3721fbc@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /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).