From: Edward Reingold <reingold@iit.edu>
To: Bastien <bzg@gnu.org>
Cc: Chong Yidong <cyd@gnu.org>, emacs-devel@gnu.org
Subject: Re: Evil defvars in org.el
Date: Fri, 27 Apr 2012 09:57:36 -0500 [thread overview]
Message-ID: <CAO_04X5tPJ7QnZ08Pv9KChNP6cBHyJdGOcpOpUkn3-TCujtzxQ@mail.gmail.com> (raw)
In-Reply-To: <87vckls01f.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
Although I no longer maintain the code (and have not for years), my memory
is that many things will break if this is changed willy-nilly. It is part
of the earliest-written (circa 1983), deepest levels of the code, so the
changes will be pervasive, affecting almost every .el file. When I wrote
the code (primarily for my own use and amusement), I saw little choice in
using the mechanism, though I knew it was clunky. Emacs at the time was
MUCH smaller and I knew most of its internals well, so I felt pretty
safe...who'd have guessed how much it would grow over almost 30 years, or
that my code would still be around. Sorry.
On Fri, Apr 27, 2012 at 9:48 AM, Bastien <bzg@gnu.org> wrote:
> Hi Glenn,
>
> Bastien <bzg@gnu.org> writes:
>
> > From latest calendar.el in Emacs:
> >
> > ;; A note on free variables:
> >
> > ;; The calendar passes around a few dynamically bound variables, which
> > ;; unfortunately have rather common names. They are meant to be
> > ;; available for external functions, so the names can't be changed.
> >
> > ;; displayed-month, displayed-year: bound in calendar-generate, the
> > ;; central month of the 3 month calendar window
> > ;; original-date, number: bound in diary-list-entries, the arguments
> > ;; with which that function was called.
> > ;; date, entry: bound in diary-list-sexp-entries (qv)
> > ^^^^ ^^^^^
>
> I'm not entirely sure whether the comment quoted above reflects
> the situation in Calendar's code.
>
> Could you have a look and tell me if something needs to be fixed
> in Calendar?
>
> Thanks!
>
> --
> Bastien
>
>
[-- Attachment #2: Type: text/html, Size: 2134 bytes --]
next prev parent reply other threads:[~2012-04-27 14:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 3:17 Evil defvars in org.el Chong Yidong
2012-04-27 6:07 ` Bastien
2012-04-27 14:48 ` Bastien
2012-04-27 14:57 ` Edward Reingold [this message]
2012-04-27 16:14 ` Bastien
2012-04-27 17:09 ` SAKURAI Masashi
2012-04-27 16:05 ` Glenn Morris
2012-04-27 16:33 ` Drew Adams
2012-04-28 0:15 ` Miles Bader
2012-04-28 0:17 ` Drew Adams
2012-04-28 0:48 ` Miles Bader
2012-04-28 2:25 ` Chong Yidong
2012-05-04 6:56 ` Glenn Morris
2012-05-04 15:29 ` Stefan Monnier
2012-05-04 20:53 ` Johan Bockgård
2012-05-05 0:37 ` Stefan Monnier
2012-05-05 20:00 ` Glenn Morris
2012-05-07 14:57 ` Stefan Monnier
2012-04-28 2:14 ` Stefan Monnier
2012-04-28 5:57 ` Achim Gratz
2012-04-28 15:10 ` Stefan Monnier
2012-04-28 16:31 ` Achim Gratz
2012-04-28 19:33 ` Stefan Monnier
2012-04-28 6:00 ` Drew Adams
2012-05-08 22:48 ` Martyn Jago
2012-05-09 17:37 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO_04X5tPJ7QnZ08Pv9KChNP6cBHyJdGOcpOpUkn3-TCujtzxQ@mail.gmail.com \
--to=reingold@iit.edu \
--cc=bzg@gnu.org \
--cc=cyd@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.