Hi Martyn,
Martyn Jago martyn.j...@btinternet.com writes:
The FSF process is in progress - I'm currently waiting for the agreement
to sign. I'll tidy up the YAML export.
I confirm the assignment/disclaimer process with the FSF is complete.
I added you to the list of contributors on Worg:
Eric Schulte schulte.e...@gmail.com writes:
Martyn Jago martyn.j...@btinternet.com writes:
Eric Schulte schulte.e...@gmail.com writes:
[...]
Hi Martyn,
That's great news. A just had trouble trying to apply your earlier
patch, could you reproduce the patch with
git diff cpp.patch
Bastien bastien.gue...@wikimedia.fr writes:
Hi Martyn,
Martyn Jago martyn.j...@btinternet.com writes:
The FSF process is in progress - I'm currently waiting for the agreement
to sign. I'll tidy up the YAML export.
I confirm the assignment/disclaimer process with the FSF is complete.
I
[...]
Hi Eric
Apologies, I'm still familiarising myself with Gnus but hopefully this
will work.
Worked perfectly, this is now applied thanks.
Also thanks for Babel, I think its got a great future!
With engaged users sending in patches and improvements I'm sure it will.
Thanks! -- Eric
Eric Schulte schulte.e...@gmail.com writes:
[...]
Hi Martyn,
Thanks for sharing this patch, it looks great. Also, I would love to
include your YAML support. It's better to have partial YAML support
than none, and any skeleton can serve as the foundation for more
sophisticated support.
Martyn Jago martyn.j...@btinternet.com writes:
Eric Schulte schulte.e...@gmail.com writes:
[...]
Hi Martyn,
Thanks for sharing this patch, it looks great. Also, I would love to
include your YAML support. It's better to have partial YAML support
than none, and any skeleton can serve as
[...]
Hi
After further inspection and testing the following patch is more
complete (apologies for the noise).
In addition I have a very simple Yaml template if it is of any interest
to anybody. I have a strong use case for tangling Yaml for 'literate
configuration' purposes since I come
Martyn Jago martyn.j...@btinternet.com writes:
Hi
I've noticed a couple of minor inconsistencies with C++ export...
- According to the Org manual (section 14.7 Languages) the identifier
for C++ is C++ (upper-case), but in practice this fails and the
identifier c++ (lower-case) must
