From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ken Raeburn To: rms@gnu.org Cc: guile-emacs@sourceware.cygnus.com Subject: Re: guile-emacs-0.1 released Date: Sun, 07 Jan 2001 13:28:00 -0000 Message-id: <200101072128.QAA10694@raeburn.org> References: <200003170249.TAA03077@aztec.santafe.edu> <200101071713.KAA18087@aztec.santafe.edu> X-SW-Source: 2001-q1/msg00001.html > I am responding to messages that got buried during the year. > Please forgive me for taking so long to respond. It's okay, I know the problem too well.... > It occurs to me now that there's more than one way of interpreting > what you originally said. So I think the useful thing for me to do > is explain what I'm concerned about. Sorry I wasn't more clear about it. Yes, what you describe is what I want to see. What I meant by "interaction of Lisp dynamic bindings...and Scheme lexical bindings" was basically how to set up that interface for Scheme code to access the "current" elisp values, and possibly the reverse. (And the function value of a symbol, etc.) > But whatever mechanism people use in Scheme to make and access > dynamically scoped variables, it should be integrated smoothly with > Emacs buffer-local and frame-local bindings when you use it in Emacs. Yes, the Emacs "current" value would deal with not just the dynamic binding, but also the buffer- and frame-local bindings, falling back to the global Scheme "default" value only if none of the others were in use. Though it may be useful to provide functions to look at each of those separately, for maximum convenience we probably want one or two macros for reading and writing that will just Do The Right Thing for people manipulating the elisp environment from Scheme.