unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Bug Emacs 21.3: write-file downcasing
Date: 12 Feb 2003 11:26:10 +0100	[thread overview]
Message-ID: <5xwuk5ssl9.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <m2ptpx299k.fsf@nyaumo.jasonr.f2s.com>

Jason Rumney <jasonr@gnu.org> writes:

> Richard Stallman <rms@gnu.org> writes:
> 
> > That adds to the weight of the need.  Still, I would much rather
> > we could avoid the need to compare file names using anything other
> > than string=.
> 
> Even on GNU and similar systems, it is probably better to compare
> inodes than strings to determine if two files are the same file.
> That would deal with case-insensitive filesystems where they exist on
> those platforms.
> 
> There are already places in the Emacs code where inodes are used (to
> deal with hard-links), making a function available for lisp to do
> such a comparison and encouraging people to use it rather than string=
> seems like a good thing to me.

So there are really two issues here when comparing two file names A and B:

1) do A and B name the same file  (could be in different directories)
 
2) are A and B the "same" file name, if underlaying FS is case insensitive.

In case 1), comparing inodes (when available) will be the correct solution.

In case 2), just comparing inodes doesn't help.


Furthermore, if the file hasn't been created yet, you cannot use inodes to
compare names A and B...

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2003-02-12 10:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07  5:38 Bug Emacs 21.3: write-file downcasing Dhruva Krishnamurthy
2003-02-07  8:07 ` Juanma Barranquero
2003-02-07 15:23   ` Eli Zaretskii
2003-02-07 15:50     ` Juanma Barranquero
2003-02-07 17:16       ` Eli Zaretskii
2003-02-07 17:33         ` Juanma Barranquero
2003-02-07 17:57           ` Stefan Monnier
2003-02-07 18:19             ` Eli Zaretskii
2003-02-09 12:39               ` Richard Stallman
2003-02-09 15:52                 ` Eli Zaretskii
2003-02-10  4:41                   ` Dhruva Krishnamurthy
2003-02-10  5:46                     ` Eli Zaretskii
2003-02-10 10:03                       ` Dhruva Krishnamurthy
2003-02-10  8:21                     ` Jason Rumney
2003-02-10 10:44                       ` Juanma Barranquero
     [not found]               ` <m2smuxcwba.fsf@primate.xs4all.nl>
2003-02-10 22:39                 ` Richard Stallman
2003-02-10 22:52                   ` Andreas Schwab
2003-02-11 22:25                     ` Richard Stallman
2003-02-12  8:28                       ` Jason Rumney
2003-02-12 10:26                         ` Kim F. Storm [this message]
2003-02-12 19:36                           ` Jason Rumney
2003-02-12 17:50                         ` Kevin Rodgers
2003-02-12 22:19                           ` Andreas Schwab
2003-02-14 22:29                             ` Kevin Rodgers
2003-02-11 14:53                   ` Benjamin Riefenstahl
2003-02-11 23:02                     ` Jason Rumney
2003-02-12 13:37                       ` Benjamin Riefenstahl
2003-02-12 13:49                         ` Andreas Schwab
2003-02-12 14:57                           ` Benjamin Riefenstahl
2003-02-12 19:40                         ` Jason Rumney
2003-02-07 18:18           ` Eli Zaretskii
2003-02-07 20:19             ` Juanma Barranquero
2003-02-07 23:03               ` Eli Zaretskii
2003-02-07 18:31         ` Jason Rumney

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=5xwuk5ssl9.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.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).