Re: [O] Buffer local alias?

[Andreas Leha]

address@hidden (Thomas S. Dye) writes:

> Bastien <address@hidden> writes:
>
>> Nick Dokos <address@hidden> writes:
>>
>>> Use fboundp, instead of boundp: the latter checks the variable binding
>>> slot, whereas the former checks the function binding slot.
>>
>> Also, I thought sbe was unknown enough to rename it directly
>> instead of creating an alias.  If many people are using sbe,
>> maybe an alias is better -- but I'd rather not to add it.
>
> Thanks Nick. This works:
>
>   * Local variables                                                  
> :noexport:
>
>   # Local Variables:
>   # eval: (and (fboundp 'org-sbe) (not (fboundp 'sbe)) (fset 'sbe 'org-sbe))
>   # eval: (sbe "setup-common-lisp")
>   # End:
>
> Bastien, for my use case there is no reason to define an alias.

I am in favor of such an alias.  In that particular case it seems that
it would not hurt much (IMO) and it would increase backward
compatibility.


Let me take the opportunity to sigh a little bit:

I am not as organized as Tom is.  So the chances to use my up-to-date
orgmode and successfully export any of my org documents from a year ago
(they are almost all 'Literate Programming' documents and, thus, maybe
more fragile?) are slim.  I do not have numbers, but it seems like I'll
need to adapt such documents all the time.

I know that this problem is a problem of balancing backward
compatibility with new features, better design, etc and cannot be
solved.  And I see the win in (most of) the breaking changes.

But let me just express my vote for even more awareness of people like
me, who do not read all release notes, forget most of the messages from
the mailing list and as a result need 2 hours to export some document
from last year again today.

A change like this one (renaming sbe to org-sbe) is a small change and
will only be an annoyance in one years time.  The drop of the implicit
naming of call lines, for example, was (and still will be for some of my
files) a bigger issue.


Regards,
Andreas