From: tyler <tyler.smith@mail.mcgill.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: uniquify-buffer-name-style
Date: Thu, 09 Apr 2009 22:40:30 -0300 [thread overview]
Message-ID: <877i1ti8vl.fsf@blackbart.sedgenet> (raw)
In-Reply-To: 878wm9v14b.fsf@gmail.com
Sean Sieger <sean.sieger@gmail.com> writes:
> Peter Dyballa <Peter_Dyballa@Web.DE> writes:
>
> Am 09.04.2009 um 21:39 schrieb Sean Sieger:
>
> > Section 23.7.1 Making Buffer Names Unique in the manual doesn't
> > mention
> > the elisp (require 'uniquify) before discussing customizing the
> > variable, uniquify-buffer-name-style. Should it?
> >
> I think it's auto-loaded. C-h f uniq TAB gives a lot of functions.
>
> Not on GNU Emacs 23.0.92.2 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of
> 2009-04-09 on g41r2f1.
>
> If I evaluate (require 'uniquify), the variables and the functions
> become available through C-h v and C-h f.
>
> I don't have an older version of Emacs to check this on, do older
> versions auto-load uniquify.el?
>
I'm running 23.0.60.1, built from cvs on Debian, as well as the
prepackaged version 22.2.1 from the Debian Lenny repository, and neither
of them have uniquify autoloaded.
Tyler
--
The purpose of models is not to fit the data but to sharpen the
questions. --Samuel Karlin
next prev parent reply other threads:[~2009-04-10 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 13:09 uniquify-buffer-name-style Sean Sieger
2009-04-08 19:16 ` uniquify-buffer-name-style Tassilo Horn
2009-04-08 20:59 ` uniquify-buffer-name-style tyler
2009-04-08 22:02 ` uniquify-buffer-name-style Samuel Wales
2009-04-09 19:39 ` uniquify-buffer-name-style Sean Sieger
2009-04-09 22:20 ` uniquify-buffer-name-style Peter Dyballa
2009-04-09 23:49 ` uniquify-buffer-name-style Sean Sieger
2009-04-10 1:40 ` tyler [this message]
2009-04-10 14:08 ` uniquify-buffer-name-style Sean Sieger
[not found] ` <mailman.5004.1239315634.31690.help-gnu-emacs@gnu.org>
2009-04-10 0:46 ` uniquify-buffer-name-style Miles Bader
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=877i1ti8vl.fsf@blackbart.sedgenet \
--to=tyler.smith@mail.mcgill.ca \
--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).