From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32420@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#32420: 26.1.50; Ibuffer: Detect correctly the buffers running a process
Date: Sun, 12 Aug 2018 17:21:36 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1808121711410.2578@calancha-pc.dy.bbexcite.jp> (raw)
In-Reply-To: <83in4gls8n.fsf@gnu.org>
>>> How do you see it reporting a process? What I see is that it reports
>>> a pseudo-file for it. Am I missing something?
>> Attached 1 picture.
>> It shows at the bottom the line:
>> 3 buffers 2515909 1 file, 1 process
>
> Ah, okay. So, to fix this, isn't it better to see if the current
> buffer is a process-buffer of some process in process-list?
It's a bit tricky code.
When such thing run, the summarizer, I believe the current buffer
is *Ibuffer*; you receive 'strings': they are the rows in
column 'Filename/Process'.
There is no direct way to connect each string with its buffer. The
original code make the assumption that if 'string' matches something like
(foobar)
then it corresponds to a buffer running a process.
That assumption is wrong, for instance, in several info buffers.
Because you first create all columns, and the summarizer runs at the end,
I thought is simple to add the process as a text property for those
buffers having a process. Then you don't need any assumption on 'string':
you just check whether if 'string' has a property 'ibuffer-process' or
not.
next prev parent reply other threads:[~2018-08-12 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 16:48 bug#32420: 26.1.50; Ibuffer: Detect correctly the buffers running a process Tino Calancha
2018-08-11 16:57 ` Eli Zaretskii
2018-08-11 17:13 ` Tino Calancha
2018-08-11 17:37 ` Eli Zaretskii
2018-08-12 8:21 ` Tino Calancha [this message]
2018-08-12 18:46 ` Eli Zaretskii
2018-08-13 10:30 ` Tino Calancha
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=alpine.DEB.2.20.1808121711410.2578@calancha-pc.dy.bbexcite.jp \
--to=tino.calancha@gmail.com \
--cc=32420@debbugs.gnu.org \
--cc=eliz@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.
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.