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: Thu, 25 Jan 2018 21:12:34 +0800 [thread overview]
Message-ID: <CAL1eYuJ5tVyYbFJOCs2kvun3B1hDSDC5PQ6iAaZb3Xcf9Rqihw@mail.gmail.com> (raw)
In-Reply-To: <87mv13cr2w.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]
I see. Seems current ob-core.el can filter out the `src-coderef`.
Like the following:
#+begin_src emacs-lisp
(prin1 "hello, world!") (ref:hello)
#+end_src
#+RESULTS[<2018-01-25 20:28:40> 16eccfedcc87d3ca0c7024b2637c646d4708ec42]:
: hello, world!
#+begin_src ruby :results output
puts "hello, world!" (ref:hello)
#+end_src
#+RESULTS[<2018-01-25 20:46:21> e1e8632ccedf7cc3c676be0c89841a885bbcc7d9]:
: hello, world!
But about your questions:
> What it the comment syntax is not properly defined?
I think almost all programming language has comments. About some other
babels which don't have comment. I think `org-babel` can check whether
babel language has comment.
> What if the coderef format already contains comment syntax?
`org-babel` already use current coderef format. Keep current coderef format
is fine. If coderef format is like `#ref:label`. and Ruby language use
comment `#` too. Then after prepending comment char, it becomes `#
#ref:label`. It is fine. Right?
> What if the language does not support inline comments and you're in the
middle of a line?
It is fine too. Current coderef already support insert coderef format at
right align even I'm in the middle of a line. I tested.
All your questions solved.
My wanted feature is simple, just `(insert (concat comment-char
coderef-format))`
[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 Wed, Jan 24, 2018 at 9:40 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> "numbchild@gmail.com" <numbchild@gmail.com> writes:
>
> > I think this function should be in Org-mode itself.
> > Because when you're editing the source code, will not want this
> src-coderef
> > like `(ref:example)` be editable. It should be in comment.
>
> Thank you for the suggestion. However I have some doubts about this.
>
> What it the comment syntax is not properly defined? What if the coderef
> format already contains comment syntax? What if the language does not
> support inline comments and you're in the middle of a line (e.g.,
> FORTRAN)?
>
> I'm wondering if this is really a panacea. The current situation, albeit
> imperfect, is simple and easy to understand.
>
> WDYT?
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 4079 bytes --]
next prev parent reply other threads:[~2018-01-25 13:13 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 [this message]
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
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=CAL1eYuJ5tVyYbFJOCs2kvun3B1hDSDC5PQ6iAaZb3Xcf9Rqihw@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).