all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 4727@emacsbugs.donarmstrong.com
Subject: bug#4727: 23.1; `multi-isearch-(files|buffers)(-regexp)'
Date: Thu, 15 Oct 2009 15:52:18 -0700	[thread overview]
Message-ID: <083F366AB17D4E52AC846BCFEF20B28F@us.oracle.com> (raw)
In-Reply-To: <87fx9kz5x5.fsf@mail.jurta.org>

> However, we could convert relative file names to internal absolute
> file names before starting multi-file Isearch.  So you will be able
> to specify file names relative to the default directory where
> multi-file Isearch was started.

That was what I was thinking.

> > 3. Similarly, for `multi-isearch-buffers(-regexp)':
> >
> > a. The doc strings need to say explicitly that the BUFFERS must be
> > live buffers, not their names.
> >
> > b. Why should the BUFFERS need to be buffers - why not also allow
> > buffer names?
> >
> > The code is unnecessarily restrictive/brittle.
> 
> Similarly, we could convert buffer names to internal live buffers
> before starting multi-buffer Isearch.

Why not? That's pretty standard. Let the function do the work of calling
`get-buffer'.






  reply	other threads:[~2009-10-15 22:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87aay3kbad.fsf@mail.jurta.org>
2009-10-15  0:27 ` bug#4727: 23.1; `multi-isearch-(files|buffers)(-regexp)' Drew Adams
2009-10-15 21:28   ` Juri Linkov
2009-10-15 22:52     ` Drew Adams [this message]
2009-11-30 20:35   ` bug#4727: marked as done (23.1; `multi-isearch-(files|buffers)(-regexp)') Emacs bug Tracking System

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=083F366AB17D4E52AC846BCFEF20B28F@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=4727@emacsbugs.donarmstrong.com \
    --cc=juri@jurta.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.