From: Aaron Maxwell <amax@redsymbol.net>
To: help-gnu-emacs@gnu.org
Subject: Anything like this exist already? (buffer name intelligence)
Date: Fri, 11 Jan 2008 10:59:08 -0800 [thread overview]
Message-ID: <200801111059.08794.amax@redsymbol.net> (raw)
Hi all,
I find that much of the work I do now involves similarly named files, so that
the default buffer naming algorithm is less than ideal. For example, I write
Python code in the Django framework a lot, which at any given moment I'll
have a number of files like this open at once:
pkg1/__init__.py
pgk1/models.py
pkg1/views.py
pkg2/__init__.py
pkg1/views.py
some_unrelated_library/__init__.py
Etc. So it's hard to know what the buffer named "__init__.py<3>" corresponds
to just from memory, etc.
I've taken to renaming such buffers with a prefix in their file path, just
enough to make them unique: i.e., for "/home/amax/src/snazzylib/__init__.py",
I might rename its buffer from "__init__.py" to "snazzylib/__init__.py". And
I wrote a utility to automate this, which I've pasted below. I bind it to
C-c e, and thus can quickly give a new buffer a clueful name without
interrupting myself to think about it.
Am I reinventing the wheel here? I can't imagine being the first to be
annoyed by this, so there's a good chance this problem has already been
solved. If someone knows of an existing solution, can you point me to it?
If so, I may use that rather than putting more work into this (I have further
features in mind). Otherwise I'll add to it and package it up nice and
pretty so others can use it.
Thanks.
--
Aaron Maxwell
http://redsymbol.net
Business Owners and Self-Employed: You're NOT Alone!
The Business Butler - http://businessbutler.us
next reply other threads:[~2008-01-11 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 18:59 Aaron Maxwell [this message]
[not found] <mailman.6051.1200077954.18990.help-gnu-emacs@gnu.org>
2008-01-11 19:08 ` Anything like this exist already? (buffer name intelligence) Joost Kremers
2008-01-11 19:19 ` Aaron Maxwell
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=200801111059.08794.amax@redsymbol.net \
--to=amax@redsymbol.net \
--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).