From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tino Calancha Newsgroups: gmane.emacs.bugs Subject: bug#23734: 25.1.50; ibuffer: Search a buffer by content Date: Fri, 10 Jun 2016 18:17:54 +0900 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11415196871fac0534e903c4 X-Trace: ger.gmane.org 1465550464 32761 80.91.229.3 (10 Jun 2016 09:21:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 10 Jun 2016 09:21:04 +0000 (UTC) To: 23734@debbugs.gnu.org, Tino Calancha Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jun 10 11:20:56 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1bBIcZ-0005E3-CC for geb-bug-gnu-emacs@m.gmane.org; Fri, 10 Jun 2016 11:20:55 +0200 Original-Received: from localhost ([::1]:39257 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bBIcY-0007UO-Gz for geb-bug-gnu-emacs@m.gmane.org; Fri, 10 Jun 2016 05:20:54 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55880) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bBIZs-0005N8-3B for bug-gnu-emacs@gnu.org; Fri, 10 Jun 2016 05:18:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bBIZn-0005T5-00 for bug-gnu-emacs@gnu.org; Fri, 10 Jun 2016 05:18:06 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:51040) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bBIZm-0005Sz-SQ for bug-gnu-emacs@gnu.org; Fri, 10 Jun 2016 05:18:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bBIZm-0006HW-Gw for bug-gnu-emacs@gnu.org; Fri, 10 Jun 2016 05:18:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Tino Calancha Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 10 Jun 2016 09:18:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 23734 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 23734-submit@debbugs.gnu.org id=B23734.146555028124139 (code B ref 23734); Fri, 10 Jun 2016 09:18:02 +0000 Original-Received: (at 23734) by debbugs.gnu.org; 10 Jun 2016 09:18:01 +0000 Original-Received: from localhost ([127.0.0.1]:35144 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bBIZl-0006HH-Ad for submit@debbugs.gnu.org; Fri, 10 Jun 2016 05:18:01 -0400 Original-Received: from mail-yw0-f176.google.com ([209.85.161.176]:34468) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bBIZk-0006H2-42 for 23734@debbugs.gnu.org; Fri, 10 Jun 2016 05:18:00 -0400 Original-Received: by mail-yw0-f176.google.com with SMTP id c72so61090367ywb.1 for <23734@debbugs.gnu.org>; Fri, 10 Jun 2016 02:18:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=n0D0zyHfVrW2hJJeNb6ocJksgiL+ooKV90j2M7c1qvI=; b=i3TSwQaDM3K/qoEe+qRLv5BQnlxHheJkXRzIK0dSXMDocGWDB2oqn4rBpgfQ8lQfgv BtgrDH6uPSenxRqToS8+s+6aMPw1w1o5kjfxirkmMxgAfDnQOOtZqQ3JIM5v0OL20/wg f8t9Y17+xdQAyoIjI4euhrD3aH0XcvF/EpkNcu651tG60P06MqNdU3C4KpLLG4oSjgmQ QTv4gKcUKuOIcYKTSk7sd8zCKJbGFI28wLF9oALqt6eHRKHO3jcMQ4WPvtgkgtoZOaa5 NECapM5yFx+MqRpESzrrNtkeMMN2ghkzSONczoxOusXP4KwLmoo7YIUhhztwnRhGJTEE lHPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=n0D0zyHfVrW2hJJeNb6ocJksgiL+ooKV90j2M7c1qvI=; b=PO/rZZzoY4newYDcuQGQ1AmFmpLF4XDB0fuEASB0XaVZeGbqI/7dzkw0qvmkenIxQs RcKbNItTlQUdeyYmk2/wrdH/EmAbweEArcTeH/u6O3R6e6O7AvFixmeqfNp0kJ2huaUD /Hsn/ACLSDXrzhBgWE3CBfF82cNz+9qZH3W2VlXdGDGHhVoGyQzEABCLFjIqP796EMxg 0PMD/Y7YDSlgBTVXv9fEaFUENOw6X1zEuAYzM1QJzzYbyqFx4VWhRC4MJIuTm5JmVLQk lh6+ZGlimsuQoO6X6jsOKen1ExwrqV0utEywMc1K8rfruBhwjIPMlFqIMBV9LTHbdKgk Ljfw== X-Gm-Message-State: ALyK8tLUbQiHnxb9RfjtY2NB6HrDOyfvLoeJR3c5tlT9+xZIgU5Rc/fuzBBnQFFcLp4zE3idxCAhpbTqPoAV5g== X-Received: by 10.129.51.67 with SMTP id z64mr463227ywz.149.1465550274763; Fri, 10 Jun 2016 02:17:54 -0700 (PDT) Original-Received: by 10.37.215.216 with HTTP; Fri, 10 Jun 2016 02:17:54 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:119369 Archived-At: --001a11415196871fac0534e903c4 Content-Type: text/plain; charset=UTF-8 > multi-occur can do this kind of thing. > C-u M-x multi-occur-in-matching-buffers RET . RET foo (bar) RET You are right! Having several ways to solve a problem, letting you to choose the one you like more is generally a good thing. *) multi-occur-in-matching-buffers is certainly a more general solution (don't require the user being familiar with Ibuffer). *) The ibuffer approach it could be more suitable for people using ibuffer or dired. On Fri, Jun 10, 2016 at 6:16 PM, Tino Calancha wrote: > > multi-occur can do this kind of thing. > > C-u M-x multi-occur-in-matching-buffers RET . RET foo (bar) RET > > You are right! > Having several ways to solve a problem, letting you to choose the one you > like more is generally a good thing. > > *) multi-occur-in-matching-buffers is certainly a more general solution > (don't require > the user being familiar with Ibuffer). > *) The ibuffer approach it could be more suitable for people using ibuffer > or dired. > > > On Fri, Jun 10, 2016 at 2:24 AM, Glenn Morris wrote: > >> Tino Calancha wrote: >> >> > It's commun one Emacs session having dozens of buffers on memory. On >> > such situation, it is hard to remember the name of one particular >> > buffer. >> > >> > It may be useful having easy way to search buffers by content. >> >> multi-occur can do this kind of thing. >> >> > For example, one user is developping a funtion foo >> > in the buffer BUF, with name BUF-NAME: >> > >> > foo-type foo (bar) >> > >> > The user may not remember BUF-NAME, but s/he could be able >> > to write a regexp matching just the content of BUF. >> > For instance, something like >> > "foo (bar)" >> > likely would match just BUF content (or a few buffers more). >> >> >> C-u M-x multi-occur-in-matching-buffers RET . RET foo (bar) RET >> > > --001a11415196871fac0534e903c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
> mult= i-occur can do this kind of thing.
> C-u M-= x multi-occur-in-matching-buffers RET . RET foo (bar) RET

=C2=A0You are right!
=C2=A0 Having several ways to solve a prob= lem, letting you to choose the one you
=C2=A0like more is generall= y a good thing.

*) multi-occur-in-matching-buffers is certainl= y a more general solution (don't require
=C2=A0=C2=A0=C2=A0 th= e user being familiar with Ibuffer).
*) The ibuffer approach it co= uld be more suitable for people using ibuffer or dired.

On Fri, Jun 10, 2016 at 6:16 PM= , Tino Calancha <f92capac@gmail.com> wrote:
> multi-occur can do this kind of thing.
> C-u M-x multi-occur-in-matching-buffers RET . RET foo (bar) RET<= br>
=C2=A0You are right!
=C2=A0 Having several way= s to solve a problem, letting you to choose the one you
=C2=A0like= more is generally a good thing.

*) multi-occur-in-matching-bu= ffers is certainly a more general solution (don't require
=C2= =A0=C2=A0=C2=A0 the user being familiar with Ibuffer).
*) The ibuf= fer approach it could be more suitable for people using ibuffer or dired.


On Fri, Jun 10, 2016 at 2:24 AM, Glenn Morris <rgm@gnu.org> wrot= e:
Tino Calancha wrote:

> It's commun one Emacs session having dozens of buffers on memory. = On
> such situation, it is hard to remember the name of one particular
> buffer.
>
> It may be useful having easy way to search buffers by content.

multi-occur can do this kind of thing.

> For example, one user is developping a funtion foo
> in the buffer BUF, with name BUF-NAME:
>
> foo-type foo (bar)
>
> The user may not remember BUF-NAME, but s/he could be able
> to write a regexp matching just the content of BUF.
> For instance, something like
> "foo (bar)"
> likely would match just BUF content (or a few buffers more).


C-u M-x multi-occur-in-matching-buffers RET . RET foo (bar) RET


--001a11415196871fac0534e903c4--