uniquify-buffer-name-style

uniquify-buffer-name-style

[Sean Sieger]

GNU Emacs 23.0.92.1 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of
2009-03-31 on g41r2f1

Um, I'm working my way through the section `File Handling' in the manual
and came across the variable, uniquify-buffer-name-style, by way of the
node `Uniquify' and cannot find any trace of it, let alone how I might
set it to the value, forward.

Re: uniquify-buffer-name-style

[Tassilo Horn]

Sean Sieger <sean.sieger@gmail.com> writes:

Hi Sean,

> Um, I'm working my way through the section `File Handling' in the
> manual and came across the variable, uniquify-buffer-name-style, by
> way of the node `Uniquify' and cannot find any trace of it, let alone
> how I might set it to the value, forward.

  M-x customize-variable RET uniquify-buffer-name-style RET

HTH,
Tassilo

Re: uniquify-buffer-name-style

[tyler]

Tassilo Horn <tassilo@member.fsf.org> writes:

> Sean Sieger <sean.sieger@gmail.com> writes:
>
>> Um, I'm working my way through the section `File Handling' in the
>> manual and came across the variable, uniquify-buffer-name-style, by
>> way of the node `Uniquify' and cannot find any trace of it, let alone
>> how I might set it to the value, forward.
>
>   M-x customize-variable RET uniquify-buffer-name-style RET
>

[no match]

I'm running Emacs 23.0.60.1 and I can confirm that this variable,
mentioned in (info "(emacs)Uniquify"), doesn't appear to exist according
to C-h v or customize-variable.

Cheers,

Tyler

-- 
What is wanted is not the will to believe, but the will to find out,
which is the exact opposite.           --Bertrand Russell

Re: uniquify-buffer-name-style

[Samuel Wales]

Try putting (require 'uniquify) in .emacs.



On 2009-04-08, tyler <tyler.smith@mail.mcgill.ca> wrote:
> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> Sean Sieger <sean.sieger@gmail.com> writes:
>>
>>> Um, I'm working my way through the section `File Handling' in the
>>> manual and came across the variable, uniquify-buffer-name-style, by
>>> way of the node `Uniquify' and cannot find any trace of it, let alone
>>> how I might set it to the value, forward.
>>
>>   M-x customize-variable RET uniquify-buffer-name-style RET
>>
>
> [no match]
>
> I'm running Emacs 23.0.60.1 and I can confirm that this variable,
> mentioned in (info "(emacs)Uniquify"), doesn't appear to exist according
> to C-h v or customize-variable.
>
> Cheers,
>
> Tyler
>
> --
> What is wanted is not the will to believe, but the will to find out,
> which is the exact opposite.           --Bertrand Russell
>
>
>
>


-- 
Myalgic encephalomyelitis denialism is causing death and severe suffering,
worse than MS.  Greed is corrupting science into foul nonsense.  Anybody can
get the disease at any time permanently.  Do science and justice matter to
you?  http://www.meactionuk.org.uk/What_Is_ME_What_Is_CFS.htm

Re: uniquify-buffer-name-style

[Sean Sieger]

Samuel Wales <samologist@gmail.com> writes:

    Try putting (require 'uniquify) in .emacs.

On GNU Emacs 23.0.92.2 (i686-pc-linux-gnu, GTK+ Version 2.14.4) of
2009-04-09 on g41r2f1

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?

Re: uniquify-buffer-name-style

[Peter Dyballa]

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.

--
Greetings

   Pete

      _o    o         o   o
    _<<     \\_/\_,   \\_ \\_/\_,
   (*)/(*) (*)   (*) (*) `-    (*)

Re: uniquify-buffer-name-style

[Sean Sieger]

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'm totally digging having found this variable.  I have never wanted the
path in the title bar nor---god forbid---in the mode line.  However I
often have many files named `WORKSHEET' open and initializing this
variable with `forward' so solves ... scratches an itch I have had for a
long time.  Uh-huh, this completes a little system of every project
having a file of that name and `-*- outline -*-' at the top of each.

I don't have an older version of Emacs to check this on, do older
versions auto-load uniquify.el?

Re: uniquify-buffer-name-style

[tyler]

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

Re: uniquify-buffer-name-style

[Sean Sieger]

tyler <tyler.smith@mail.mcgill.ca> writes:

    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.

Thank you for your several reality checks, Tyler.

Re: uniquify-buffer-name-style

[Miles Bader]

Peter Dyballa <Peter_Dyballa@Web.DE> writes:
>> 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.

It's not.  Which is stupid.

http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=2853

-Miles

-- 
`Cars give people wonderful freedom and increase their opportunities.
 But they also destroy the environment, to an extent so drastic that
 they kill all social life' (from _A Pattern Language_)

uniquify-buffer-name-style

[Luc Teirlinck]

Setting `uniquify-buffer-name-style' outside Custom currently only
takes effect after uniquify.el is loaded.  This misfeature is caused
by the use of defadvice in uniquify.el.  As getting rid of this advice
in uniquify.el requires non-trivial changes to the C code, I do not
believe that it would be advisable to do this at the present time.

In the patch below, I just document the misfeature and add a comment
about the desirability to get rid of it instead.  I can install if
desired.

===File ~/uniquify.el-diff==================================
*** uniquify.el	06 Feb 2006 16:02:02 -0600	1.61
--- uniquify.el	28 May 2006 21:09:47 -0500	
***************
*** 93,99 ****
    "Unique buffer names dependent on file name."
    :group 'applications)
  
! 
  (defcustom uniquify-buffer-name-style nil
    "*If non-nil, buffer names are uniquified with parts of directory name.
  The value determines the buffer name style and is one of `forward',
--- 93,100 ----
    "Unique buffer names dependent on file name."
    :group 'applications)
  
! ;; The last paragraph of the docstring below should really be made obsolete
! ;; by eliminating the dependence on advice.
  (defcustom uniquify-buffer-name-style nil
    "*If non-nil, buffer names are uniquified with parts of directory name.
  The value determines the buffer name style and is one of `forward',
***************
*** 104,110 ****
    reverse        name\\mumble\\bar  name\\mumble\\quux
    post-forward   name|bar/mumble  name|quux/mumble
    post-forward-angle-brackets   name<bar/mumble>  name<quux/mumble>
!   nil            name  name<2>"
    :type '(radio (const forward)
  		(const reverse)
  		(const post-forward)
--- 105,116 ----
    reverse        name\\mumble\\bar  name\\mumble\\quux
    post-forward   name|bar/mumble  name|quux/mumble
    post-forward-angle-brackets   name<bar/mumble>  name<quux/mumble>
!   nil            name  name<2>
! 
! This variable only takes effect when uniquify.el is loaded.  If you set
! this variable in your .emacs, also specify `(require 'uniquify)'.
! Setting this variable through Custom automatically loads uniquify.el if it
! is not already loaded."
    :type '(radio (const forward)
  		(const reverse)
  		(const post-forward)
============================================================

Re: uniquify-buffer-name-style

[Richard Stallman]

It seems to me that adding a simple hook (abnormal) for
Fcreate_file_buffer and Frename_buffer to call could make it possible
to eliminate that defadvice, and then it would be easy to fix this
bug.

It could be tricky figuring out the right calling conventions for the
hook functions so that a single hook could do for both
Fcreate_file_buffer and Frename_buffer, and still be simple.

If we don't do this, we can document the problem, but the text you
wrote is terribly ambiguous.  In fact, I am not sure what it means.

Do you mean that:

    If you set the variable directly before uniquify is loaded,
    it won't have any effect.

Or do you mean that:

    If you set this variable when uniquify is already loaded,
    it won't have any effect unless you reload uniquify.

Re: uniquify-buffer-name-style

[Luc Teirlinck]

Richard Stallman wrote:

   If we don't do this, we can document the problem, but the text you
   wrote is terribly ambiguous.  In fact, I am not sure what it means.

If uniquify is already loaded, setting the variable takes effect immediately.
Otherwise, it only takes effect once uniquify is loaded.

Sincerely,

Luc.

Re: uniquify-buffer-name-style

[Richard Stallman]

    If uniquify is already loaded, setting the variable takes effect immediately.
    Otherwise, it only takes effect once uniquify is loaded.

Please say that in the text.