From: "David L" <idht4n@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: buffer for unopened file?
Date: Fri, 19 Oct 2007 10:53:18 -0700 [thread overview]
Message-ID: <b79371120710191053i47df312cwc88fc75fe8b656f8@mail.gmail.com> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICCELMEAAA.drew.adams@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1476 bytes --]
On 10/19/07, Drew Adams <drew.adams@oracle.com> wrote:
<snip>
> Making files available in the buffer list means visiting them, even if
> they
> are not displayed. So if by "open" he means visit, then what he wants is
> impossible
That's what I figured, but I hoped there might be a layer
of abstraction between the list of buffers and the actual
buffers that would allow the buffer to be lazy opened
when the buffer was actually visited. So the buffer
list would be a combination of real buffers and
buffers that could exist by visiting a file if the user
tried to view that buffer.
The use case is that I have a makefile that
generates dependencies for an application
and those dependencies are scattered around
a directory tree with other files that aren't
dependencies. When I'm working on the source
code, I sometimes want to open a file that I know
starts with xyz, but I don't know its directory or
what it ends with. It would be nice to use buffer
name completion to find the file. What I do today
is a tags search for something I know is in that
file, but sometimes I can't think of exactly what's
in it. If I could just type C-x b xyz<tab> and see
a list of all of the (pseudo)buffers that begin
with xyz or search my ECB alphabetized
buffer list for the file, that would be great.
>
> So I think he's gotten some help for his problem from both of us,
> depending
> on what he really wants. ;-)
Yes, thank you all for your suggestions. I'll try them out.
[-- Attachment #1.2: Type: text/html, Size: 2093 bytes --]
[-- Attachment #2: Type: text/plain, Size: 152 bytes --]
_______________________________________________
help-gnu-emacs mailing list
help-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
next prev parent reply other threads:[~2007-10-19 17:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 14:27 buffer for unopened file? David L
2007-10-19 15:18 ` Amy Templeton
2007-10-19 15:36 ` Sebastian Tennant
2007-10-19 15:54 ` Drew Adams
2007-10-19 16:07 ` Sebastian Tennant
2007-10-19 17:21 ` Drew Adams
2007-10-19 17:53 ` David L [this message]
2007-10-19 18:20 ` Drew Adams
2007-10-20 16:39 ` Dieter Wilhelm
2007-10-20 17:09 ` Drew Adams
2007-10-20 17:53 ` Dieter Wilhelm
2007-10-20 20:47 ` Dieter Wilhelm
2007-10-20 21:29 ` Icicles and Emacs [was: buffer for unopened file?] Drew Adams
[not found] ` <mailman.2372.1192913119.18990.help-gnu-emacs@gnu.org>
2007-10-23 13:29 ` Icicles integration into CVS emacs (was: buffer for unopened file?) Giles Chamberlin
2007-10-21 20:56 ` buffer for unopened file? David L
[not found] ` <mailman.2406.1193000213.18990.help-gnu-emacs@gnu.org>
2007-10-24 12:55 ` Mathias Dahl
[not found] <mailman.2307.1192804070.18990.help-gnu-emacs@gnu.org>
2007-10-19 17:42 ` Stefan Monnier
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=b79371120710191053i47df312cwc88fc75fe8b656f8@mail.gmail.com \
--to=idht4n@gmail.com \
--cc=help-gnu-emacs@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.
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).