unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tino Calancha <f92capac@gmail.com>
To: 23734@debbugs.gnu.org, Tino Calancha <f92capac@gmail.com>
Subject: bug#23734: 25.1.50; ibuffer: Search a buffer by content
Date: Fri, 10 Jun 2016 18:17:54 +0900	[thread overview]
Message-ID: <CAMn5WmaTgCe803obvbQg7SvsrB8sfvX5QaisWYJycBQP=_ssug@mail.gmail.com> (raw)
In-Reply-To: <CAMn5WmaW1RYx=b-6_M21ko-Zwj8a_SRD82yQny-44Df49E4Yrw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]

> 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 <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
>
>  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 <rgm@gnu.org> 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
>>
>
>

[-- Attachment #2: Type: text/html, Size: 2950 bytes --]

  parent reply	other threads:[~2016-06-10  9:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09  6:19 bug#23734: 25.1.50; ibuffer: Search a buffer by content Tino Calancha
2016-06-09 17:24 ` Glenn Morris
2016-06-09 17:28   ` Glenn Morris
2016-06-10  9:20     ` Tino Calancha
2016-06-15  4:33     ` C. Calancha
     [not found]   ` <CAMn5WmaW1RYx=b-6_M21ko-Zwj8a_SRD82yQny-44Df49E4Yrw@mail.gmail.com>
2016-06-10  9:17     ` Tino Calancha [this message]
2016-07-03  6:13 ` bug#23734: (no subject) 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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='CAMn5WmaTgCe803obvbQg7SvsrB8sfvX5QaisWYJycBQP=_ssug@mail.gmail.com' \
    --to=f92capac@gmail.com \
    --cc=23734@debbugs.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).