From: Bastien <bzg@gnu.org>
To: "Göktuğ Kayaalp" <self@gkayaalp.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Inheriting some local variables from source code block editing buffers
Date: Mon, 30 Apr 2018 00:09:35 +0200 [thread overview]
Message-ID: <874ljt3bs0.fsf@gnu.org> (raw)
In-Reply-To: <ygmefiy3p88.fsf@gkayaalp.com> ("Göktuğ Kayaalp"'s message of "Sun, 29 Apr 2018 20:19:03 +0300")
Hi Göktuğ,
thanks for your patch.
Kayaalp <self@gkayaalp.com> writes:
> when editing a source block, passing some local variables from the
> original buffer into the buffer in which the source code is edited might
> be useful. My use case is passing the value of ‘lexical-binding’ when
> editing Elisp source code blocks in my literate .emacs so that I don't
> mistakenly evaluate code in a non-lexical environment thinking it's the
> opposite instead.
Yes, I see how this can be useful in this case.
Do you have other examples on local variables that would be useful to
pass on when editing code in Org Src buffers?
> I've implemented this with the patch attached to this message, if it's
> deemed useful, I can revise it for inclusion upstream (just wanted to
> see what you think about the idea with this one).
Note that in the particular case of lexical-binding and emacs-lisp
blocks, there is the :lexical block parameter -- of course, this is
for execution, not edition, but you can use it as a clue on whether
the block supposes lexical binding or not.
In general, instead of inheriting values from the Org's buffer, I'd
allow users to set the values independantly -- for example, the cdr
of elements in `org-babel-load-languages', instead of being `t' all
the time (because nil makes no sense to me), could contain an alist
of variables and their local values when editing and... executing.
This is: *if* we find cases that seem generic enough.
What do you think?
--
Bastien
next prev parent reply other threads:[~2018-04-29 22:09 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-29 17:19 Inheriting some local variables from source code block editing buffers Göktuğ Kayaalp
2018-04-29 22:09 ` Bastien [this message]
2018-05-01 3:30 ` Göktuğ Kayaalp
2018-05-01 8:43 ` Nicolas Goaziou
2018-05-01 8:45 ` Nicolas Goaziou
2018-05-01 11:41 ` Göktuğ Kayaalp
2018-05-01 11:55 ` Nicolas Goaziou
[not found] ` <ygmvac7lcl1.fsf@gkayaalp.com>
2018-05-01 14:00 ` Nicolas Goaziou
2018-05-01 16:37 ` Aaron Ecay
[not found] ` <ygmin87kwua.fsf@gkayaalp.com>
2018-05-01 19:35 ` Aaron Ecay
2018-05-01 20:04 ` Göktuğ Kayaalp
2018-05-01 20:53 ` Aaron Ecay
2018-05-01 22:12 ` Göktuğ Kayaalp
2018-05-01 22:19 ` Aaron Ecay
2018-05-01 22:26 ` Göktuğ Kayaalp
2018-05-02 10:16 ` Nicolas Goaziou
2018-05-02 19:52 ` Göktuğ Kayaalp
2018-05-01 11:45 ` Göktuğ Kayaalp
2018-05-14 5:44 ` Göktuğ Kayaalp
2018-05-14 12:13 ` Nicolas Goaziou
2018-05-14 16:34 ` Göktuğ Kayaalp
2018-05-14 16:47 ` Nicolas Goaziou
2018-05-15 18:36 ` Göktuğ Kayaalp
2018-05-18 21:48 ` Göktuğ Kayaalp
2018-05-19 12:26 ` Nicolas Goaziou
2018-05-21 14:20 ` Aaron Ecay
2018-05-14 13:33 ` Aaron Ecay
2018-05-14 16:46 ` Göktuğ Kayaalp
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=874ljt3bs0.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=self@gkayaalp.com \
/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).