From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: gnulib fsusage
Date: Thu, 19 Jan 2023 18:11:45 +0800 [thread overview]
Message-ID: <875yd296la.fsf@yahoo.com> (raw)
In-Reply-To: <83y1pzyqed.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 19 Jan 2023 08:44:42 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Date: Thu, 19 Jan 2023 10:24:29 +0800
>>
>> Apparently lib/fsusage.o is not built when there is no suitable way for
>> it to get the necessary information, but it is still used
>> unconditionally by Emacs.
>
> Not unconditionally: the implementation of file-system-info in
> fileio.c is conditioned on !DOS_NT, and both MSDOS and WINDOWSNT ports
> have their separate implementations which don't use Gnulib's fsusage.
>
>> Is this the right way to detect whether or not get_fs_usage is actually
>> present?
>
> Which port needs to exclude it, and why? Is that port going to
> implement its own version of file-system-info? We must have a
> non-trivial working implementation for each supported platform,
> because Dired (and Tramp?) uses it.
The Android port doesn't support statvfs, because that function is
missing from the Android C library, apparently for security reasons.
> If the port you are considering will have its own implementation, then
> the same method as DOS_NT uses will be appropriate.
I cannot find any way to do such an implementation, sorry. But if
someone else knows, that would be great. Thanks.
next prev parent reply other threads:[~2023-01-19 10:11 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bkmv6z36.fsf.ref@yahoo.com>
2023-01-19 2:24 ` gnulib fsusage Po Lu
2023-01-19 6:44 ` Eli Zaretskii
2023-01-19 8:52 ` Michael Albinus
2023-01-19 10:11 ` Po Lu [this message]
2023-01-19 10:26 ` Eli Zaretskii
2023-01-19 11:59 ` Po Lu
2023-01-19 13:33 ` Eli Zaretskii
2023-01-19 13:40 ` Po Lu
2023-01-19 14:27 ` Android port (was: gnulib fsusage) Eli Zaretskii
2023-01-19 14:34 ` Android port Po Lu
2023-01-19 14:56 ` Eli Zaretskii
2023-01-20 0:18 ` Po Lu
2023-01-20 7:09 ` Eli Zaretskii
2023-01-20 9:39 ` Po Lu
2023-01-25 10:48 ` Po Lu
2023-01-26 8:59 ` Eli Zaretskii
2023-01-20 6:47 ` Android port (was: gnulib fsusage) Jean Louis
2023-01-20 7:19 ` Eli Zaretskii
2023-01-28 7:50 ` Konstantin Kharlamov
2023-01-28 8:49 ` Eli Zaretskii
2023-01-28 9:06 ` Konstantin Kharlamov
2023-01-28 9:21 ` Eli Zaretskii
2023-01-28 9:31 ` Konstantin Kharlamov
2023-01-28 9:59 ` Android port Po Lu
2023-01-29 9:54 ` Android port (was: gnulib fsusage) Jean Louis
2023-01-28 9:57 ` Android port Po Lu
2023-01-28 10:23 ` Konstantin Kharlamov
2023-01-29 9:38 ` Android port (was: gnulib fsusage) Jean Louis
2023-01-29 20:36 ` 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=875yd296la.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--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).