From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Laurence Warne <laurencewarne@gmail.com>
Cc: 59407@debbugs.gnu.org
Subject: bug#59407: [PATCH] Add Colors to proced
Date: Sun, 20 Nov 2022 20:33:59 +0800 [thread overview]
Message-ID: <87wn7p7qko.fsf@yahoo.com> (raw)
In-Reply-To: <CAE2oLqhvrf4w=dGp8zmPbi68BfG0htUhH92CTuF+DgR2bmj41A@mail.gmail.com> (Laurence Warne's message of "Sun, 20 Nov 2022 10:26:35 +0000")
Laurence Warne <laurencewarne@gmail.com> writes:
> Hi, attached is a patch I've recently been working to do with
> colorizing proced buffers, similar to htop.
>
> In particular, the current Emacs process id is highlighted purple in
> both the process id and parent process id columns, session group
> leaders have their process ids underlined, larger memory sizes for rss
> and vsize are highlighted in darker shades of orange, and the first
> word in the args property (the executable) is highlighted in blue -
> I've attached a couple of screenshots.
Thanks, but what exactly is the purpose of this change?
The more colors that need to be allocated, the slower Emacs becomes over
a wide-area network. In addition, every time a new color is used,
xfont_draw needs to be called again, generating more network traffic.
Emacs has already become quite slow over a network connection (though
this should have become significantly better in Emacs 29.)
Adding "eye candy" where it is not really necessary will only be a step
backwards.
> (require 'proced)
> (setq-default proced-auto-update-flag t)
> (setq-default proced-auto-update-interval 1)
> (setq proced-enable-color-flag t)
I guess if it is off by default, then I have no objections. But I
respectfully ask everyone to keep in mind the network impact of changes
they make to Emacs.
next prev parent reply other threads:[~2022-11-20 12:33 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 [this message]
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
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=87wn7p7qko.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=59407@debbugs.gnu.org \
--cc=laurencewarne@gmail.com \
--cc=luangruo@yahoo.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.