unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Converting an Integer into Human Readable String
Date: Fri, 08 Apr 2011 09:07:45 +0200	[thread overview]
Message-ID: <87wrj5b4qm.fsf@gmail.com> (raw)
In-Reply-To: inmabq$qb0$1@news.sap-ag.de

Klaus Straubinger <KSNetz@UseNet.ArcorNews.DE> writes:

> Thierry Volpiatto <thierry.volpiatto@gmail.com> wrote:
>
>> anything have a function for this:
>>
>> (anything-ff-human-size 4060)
>> ==> "4.0K"
>
> And there is url-pretty-length from url-util.el (which is part of GNU Emacs):
>
>     (url-pretty-length 4060)
>     ==> "3k"
>
> (In this example, the result is "3k" because 4060 is smaller than
> 4 * 1024.)
Note that all functions that use elisp to get such result fail with:

--8<---------------cut here---------------start------------->8---
(url-pretty-length 7141892608)
Debugger entered--Lisp error: (overflow-error "7141892608")
--8<---------------cut here---------------end--------------->8---

When using big numbers.
Same for format-mode-line etc...

To avoid that the calc functions can be used giving a string instead of
integer.

--8<---------------cut here---------------start------------->8---
(anything-ff-human-size "7141892608")
==> "6.7G"
(anything-ff-human-size (nth 7 (file-attributes "~/.VirtualBox/Machines/LoseDows.vdi")))
==> "6.7G"
--8<---------------cut here---------------end--------------->8---

Would be great elisp handle such numbers.

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 




  reply	other threads:[~2011-04-08  7:07 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 10:02 Converting an Integer into Human Readable String Nordlöw
2011-04-07 11:34 ` Deniz Dogan
2011-04-07 12:04   ` Eli Zaretskii
2011-04-07 11:52 ` Eli Zaretskii
2011-04-07 12:51 ` Drew Adams
2011-04-07 17:43   ` Eli Zaretskii
2011-04-07 18:13     ` Drew Adams
2011-04-07 18:35       ` Eli Zaretskii
2011-04-07 18:51         ` Drew Adams
2011-04-07 20:10           ` Eli Zaretskii
2011-04-07 18:44       ` Eli Zaretskii
2011-04-07 19:01         ` Thierry Volpiatto
     [not found]         ` <mailman.17.1302204476.27822.help-gnu-emacs@gnu.org>
2011-04-08  6:35           ` Klaus Straubinger
2011-04-08  7:07             ` Thierry Volpiatto [this message]
2011-04-08  8:29               ` Eli Zaretskii
2011-04-08  9:38                 ` Thierry Volpiatto
2011-04-08 11:41 ` Pascal J. Bourguignon
2011-04-08 15:19   ` Eli Zaretskii
2011-04-08 19:12     ` Thierry Volpiatto
2011-04-08 21:36       ` Eli Zaretskii
2011-04-09  5:24         ` Thierry Volpiatto
2011-04-09  8:46   ` Eli Zaretskii
     [not found]   ` <mailman.1.1302338931.20547.help-gnu-emacs@gnu.org>
2011-04-09  9:33     ` Pascal J. Bourguignon
2011-04-09 12:13       ` Eli Zaretskii
     [not found]       ` <mailman.0.1302351322.29796.help-gnu-emacs@gnu.org>
2011-04-11 15:31         ` Ted Zlatanov
2011-04-11 16:57           ` Eli Zaretskii
2011-05-12 19:30           ` Ted Zlatanov

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=87wrj5b4qm.fsf@gmail.com \
    --to=thierry.volpiatto@gmail.com \
    --cc=help-gnu-emacs@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.
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).