Kyle Meyer writes:
> I've sat down to work on it a few times and wasn't able to get anywhere
> with the time I had available. It's on my list to revisit. However, as
> we have no proposed fix, in my view it'd make sense to revert the
> problematic commit, 39c656870. While that recent commit
org-get-outline-path ;)
George Mauer writes:
> I feel silly that I can’t figure this out but how do I get the current
> heading, its parent, its parent parent, etc via elisp?
--
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key
Ok... just reporting back my progress in case it helps someone else. Bur
first, all the stuff that you can do with src blocks is stuff I never
imagined. Seems like the possibilities are endless. Here is what I did so
far:
#+NAME: simulation
#+HEADER: :var cap="DEFAULTCAPTION" :cache yes :eval
How about this:
Add key binding for converting org mode to Confluence wiki, i.e.,
'C-x C-e f f' converts current org buffer to a temporary buffer
holding Confluence wiki markup.
This key binding takes effect only when org-confluence.el file
in contrib directory is loaded first.
On Sat, Apr 11, 2020 at 5:43 PM wrote:
...
> Well, that depends on your target. If you aim for CSL than that's already
> fairly complete. (Even it's more than complete since the current CSL
> specification only knows normal citations. Suppressing authors is done by
> calling applications, and
Hi,
> Let's assume Org implements SuppressAuthor as "-@doe", so far it has:
>
> | Syntax| Mode| Sample output
> |
> |---+-+---|
> | @doe or [cite:@doe] | AuthorInText
Hello,
Richard Kim writes:
> I would like to suggest the following patch so that I can easily export
> to Confluence wiki format using the usual org-mode export mechanism.
Sure. Could you write a proper commit message and send it again?
Thank you.
Regards,
--
Nicolas Goaziou
I feel silly that I can’t figure this out but how do I get the current
heading, its parent, its parent parent, etc via elisp?
Hello,
stardiviner writes:
> I think the hidden drawers info is useful for users, this should be
> shown when org-cycle on headlines.
Doesn't this defeat the whole purpose of drawers? What problem do you
want to solve?
Regards,
--
Nicolas Goaziou
On Wed, Apr 8, 2020, 5:32 AM Nicolas Goaziou wrote:
[snip]
> Sounds like a plan. Let me summarize it a bit :
>
> 1. [ ] Finalize Org citation syntax. It is mostly good, but we need to
>decide about the following points:
>
>- [ ] Should it include both "(cite):" and "cite:", i.e., does
Alright, I see. Thanks for the explanations!
сб, 11 апр. 2020 г. в 03:40, Kyle Meyer :
>
> Dmitrii Korobeinikov writes:
>
> >> That seems confusing to me as well (at least being the not-advanced
> >> clocker that I am). I suspect the confusion comes from the different
> >> perspective from
I think the hidden drawers info is useful for users, this should be
shown when org-cycle on headlines.
Here is the patch.
--
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner,
12 matches
Mail list logo
