From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Buffer local alias?
Date: Tue, 14 Jan 2014 22:49:30 +0100 [thread overview]
Message-ID: <87wqi2xmhh.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: m1a9eyxqzl.fsf@poto.myhome.westell.com
tsd@tsdye.com (Thomas S. Dye) writes:
> Bastien <bzg@gnu.org> writes:
>
>> Nick Dokos <ndokos@gmail.com> 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
next prev parent reply other threads:[~2014-01-14 21:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 19:00 Buffer local alias? Thomas S. Dye
2014-01-14 19:39 ` Nick Dokos
2014-01-14 19:44 ` Bastien
2014-01-14 20:12 ` Thomas S. Dye
2014-01-14 21:49 ` Andreas Leha [this message]
2014-01-15 0:05 ` Thomas S. Dye
2014-01-15 8:41 ` Andreas Leha
2014-01-15 8:51 ` Eric S Fraga
2014-01-15 9:33 ` Sebastien Vauban
2014-01-15 9:50 ` Andreas Leha
2014-01-15 19:59 ` Achim Gratz
2014-01-15 20:40 ` Andreas Leha
2014-01-16 16:44 ` Achim Gratz
2014-01-16 16:54 ` Rick Frankel
2014-01-16 17:51 ` Thomas S. Dye
2014-01-15 9:30 ` Sebastien Vauban
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqi2xmhh.fsf@med.uni-goettingen.de \
--to=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).