unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: matlantis <matlantis@gmx.de>
To: Help-gnu-emacs@gnu.org
Subject: Re: file path in buffer name
Date: Tue, 17 Nov 2009 02:39:45 -0800 (PST)	[thread overview]
Message-ID: <26387680.post@talk.nabble.com> (raw)
In-Reply-To: <26369589.post@talk.nabble.com>


Thanks a lot for all the answers. i did not know that customization variable
and find it absolutely sufficient for my purpose. 
it showed me again: emacs is the best ;-)

greetings

Martin



matlantis wrote:
> 
> Hi emacs friends,
> 
> i have to edit multiple files with the same file name (CMakeLists.txt) and
> since emacs gives the buffer the name of the file and adding a number to
> it, it is very hard to decide with buffer has which file.
> 
> So what i need is a method to say emacs to make the buffer name looking
> like "CMakeLists.txt in <path>". Even better would be if <path> could be
> abbreviated to 30 characters, but thats not important.
> 
> I have no experience in elisp programming, please can anybody explain to
> me, what to put in my .emacs file to give emacs the desired behavior?
> 
> best regards and thanks for help
> 
> Martin
> 

-- 
View this message in context: http://old.nabble.com/file-path-in-buffer-name-tp26369589p26387680.html
Sent from the Emacs - Help mailing list archive at Nabble.com.





  parent reply	other threads:[~2009-11-17 10:39 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 10:21 file path in buffer name matlantis
2009-11-16 18:42 ` Drew Adams
2009-11-16 19:48   ` suvayu ali
2009-11-16 19:38 ` Sean Sieger
2009-11-16 19:44 ` Peter Dyballa
2009-11-17 10:39 ` matlantis [this message]
     [not found] ` <mailman.10881.1258454397.2239.help-gnu-emacs@gnu.org>
2009-11-29  7:19   ` Barrie
     [not found] <mailman.10818.1258395337.2239.help-gnu-emacs@gnu.org>
2009-11-16 19:10 ` Joost Kremers
2009-11-16 20:07   ` Lennart Borgman
2009-11-16 20:21     ` Peter Dyballa
2009-11-16 20:53     ` Sean Sieger
2009-11-16 21:23       ` Xavier Maillard
2009-11-17 15:17       ` Lennart Borgman
2009-11-17 15:31         ` Sean Sieger
2009-11-17 15:36           ` Lennart Borgman
2009-11-17 16:12             ` Sean Sieger
2009-11-17 16:22               ` Lennart Borgman
2009-11-17 16:49                 ` Sean Sieger
2009-11-17 16:55                   ` Lennart Borgman
2009-11-17 20:54                     ` Sean Sieger
2009-11-17 21:16                       ` Lennart Borgman
2009-11-17 21:40                         ` Drew Adams
2009-11-17 22:01                           ` Sean Sieger
2009-11-17 22:16                             ` Drew Adams
2009-11-17 23:02                               ` Sean Sieger
     [not found]     ` <mailman.10847.1258404828.2239.help-gnu-emacs@gnu.org>
2009-11-17  7:31       ` Joost Kremers
2009-11-17 14:43         ` Sean Sieger
     [not found]   ` <mailman.10839.1258402065.2239.help-gnu-emacs@gnu.org>
2009-11-17  7:27     ` Joost Kremers
2009-11-16 19:11 ` Alain Ketterlin

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=26387680.post@talk.nabble.com \
    --to=matlantis@gmx.de \
    --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).