From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: knagano@sodan.org, emacs-devel@gnu.org,
Andrew Innes <andrewi@gnu.org>, Jason Rumney <jasonr@gnu.org>
Subject: Re: init_buffer PWD fix
Date: Mon, 22 Apr 2002 11:10:55 +0300 (IDT) [thread overview]
Message-ID: <Pine.SUN.3.91.1020422110157.11473R-100000@is> (raw)
In-Reply-To: <200204220701.g3M71K923828@sic.twinsun.com>
On Mon, 22 Apr 2002, Paul Eggert wrote:
> > The problem is probably what you'd guess: the inode comparison doesn't
> > work on Windows as well as it does on Posix platforms...
>
> If memory serves, that problem occurs on some Windows platforms but
> not on others
It depends on the library used to build Emacs. Windows filesystems don't
have inodes, so a library must emulate them, and the emulation should be
good enough to DTRT in such cases. IIRC, the stock Windows runtime
simply returns zero in the inode member.
> so any workaround should apply only to Windows
> platforms where 'stat' is broken. Fcopy_file uses the conditional
> `#if !defined (DOS_NT) || __DJGPP__ > 1' before inspecting st_ino;
> would that be appropriate here too?
DJGPP emulates the inodes well enough for the code to work, but the
Windows port is not compiled with DJGPP. It is compiled with MSVC or
MinGW, both of which use the Windows runtime.
There's an inode emulation code in src/w32.c, but it seems like it's
disabled. Jason, can you tell why (I've read the comments, but it sounds
like this case contradicts them)?
Personally, I think the code in buffer.c could compare normalized file
names as either an alternative or a complementary to the inode method.
Then it could be made reliable on more platforms.
> > But even so, I still don't see how this would cause a failure.
>
> If 'stat' is broken, then Emacs can think that $PWD is correct even
> when it is not.
I understand that, but a specific example might still help. Thhis is the
first time I see such a complaint, so I wonder how come no one else sees
the problem.
next prev parent reply other threads:[~2002-04-22 8:10 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-21 20:15 init_buffer PWD fix Keiichiro Nagano
2002-04-21 23:00 ` Keiichiro Nagano
2002-04-22 6:18 ` Paul Eggert
2002-04-22 7:20 ` Keiichiro Nagano
2002-04-22 11:15 ` Eli Zaretskii
2002-04-22 21:16 ` Jason Rumney
2002-04-22 7:53 ` Eli Zaretskii
2002-04-22 7:01 ` Paul Eggert
2002-04-22 8:10 ` Eli Zaretskii [this message]
2002-04-22 7:22 ` Paul Eggert
2002-04-22 11:14 ` Eli Zaretskii
2002-04-22 23:21 ` Paul Eggert
2002-04-23 6:05 ` Eli Zaretskii
2002-04-22 21:21 ` Jason Rumney
2002-04-23 5:56 ` Eli Zaretskii
2002-04-23 6:14 ` MIYASHITA Hisashi
2002-04-23 11:00 ` Eli Zaretskii
2002-04-24 17:55 ` Richard Stallman
2002-04-24 18:14 ` MIYASHITA Hisashi
2002-04-23 17:45 ` Paul Eggert
2002-04-24 6:52 ` MIYASHITA Hisashi
2002-04-24 7:13 ` Paul Eggert
2002-04-24 7:45 ` MIYASHITA Hisashi
2002-04-24 11:12 ` Eli Zaretskii
2002-04-24 10:30 ` MIYASHITA Hisashi
2002-04-24 16:03 ` Eli Zaretskii
2002-04-24 17:13 ` MIYASHITA Hisashi
2002-04-24 18:10 ` Eli Zaretskii
2002-04-24 18:25 ` MIYASHITA Hisashi
2002-04-24 19:19 ` Paul Eggert
2002-04-24 19:41 ` MIYASHITA Hisashi
2002-04-24 19:59 ` MIYASHITA Hisashi
2002-04-24 20:21 ` Paul Eggert
2002-04-24 20:41 ` MIYASHITA Hisashi
2002-04-24 21:01 ` Paul Eggert
2002-04-24 21:23 ` MIYASHITA Hisashi
2002-04-24 21:35 ` MIYASHITA Hisashi
2002-04-25 22:52 ` Stefan Monnier
2002-04-25 3:42 ` Eli Zaretskii
2002-04-24 16:47 ` Paul Eggert
2002-04-24 17:55 ` MIYASHITA Hisashi
2002-04-24 10:38 ` MIYASHITA Hisashi
2002-04-24 16:08 ` Eli Zaretskii
2002-04-24 16:10 ` Eli Zaretskii
2002-04-24 7:55 ` MIYASHITA Hisashi
2002-04-24 11:07 ` Eli Zaretskii
2002-04-24 11:05 ` Eli Zaretskii
2002-04-24 10:31 ` MIYASHITA Hisashi
2002-04-24 16:05 ` Eli Zaretskii
2002-04-22 7:03 ` Eli Zaretskii
2002-04-22 6:49 ` Keiichiro Nagano
2002-04-22 8:01 ` Eli Zaretskii
2002-04-22 8:26 ` Keiichiro Nagano
2002-04-22 11:19 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.3.91.1020422110157.11473R-100000@is \
--to=eliz@is.elta.co.il \
--cc=andrewi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=knagano@sodan.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).