From: John Yates <john@yates-sheets.org>
To: Tom <adatgyujto@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Feature suggestion: iswitchb should have an option to show virtual buffers like ido does
Date: Fri, 13 Jan 2012 14:31:22 -0500 [thread overview]
Message-ID: <CAJnXXohWZxX+bDX9Sfj5W5KRHLNJfK7E5ZXzW24ZU0XB-Ojbfg@mail.gmail.com> (raw)
In-Reply-To: <loom.20120113T155855-86@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
On Fri, Jan 13, 2012 at 10:11 AM, Tom <adatgyujto@gmail.com> wrote:
>
> BTW, there is one feature which ido could implement. This virtual buffer
> concept could be extended, so that the user can specify additional lists,
> not just recent files.
>
> For example, if I work on a project then there are files in it which
> I open only rarely, so these files are not on the recent files list.
> In this case I would compile the list of all files in the project and
> tell ido to also use this list. This way ido would list matches from
> the buffer list first, then from the recent files and then also from
> the list of project files.
>
I would absolutely love to see such a capability.
Today I already place in the root directory of each of my projects a list
of paths to all of the files in that project. I make a project current by
loading that file into s special buffer. Finally I have a special key
binding that uses that buffer and completion to open any project file.
Ideally I would have ido seach upwards through the directory tree starting
from the directory part of buffer-file-name for something like
.ido-project-files.
Such ido integration would eliminate my separate key binding and the
awkward statefulness of my current project files buffer.
/john
[-- Attachment #2: Type: text/html, Size: 1672 bytes --]
next prev parent reply other threads:[~2012-01-13 19:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 8:27 Feature suggestion: iswitchb should have an option to show virtual buffers like ido does Tom
2012-01-13 12:04 ` Richard Riley
2012-01-13 15:11 ` Tom
2012-01-13 19:31 ` John Yates [this message]
2012-01-13 19:59 ` Tom
2012-01-14 3:12 ` John Yates
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=CAJnXXohWZxX+bDX9Sfj5W5KRHLNJfK7E5ZXzW24ZU0XB-Ojbfg@mail.gmail.com \
--to=john@yates-sheets.org \
--cc=adatgyujto@gmail.com \
--cc=emacs-devel@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).