From: Ihor Radchenko <email@example.com>
To: Zelphir Kaltstahl <firstname.lastname@example.org>
Cc: Bruno Barbier <email@example.com>,
firstname.lastname@example.org, Bastien <email@example.com>
Subject: Re: [PATCH] lisp/ob-scheme.el
Date: Sun, 26 Mar 2023 09:32:19 +0000 [thread overview]
Message-ID: <87a5zzvows.fsf@localhost> (raw)
Zelphir Kaltstahl <firstname.lastname@example.org> writes:
>>> + "Expand :var header arguments given as VARS."
>>> + (mapconcat
>>> + (lambda (var)
>>> + (format "(define %s %S)" (car var) (cdr var)))
>> Is there any reason why you use %s for variable name? Previously it was
>> formatted with escapes (using %S).
> That was me thinking: "The name of the variable should just be itself, not
> wrapped in double quotes, because in Scheme I cannot create a variable as
> (define "abc" 123)". But maybe I misunderstood %s and %S. I also do not know,
> how elisp's `print' treats its arguments. Will use 2 times %S then.
The main difference between %S and %s can be demonstrated using the
(insert (format "%s" 'symbol\#w\ spaces))
(insert (format "%S" 'symbol\#w\ spaces))
Basically, if symbol name contains funny chars, reader may need to have
them escaped. %S does the escaping, while %s does not.
Of course, %S escapes according to Elisp reader, not Scheme.
I am not sure if Scheme syntax allows escapes in symbol names.
If not, there should be no real difference.
Also, `print' is the same as %S.
>> Also, previous version quoted the variable value with "'". Why didn't
>> you do it here?
> I am not sure I understand what you are referring to in the previous version. Do
> you mean that `print' quoted variable values with a single quote? Do you mean
> this part of the previous code:
> (print `(,(car var) ',(cdr var)))
Yes, but upon closer look, it should not matter. Your code will work
>>> + (concat (org-babel-expand-header-arg-vars:scheme vars) body))
>> `mapconcat' you used in `org-babel-expand-header-arg-vars:scheme' does
>> not add trailing newline, unlike done previously.
> Am I not adding a newline? I think I do?:
I meant after variable definitions.
(concat (org-babel-scheme-expand-header-arg-vars vars) body)
but string returned by `org-babel-scheme-expand-header-arg-vars' will
not have final newline after the very last define.
> I have a question or suggestion:
> When I save the file in Emacs, my Emacs turns all the tabs in there into spaces.
> Probably my own custom global config's choice about indentation. Could a general
> mode line thing be added to avoid that and nail down the current formatting
> style, so that contributors only need to allow Emacs to run those settings and
> then not need to care about it? Currently the indentation style seems to be a
> mix of tabs and spaces.
This is something about your setup overriding Org mode project defaults.
If you open org-mode/.dir-locals.el, you will see that we enable
indent-tabs-mode. If you still do not get it enabled, you probably
set indentation defaults aggressively it in your config via hooks or
> And one more question:
> Does the name of the patch file matter? Git changed the name and I will attach
> it as it was created by git. Hope that's alright.
Patch file name does not matter.
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-03-26 9:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 11:27 org-babel guile source block bug in handling multiple values Zelphir Kaltstahl
2023-03-07 14:36 ` Ihor Radchenko
2023-03-07 15:18 ` Zelphir Kaltstahl
2023-03-07 19:52 ` Bruno Barbier
2023-03-08 0:55 ` Zelphir Kaltstahl
2023-03-08 19:38 ` Bruno Barbier
2023-03-09 0:44 ` Zelphir Kaltstahl
2023-03-09 13:04 ` [BUG] Inconsistent global/local :var assignments in ob-* for lisps and non-lisps (was: org-babel guile source block bug in handling multiple values) Ihor Radchenko
2023-03-10 10:39 ` Zelphir Kaltstahl
2023-03-11 9:58 ` Ihor Radchenko
2023-03-11 18:30 ` Zelphir Kaltstahl
2023-03-12 11:33 ` Ihor Radchenko
2023-03-19 13:50 ` [PATCH] lisp/ob-scheme.el Zelphir Kaltstahl
2023-03-22 10:43 ` Ihor Radchenko
2023-03-25 14:34 ` Zelphir Kaltstahl
2023-03-26 9:32 ` Ihor Radchenko [this message]
2023-04-25 12:28 ` Ihor Radchenko
2023-04-29 11:08 ` Zelphir Kaltstahl
2023-03-09 13:10 ` org-babel guile source block bug in handling multiple values Ihor Radchenko
2023-03-10 10:42 ` Zelphir Kaltstahl
2023-03-11 10:18 ` Ihor Radchenko
2023-06-02 13:11 ` Ihor Radchenko
2023-03-09 13:11 ` Ihor Radchenko
2023-03-09 14:21 ` Daniel Kraus
2023-03-10 11:57 ` Ihor Radchenko
2023-03-10 10:45 ` Zelphir Kaltstahl
2023-03-08 1:13 ` Zelphir Kaltstahl
2023-03-08 8:55 ` Ihor Radchenko
2023-03-07 15:44 ` Max Nikulin
2023-03-07 21:41 ` Rudolf Adamkovič
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).