[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: make-variable-buffer-local change

From: Dan Nicolaescu
Subject: Re: make-variable-buffer-local change
Date: Fri, 25 Sep 2009 12:46:32 -0700 (PDT)

Juanma Barranquero <address@hidden> writes:

  > On Fri, Sep 25, 2009 at 19:07, Dan Nicolaescu <address@hidden> wrote:
  > > "All packages that assign it"
  > Of course. For packages that read it, they only want to find the right
  > (local) value, or nil when it has not been assigned.
  > > It is globally assigned to nil.
  > That's the default. Every buffer-local variable has a global default.
  > Surely you're not implying that is a reason for assigning it globally.
  > > All buffers that don't set it explicitly use the global nil value.
  > All buffers that don't set it explicitly don't use it. All packages
  > that don't set it but read it expect it to be locally set (or globally
  > nil).
  > > Isn't it slightly more efficient to access global bindings than buffer
  > > local bindings, so forcing `make-variable-buffer-local' will force this
  > > inefficiency everywhere.
  > Sorry, I think I'm not understanding your point. The packages that

My point is that it is cheaper to make this variable buffer local
exactly in the buffers that need to have it buffer local, rather than
making it buffer local in all buffers. 

What this discussion points out is that it would be good to have a
clarification of the use of make-variable-buffer-local vs
make-local-variable in the docstring of one (or both) of them.  Stefan?

  > > IMHO the first thing to do there is to decide if this is a problem with
  > > uniquify, or if it's just working as expected.  (no idea here).
  > If you create a buffer *vc-dir* with working dir /emacs/lisp, and
  > another with working dir /emacs/src, one of the *vc-dir* buffers will
  > have a value for uniquify-managed and the other will not. That cannot
  > be right.

That's just a restatement of the facts, I am looking for an analysis of
the cause of issue.  Like, is this a bug in uniquify?  Or is uniquify
working as expected, but it needs extra hand holding to do the right
thing?  Something else?...

reply via email to

[Prev in Thread] Current Thread [Next in Thread]