From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: luangruo@yahoo.com, laurencewarne@gmail.com, 59407@debbugs.gnu.org
Subject: bug#59407: [PATCH] Add Colors to proced
Date: Fri, 25 Nov 2022 17:07:29 +0200 [thread overview]
Message-ID: <835yf3ul72.fsf@gnu.org> (raw)
In-Reply-To: <87pmdbnuee.fsf@gmx.de> (message from Michael Albinus on Fri, 25 Nov 2022 12:30:33 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: Eli Zaretskii <eliz@gnu.org>, luangruo@yahoo.com, 59407@debbugs.gnu.org
> Date: Fri, 25 Nov 2022 12:30:33 +0100
>
> > Also, memory-info doesn't
> > appear to take into account working on remote systems like
> > list-system-processes does, so I've also disabled the threshold
> > highlighting for proced connected to remote machines. Suggestions on
> > this are welcome (:
>
> Indeed. Should we make memory-info aware of remote systems, like we have
> done with list-system-processes and file-system-info? At least for
> remote GNU/Linux systems, reading /proc/meminfo seems to be
> easy. Proper commands for *BSD and Darwin systems shall also be applicable.
>
> Eli?
I guess it would be nice, although not terribly important.
next prev parent reply other threads:[~2022-11-25 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 10:26 bug#59407: [PATCH] Add Colors to proced Laurence Warne
2022-11-20 10:48 ` Eli Zaretskii
2022-11-20 12:33 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-20 14:40 ` Eli Zaretskii
2022-11-21 9:07 ` Laurence Warne
2022-11-21 10:32 ` Michael Albinus
2022-11-21 14:28 ` Eli Zaretskii
2022-11-25 9:34 ` Laurence Warne
2022-11-25 11:30 ` Michael Albinus
2022-11-25 15:07 ` Eli Zaretskii [this message]
2022-11-25 15:19 ` Michael Albinus
2022-11-26 9:41 ` Laurence Warne
2022-11-27 16:04 ` Michael Albinus
2022-11-29 14:02 ` Laurence Warne
2022-12-01 18:17 ` Eli Zaretskii
2022-12-01 21:14 ` Laurence Warne
2022-11-26 12:47 ` Eli Zaretskii
2022-11-20 14:14 ` Michael Albinus
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=835yf3ul72.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59407@debbugs.gnu.org \
--cc=laurencewarne@gmail.com \
--cc=luangruo@yahoo.com \
--cc=michael.albinus@gmx.de \
/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.