ian martins writes:
> Thanks for explaining. That makes sense.
>
> I'm hesitant to add the compile-only header for a couple reasons. Generally
> C-c C-c on a source block means "run this" but with compile-only it'll mean
> "run this but don't run it." It's semantically inconsistent. Also I want
Thanks for explaining. That makes sense.
I'm hesitant to add the compile-only header for a couple reasons. Generally
C-c C-c on a source block means "run this" but with compile-only it'll mean
"run this but don't run it." It's semantically inconsistent. Also I want to
bring more feature parity to
Hey Ian,
Thank you for the quick feedback!
That workflow seems to work perfectly if it's Java all the way. Then it
compiles all the related files. I am mostly working with the classes
from Clojure.
Here is an example:
#+HEADER: :classname se/my_test_package/Hey
#+HEADER: :compile-only t
Hi John,
Thanks for the suggestion and patch. Is the reason for this so that you can
have classes without needing dummy "main" methods?
Did you consider using org-babel-tangle to generate the source files? This
works for me:
Steps:
1. put javatangle.org (below) on your local.
2. create "pkg" dir
Hey Ian!
Happy to see you as the maintainer of the ob-java!
I would like to propose a feature to ob-java. The feature allows a
source code block to write and compile only, without executing.
Here is a common use case for me.
Class without a entry point have an :compile-only header.
#+HEADE
