From: Jambunathan K <kjambunathan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BABEL][PROPOSAL] headlines as executable srcnames
Date: Mon, 20 Sep 2010 13:09:48 +0530 [thread overview]
Message-ID: <81pqw8oocb.fsf@gmail.com> (raw)
In-Reply-To: <87r5gpcb9c.fsf@gmail.com> (Eric Schulte's message of "Sun, 19 Sep 2010 22:03:11 -0600")
Eric
> Hi Jambunathan,
>
> So, if I'm understanding correctly, what you are proposing includes two
> separate things, first, a new link-style syntax for calling code blocks,
> and second, the ability to provide un-named arguments to code blocks.
>
> I'm less sure about expanding link syntax into a means of calling code
> blocks. There has been some recent discussion on the list about
> expanding link syntax (in fact related to the thread your referenced
> below) and my impression was that there is far from unanimous support
> for changing the semantics of links in Org-mode. Maybe this would be
> appropriate as an optional extension to org, i.e. something in the
> contrib directory.
>
I think I am converging towards having a new 'babel: ' URL scheme.
Requests like colorization, inserting version control information etc on
export rightfully falls under one-off request and a babel: URL scheme
would help achieve all these without any hassles.
In 'babel: ' URLs, the 'path' param is likely to contain a call-site
(srcname) and key,val pairs (for named params). I think one can use or
draw inspiration from standard http URL encoders that posts HTML forms.
My ideas are not fully formed and I refine as I go along... Please be
tolerant.
Jambunathan K.
>> ,----
>> | "*Article*" #("From: Vinh Nguyen <vinhdizzo@gmail.com>
>> | Subject: Re: text color + highlight
>> | Newsgroups: gmane.emacs.orgmode
>> | To: emacs-orgmode@gnu.org
>> | Date: Thu, 9 Sep 2010 09:15:05 -0700
>> | Message-ID: <AANLkTinr_ZoRpygJPkSkYUo6pt1t3-ztOtHo32fnhscd@mail.gmail.com>
>> | Archived-At: <http://permalink.gmane.org/gmane.emacs.orgmode/30143>
>> |
>> | I'd like to write a concluding email for this thread for future
>> | searchers to find. This easy solution is brought to you by Eric
>> | Schulte and Christian Moe.
>> |
>> | Place the following in your .emacs or init.el file:
>> | ;; org-mode color
>> | (org-add-link-type
>> | \"color\" nil
>> | (lambda (path desc format)p
>> | (cond
>> | ((eq format 'html)
>> | (format \"<span style=\\\"color:%s;\\\">%s</span>\" path desc))
>> | ((eq format 'latex)
>> | (format \"{\\\\color{%s}%s}\" path desc)))))
>> | ;; org-mode highlight
>> | (org-add-link-type
>> | \"hl\" nil
>> | (lambda (path desc format)
>> | (cond
>> | ((eq format 'html)
>> | (format \"<font style=\\\"background-color:%s;\\\">%s</font>\" path desc))
>> | ((eq format 'latex)
>> | (format \"\\\\colorbox{%s}{%s}\" path desc))))) ;; require \\usepackage{color}
>> |
>> | Examples:
>> | [[color:blue][test this out]]
>> | [[hl:yellow][highlighted text]]
>> |
>> `----
next prev parent reply other threads:[~2010-09-20 7:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 11:36 Composing letters using Org mode and the LaTeX isodoc class Sébastien Vauban
2010-09-07 18:46 ` Jambunathan K
2010-09-07 19:45 ` Sébastien Vauban
2010-09-08 0:56 ` Eric Schulte
2010-09-08 1:52 ` Thomas S. Dye
2010-09-08 4:39 ` Jambunathan K
2010-09-08 11:48 ` Sébastien Vauban
2010-09-08 15:15 ` Eric Schulte
2010-09-08 16:22 ` [BABEL][PROPOSAL] headlines as executable srcnames Jambunathan K
2010-09-08 21:30 ` Sébastien Vauban
2010-09-09 15:38 ` Jambunathan K
2010-09-09 16:30 ` Jambunathan K
2010-09-10 4:51 ` Jambunathan K
2010-09-20 4:03 ` Eric Schulte
2010-09-20 7:39 ` Jambunathan K [this message]
2010-09-20 4:15 ` Eric Schulte
2010-09-08 11:45 ` Composing letters using Org mode and the LaTeX isodoc class Sébastien Vauban
2010-09-08 15:38 ` Eric Schulte
2010-09-08 21:26 ` Sébastien Vauban
2010-09-10 8:51 ` Eric S Fraga
2010-09-10 9:13 ` Sébastien Vauban
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=81pqw8oocb.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).