From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 6995@debbugs.gnu.org, thierry.volpiatto@gmail.com
Subject: bug#6995: 24.0.50; get-free-disk-space doesn't return available space in dired
Date: Mon, 13 Sep 2010 08:56:19 +0200 [thread overview]
Message-ID: <83aanm5dyk.fsf@gnu.org> (raw)
In-Reply-To: <rir5h547gu.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Date: Tue, 07 Sep 2010 16:36:01 -0400
> Cc: 6995@debbugs.gnu.org
>
> df -Pk /home/user
>
> returns
>
> Filesystem 1024-blocks Used Available Capacity Mounted on
> /real_directory/home/user 461097104 333392304 127704800 73% /home/user
>
> Because the filesystem name is long, the numerical values do not line
> up with the column headings. The current code seems to assume that
> they do line up. Thus, running dired on "~" gets wrong values for the
> total size.
How about dropping the use of `df', at least on GNU/Linux? It's IMO
ridiculous to invoke an external program for a single system call. I
know that this system call is notoriously non-portable, and that doing
in Emacs all that system-dependent stuff that `df' does is not a good
idea. But at least on the most popular free system (and perhaps on a
few compatible ones) we could do it right without all that labor, and
gain stability and reliability that depending on `df' will never
achieve.
next prev parent reply other threads:[~2010-09-13 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 19:40 bug#6995: 24.0.50; get-free-disk-space doesn't return available space in dired Thierry Volpiatto
2010-09-07 20:36 ` Glenn Morris
2010-09-13 6:56 ` Eli Zaretskii [this message]
2010-09-13 10:14 ` Stefan Monnier
2010-09-13 13:22 ` Thierry Volpiatto
2010-09-15 18:39 ` Thierry Volpiatto
2010-09-18 13:54 ` Thierry Volpiatto
2010-09-25 20:17 ` Chong Yidong
2010-09-27 8:37 ` Thierry Volpiatto
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=83aanm5dyk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6995@debbugs.gnu.org \
--cc=rgm@gnu.org \
--cc=thierry.volpiatto@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.