From: Eric Schulte <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org, Jambunathan K <kjambunathan@gmail.com>
Subject: Re: [bug] Code snippets are not getting numbered
Date: Tue, 28 Jan 2014 14:24:05 -0700 [thread overview]
Message-ID: <87txcn4q2j.fsf@gmail.com> (raw)
In-Reply-To: 87mwifhkvx.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> Code snippets are not getting numbered... Also take a look at
>> `org-export-resolve-coderef'.
>>
>> The below example is from (info "(org) Literal examples")
>>
>> #+BEGIN_SRC emacs-lisp -n -r
>> (save-excursion (ref:sc)
>> (goto-char (point-min)) (ref:jump)
>> #+END_SRC
>>
>> In line [[(sc)]] we remember the current position. [[(jump)][Line (jump)]]
>> jumps to point-min.
>
> Thank you for reporting it.
>
> The problem is one week old (dde6af3a6230b37aabfb4f75c2dee89433958375).
> When trying to fix something I broke another part.
>
> IIUC, there are two "flags" types in `org-babel-exp-code'. One is
> the :flags parameter and the other one are the switches of the source
> block. Unfortunately, you can have only one at a time since they are
> stored in an alist (the first one shadows the other one).
>
> I think a correct solution would be to rename switches "switches" and
> add them to `org-babel-exp-code-template'.
>
> Eric, what do you think?
>
That sounds reasonable to me.
>
>
> Regards,
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2014-01-29 0:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 9:37 [bug] Code snippets are not getting numbered Jambunathan K
2014-01-28 20:22 ` John Kitchin
2014-01-28 21:11 ` Nicolas Goaziou
2014-01-28 21:24 ` Eric Schulte [this message]
2014-01-29 8:08 ` Nicolas Goaziou
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=87txcn4q2j.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kjambunathan@gmail.com \
--cc=n.goaziou@gmail.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).