From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel] Arguments...
Date: Fri, 05 Nov 2010 15:42:54 -0600 [thread overview]
Message-ID: <87zktnphtx.fsf@gmail.com> (raw)
In-Reply-To: 804obvyas7.fsf@mundaneum.com
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
> Hello,
>
> Two small questions, with that minimal example:
>
> #+begin_src org
> ,* Database
> ,
> ,** Back up the database
> ,
> ,Create a backup file of the existing database:
> ,
> ,#+srcname: backup-db(dbName, dbBackupFile)
> ,#+begin_src sql
> ,BACKUP DATABASE dbName TO DISK = 'dbBackupFile'
> ,go
> ,#+end_src
> ,
> ,** Back up the database
> ,
> ,Create a backup file of the existing database:
> ,
> ,#+srcname: backup-db :var dbName :var dbBackupFile
> ,#+begin_src sql
> ,BACKUP DATABASE dbName TO DISK = 'dbBackupFile'
> ,go
> ,#+end_src
> #+end_src
>
> 1. I read on http://orgmode.org/manual/var.html that the second way to pass
> arguments is "more natural". Though, "nobody" "never" uses it in all the
> examples published on this ML. Why? Are there still subtle differences, or
> could such come in the future that would make one choose one over the
> other?
>
I think we are committed to maintaining both ways of defining variables
for code blocks for the foreseeable future.
>
> 2. In both cases, 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
Best -- Eric
>
> Best regards,
> Seb
next prev parent reply other threads:[~2010-11-05 21:43 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 [this message]
2010-12-01 12:02 ` Sébastien Vauban
2010-12-01 14:50 ` Eric Schulte
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=87zktnphtx.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).