From: "numbchild@gmail.com" <numbchild@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [feature] prepend comment char before org-babel-ref
Date: Sun, 28 Jan 2018 17:52:13 +0800 [thread overview]
Message-ID: <CAL1eYu+8jNm_RqF8g4NQue+RCmE-yMBzKO4WE7Di-_jQ+AhU8g@mail.gmail.com> (raw)
In-Reply-To: <87607ntvos.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
Thanks. @Nicolas
[stardiviner] <Hack this world!> GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
On Sat, Jan 27, 2018 at 6:58 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
> > Hello,
> >
> > "numbchild@gmail.com" <numbchild@gmail.com> writes:
> >
> >> Because it is not good for tangling.
> >> For example, tangle the bellowing src block, the tangled source code
> file
> >> will has `(ref:hello)` too.
> >> ```
> >>
> >> #+begin_src emacs-lisp :tangle "data/code/src-coderef.el"
> >> (message "hello, world") (ref:hello)
> >> #+end_src
> >
> > You need to add "-r" switch so Org knows you want to remove coderefs:
> >
> > #+begin_src emacs-lisp :tangle "data/code/src-coderef.el"
> > (message "hello, world") (ref:hello)
> > #+end_src
>
> I meant
>
> #+begin_src emacs-lisp -r :tangle "data/code/src-coderef.el"
> ^^^^
>
[-- Attachment #2: Type: text/html, Size: 2125 bytes --]
prev parent reply other threads:[~2018-01-28 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 4:24 [feature] prepend comment char before org-babel-ref numbchild
2018-01-24 13:40 ` Nicolas Goaziou
2018-01-25 13:12 ` numbchild
2018-01-25 20:19 ` Nicolas Goaziou
2018-01-26 12:34 ` numbchild
2018-01-26 12:35 ` numbchild
2018-01-27 10:56 ` Nicolas Goaziou
2018-01-27 10:58 ` Nicolas Goaziou
2018-01-28 9:52 ` numbchild [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=CAL1eYu+8jNm_RqF8g4NQue+RCmE-yMBzKO4WE7Di-_jQ+AhU8g@mail.gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).