From: Andreas Politz <politza@fh-trier.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Long buffer names in buffer menu [Emacs 22.1 on w32]
Date: Thu, 22 Oct 2009 08:50:55 +0200 [thread overview]
Message-ID: <878wf3ncq8.fsf@fh-trier.de> (raw)
In-Reply-To: icoco0b1kp.fsf@verizon.net
despen@verizon.net writes:
> "B. T. Raven" <nihil@nihilo.net> writes:
>
>> Adam Beneschan wrote:
>>> On Oct 21, 9:25 am, "Drew Adams" <drew.ad...@oracle.com> wrote:
>>>
>>>> So there is some confusion as to what you are using. Your initial mail spoke of
>>>> buff-menu.el, but it also spoke about "electric" buffer list. Those are two
>>>> different things.
>>>
>>> Actually, my initial post didn't mention any .el files. Just for the
>>> record....
>>>
>>> -- Adam
> ....
>> (setq truncate-lines t)
>
> Okay, so this sort of works:
>
> (add-hook 'electric-buffer-menu-mode-hook
> '(lambda ()
> (setq truncate-lines nil)))
>
> The long names are shown continued on the next line.
> The only problem is that cursor movement moves through
> the extended file name. Not a big problem.
You could try to flet-bind `abbreviate-file-name' around
`electric-buffer-list' and shorten the filename in which ever way you
like.
-ap
next prev parent reply other threads:[~2009-10-22 6:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 17:51 Long buffer names in buffer menu Adam Beneschan
2009-10-20 21:52 ` B. T. Raven
2009-10-20 22:58 ` Drew Adams
2009-10-21 15:38 ` Adam Beneschan
2009-10-21 16:25 ` Drew Adams
2009-10-21 16:33 ` despen
[not found] ` <mailman.9220.1256142396.2239.help-gnu-emacs@gnu.org>
2009-10-21 16:39 ` despen
2009-10-21 19:52 ` Adam Beneschan
2009-10-22 1:39 ` Long buffer names in buffer menu [Emacs 22.1 on w32] B. T. Raven
2009-10-22 2:32 ` despen
2009-10-22 6:50 ` Andreas Politz [this message]
2009-10-23 22:53 ` Adam Beneschan
2009-10-24 1:05 ` despen
2009-10-20 22:20 ` Long buffer names in buffer menu despen
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=878wf3ncq8.fsf@fh-trier.de \
--to=politza@fh-trier.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).