all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Visuwesh <visuweshm@gmail.com>, Laurence Warne <laurencewarne@gmail.com>
Cc: 59272@debbugs.gnu.org
Subject: bug#59272: [PATCH] Make Memory Human Readable in proced Buffers
Date: Mon, 14 Nov 2022 19:40:31 -0800	[thread overview]
Message-ID: <CADwFkm=CfpizbJg75_-dyaHRiTZ4cSF+ipXPYykaO86-9-S-ag@mail.gmail.com> (raw)
In-Reply-To: <87a64sew18.fsf@gmail.com>

Visuwesh <visuweshm@gmail.com> writes:

> [திங்கள் நவம்பர் 14, 2022] Laurence Warne wrote:
>
>> Hi, this patch makes vsize and rss human readable in proced buffers by
>> formatting them as megabytes or gigabytes according to their size, similar
>> as the -h flag for ls and du.
>>
>> The current behaviour is to show them always as kilobytes, though I'm
>> unsure if this meant as 1000 bytes or 1024 bytes, this patch assumes the
>> former case.
>
> We can leave this to the user to decide by...
>
>> +(defun proced-format-memory (kilobytes)
>> +  "Format KILOBYTES in a human readable format."
>
> ... using `file-size-human-readable' instead.

Yes, we could do something like

(defcustom  proced-format-memory-function #'file-size-human-readable
  "..."
  )

Where one of the options is #'identity, which means not to use human
readable sizes, and then funcall that.





  reply	other threads:[~2022-11-15  3:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 10:19 bug#59272: [PATCH] Make Memory Human Readable in proced Buffers Laurence Warne
2022-11-15  3:28 ` Visuwesh
2022-11-15  3:40   ` Stefan Kangas [this message]
2022-11-15  8:06     ` Juri Linkov
2022-11-15  8:59       ` Stefan Kangas
2022-11-15  9:51         ` Laurence Warne
2022-11-16  8:56           ` Laurence Warne
2022-11-17  9:55             ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=CfpizbJg75_-dyaHRiTZ4cSF+ipXPYykaO86-9-S-ag@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=59272@debbugs.gnu.org \
    --cc=laurencewarne@gmail.com \
    --cc=visuweshm@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.