From: Jay Kamat <jaygkamat@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Support for 'using namespace *' in ob-C.el
Date: Tue, 1 Aug 2017 18:40:06 -0700 [thread overview]
Message-ID: <CACe_Yv9veQVmLohes9Zr0psdhiX_0h24jFchNyih=VjdQofc8Q@mail.gmail.com> (raw)
In-Reply-To: <87379bs07v.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hi Nicolas,
Sorry for bumping this, but could you apply the patch I made to update
worg for documentation as well (or provide feedback)? I'd like that to
stay updated as well if possible.
If there's another mailing list for worg let me know and I'll post it there.
The patch is re-attached for convenience.
-Jay
On Tue, Aug 1, 2017 at 9:48 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Jay Kamat <jaygkamat@gmail.com> writes:
>
>> From 65c8add92842c2e547b13d5c6fb2485e7fdbf2db Mon Sep 17 00:00:00 2001
>> From: Jay Kamat <jaygkamat@gmail.com>
>> Date: Mon, 31 Jul 2017 22:47:33 -0700
>> Subject: [PATCH] ORG-NEWS: Fix a small typo in new org babel header example
>>
>> * etc/ORG-NEWS (Using): Fix typo in babel :header-args: conversion
>>
>> TINYCHANGE
>
> Applied. Thank you.
>
> Regards,
> --
> Nicolas Goaziou
[-- Attachment #2: 0001-Add-documentation-for-ob-C-namespaces.patch --]
[-- Type: application/octet-stream, Size: 1153 bytes --]
From 3267aeac0b90c76f5091104e13389ce6050dd580 Mon Sep 17 00:00:00 2001
From: Jay Kamat <jaygkamat@gmail.com>
Date: Sun, 16 Jul 2017 22:09:06 -0700
Subject: [PATCH] Add documentation for ob-C :namespaces
---
org-contrib/babel/languages/ob-doc-C.org | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/org-contrib/babel/languages/ob-doc-C.org b/org-contrib/babel/languages/ob-doc-C.org
index b1aac99b..faf2b77f 100644
--- a/org-contrib/babel/languages/ob-doc-C.org
+++ b/org-contrib/babel/languages/ob-doc-C.org
@@ -66,7 +66,7 @@ the results of evaluation inserted into the buffer.
: int b=1;
: printf("%d\n", a+b);
: #+end_src
-:
+:
: #+results:
: : 2
@@ -154,6 +154,11 @@ It features:
(C & C++ only) just like =:includes= but for =#defines= lines at the
top of the code.
+- =:namespaces= ::
+ (C++ only)
+ accepts either a single name, or a list of names of namespaces to use.
+ The final format will look like this: =using namespace name;=
+
- =:libs= ::
(C & C++ only) useful for linking with a library, may be given
=-L/path/to/lib= and =-llibrary= instructions.
--
2.11.0
next prev parent reply other threads:[~2017-08-02 1:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 5:31 [PATCH] Support for 'using namespace *' in ob-C.el Jay Kamat
2017-07-23 14:44 ` Nicolas Goaziou
2017-07-31 8:03 ` Jay Kamat
2017-07-31 15:34 ` Charles C. Berry
2017-08-01 5:54 ` Jay Kamat
2017-08-01 16:48 ` Nicolas Goaziou
2017-08-01 16:48 ` Nicolas Goaziou
2017-08-02 1:40 ` Jay Kamat [this message]
2017-08-02 6:49 ` Nicolas Goaziou
2017-08-01 8:22 ` 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='CACe_Yv9veQVmLohes9Zr0psdhiX_0h24jFchNyih=VjdQofc8Q@mail.gmail.com' \
--to=jaygkamat@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).