From: "Juanma Barranquero" <lekktu@gmail.com>
To: "Aaron Maxwell" <amax@redsymbol.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: (source) Anything like this exist already? (buffer name intelligence)
Date: Fri, 11 Jan 2008 20:48:52 +0100 [thread overview]
Message-ID: <f7ccd24b0801111148g50afaab8q5c91a1dd4af977fa@mail.gmail.com> (raw)
In-Reply-To: <200801111101.27609.amax@redsymbol.net>
On Jan 11, 2008 8:01 PM, Aaron Maxwell <amax@redsymbol.net> wrote:
> Here's the defun I refered to in my post a moment ago:
> ; Better handle similar buffer names
> (defun extend-buffer-name (arg)
> "Extend the current buffer's name according to to its full file path.
> With prefix arg, extend by N levels. Default is one level."
Do you know about uniquify.el?
Juanma
next prev parent reply other threads:[~2008-01-11 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 19:01 (source) Anything like this exist already? (buffer name intelligence) Aaron Maxwell
2008-01-11 19:48 ` Juanma Barranquero [this message]
[not found] ` <mailman.6054.1200080936.18990.help-gnu-emacs@gnu.org>
2008-01-11 20:10 ` 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=f7ccd24b0801111148g50afaab8q5c91a1dd4af977fa@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=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).