unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org, t901353@rds294.goodyear.com
Subject: Re: large files not found with `read-file-name'
Date: Fri, 12 Apr 2002 12:57:20 +0300	[thread overview]
Message-ID: <2561-Fri12Apr2002125720+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <200204112026.QAA27376@rds294.goodyear.com> (message from Tom Wurgler on Thu, 11 Apr 2002 16:26:50 -0400 (EDT))

> From: Tom Wurgler <twurgler@goodyear.com>
> Date: Thu, 11 Apr 2002 16:26:50 -0400 (EDT)
> 
> One of the users here has a file thusly:
> 
>   -rw-rw-r--   1 tomw    bob   2399830016 Apr 11 11:41 sample.file
> 
> Which GNU ls does list in a dired properly, albeit the filenames are not
> aligned etc.
> 
> But he has a emacs-lisp defun that prompts him for various input, one of 
> which is the above "sample.file" filename.  The file completion does not find 
> the file.  He is not trying to read the file itself, just get the filename and
> then he runs a shell job with the inputs gained from his elisp...
> 
> The line below demostates the problem:
> 
> (setq tommy (read-file-name "Enter the name: "))
> 
> You can start typing "sa" at the prompt, then hit "tab" and all files that start
> with "sa" are displayed except the "sample.file".  Why doesn't this file show
> up?

A stab in the dark: perhaps this happens because the standard C
library used to link Emacs has a version of the `stat' function which
doesn't support large files?  (2399830016 is more than 2GBytes.)  If
`stat' fails for that file, Emacs completion routines will behave as
if the file didn't exist, I think.

If my guess is true, `ls' could have been built with large file
support enabled.

  reply	other threads:[~2002-04-12  9:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-11 20:26 large files not found with `read-file-name' Tom Wurgler
2002-04-12  9:57 ` Eli Zaretskii [this message]
2002-04-12 11:50 ` Andreas Schwab

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=2561-Fri12Apr2002125720+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=t901353@rds294.goodyear.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.
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).