From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [Babel] Arguments...
Date: Wed, 01 Dec 2010 07:50:12 -0700 [thread overview]
Message-ID: <87ipzdfsyj.fsf@gmail.com> (raw)
In-Reply-To: <80pqtllmzz.fsf@missioncriticalit.com> ("Sébastien Vauban"'s message of "Wed, 01 Dec 2010 13:02:24 +0100")
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> Hi Eric,
>
> "Eric Schulte" wrote:
>> Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
>>> The variables are not exported to HTML (and LaTeX?), making the readability
>>> of such a documented code a bit difficult. Feature or bug?
>>
>> The variable names should be exported to both HTML and LaTeX (when
>> org-export-latex-listings is set to true) when the following declaration
>> schema is used (at least they are for me).
>>
>> #+source: something(x=9)
>> #+begin_src emacs-lisp
>> x
>> #+end_src
>
> I confirm that variable names are not exported when they don't get a value,
> such as here:
>
> #+source: add-column-in-table(table, column, type, nullability)
> #+begin_src sql
> -- add column `$column' (if column does not exist yet)
> IF NOT EXISTS (SELECT *
> FROM INFORMATION_SCHEMA.COLUMNS
> WHERE TABLE_NAME = '$table'
> AND COLUMN_NAME = '$column')
> BEGIN
> ALTER TABLE $table
> ADD $column $type $nullability
> END
> #+end_src
>
Ah, That is the problem.
Babel currently only support variable names *with* default values. This
simplifies our internal variable handling. I agree that in the future
it would be good to allow variable names which don't have default values
specified but currently all behavior is undefined when variables
definitions don't have an assignment.
I'm noting this with our variable-handling related development tasks.
Best -- Eric
prev parent reply other threads:[~2010-12-01 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 16:50 [Babel] Arguments Sébastien Vauban
2010-11-05 21:42 ` Eric Schulte
2010-12-01 12:02 ` Sébastien Vauban
2010-12-01 14:50 ` Eric Schulte [this message]
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=87ipzdfsyj.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).