Hello,
I believe I've hit a strange bug. Given this file:
------
#+STARTUP: content indent hideblocks
#+PROPERTY: header-args :tangle yes
#+PROPERTY: header-args:python :session *Python*
#+NAME: python_init
#+BEGIN_SRC python
I am writing this interface to my university's learning management system:
https://github.com/titaniumbones/Org-Marking-Mode/tree/use-structured-course-def.
I am only using hte exporting system tangentially and I have not defined a
new exporter. However, I would really like to be able to set some v
THanks John. I guess I should always just start my search for "something
cool I saw" in scimax...
Yes, thisis pretty great. I havebeen using ~helpful~ which hasa nice
interface for some extra functions, but these functions do most of what I
felt was missing.
On Thu, Nov 8, 2018 at 6:02 PM John Ki
On Thu, Nov 8, 2018 at 9:26 AM Nicolas Goaziou
wrote:
>
> I know. I can reproduce your problem. But I know nothing about ODT, so
> it would help if you could tell me what should be the desired output. At
> the moment, referencing anything else than a headline or a target is
> unsupported in this
I wrote something kind of like this at
https://github.com/jkitchin/scimax/blob/master/scimax-literate-programming.el
It might solve a different problem related to navigating code embedded in
org files.
I don't think it works on describe-function. That would be an interesting
addition perhaps. I
I feel like I saw someone do this but can't find it in my notes. When
tangling code to elisp, is it possible to point ~describe-function~ to the
original org-mode source (or at least the src block) as the "source code"
for the function, rather than the resultant .e file produced by
org-babel-tangle
Nicolas Goaziou writes:
> Hello,
>
> Ken Mankoff writes:
>
>> On Mon, Nov 5, 2018, 13:59 Nicolas Goaziou >
>>>
>>> What would be the expected output?
>>>
>>
>> There is no output. It doesn't even export. It's a showstopper. No
>> references to equations allowed or the exporter fails.
>
> I know.
Hello,
Samuel Wales writes:
> i also call them event.
>
> i have code below that shows them in agenda as "Event:" in their own face.
>
> i think there was a proposal a while back to have them be in the
> planning line [the one just after the header] as EVENT: <...> along
> with closed, scheduled
Hello,
Ken Mankoff writes:
> On Mon, Nov 5, 2018, 13:59 Nicolas Goaziou
>>
>> What would be the expected output?
>>
>
> There is no output. It doesn't even export. It's a showstopper. No
> references to equations allowed or the exporter fails.
I know. I can reproduce your problem. But I know n
Hello,
Omari Norman writes:
> I am having a problem with group tags. I reproduced it using the latest
> org-mode from the org package archive, 20181022. The minimal example is
> this: say I have a group tag that looks like this:
>
> (setq org-tag-alist
> '((:startgrouptag)
> ("pare
10 matches
Mail list logo
