On Friday, 23 Nov 2018 at 08:51, Qiang Fang wrote:
> Hello everyone,
>
> I am a user of kjambunathan's org-mode-ox-odt. The odt exporter needs some
> changed in the upstream org mode. Can you please kindly review the request?
Out of curiosity, what is the effect of this change specifically? What
Hello,
Qiang Fang writes:
> I am a user of kjambunathan's org-mode-ox-odt. The odt exporter needs some
> changed in the upstream org mode. Can you please kindly review the
> request?
You need to pull again "wip-cite" branch. It was rebased against master
yesterday. So was "wip-cite-awe".
Regar
On Thursday, 22 Nov 2018 at 14:09, Matt Price wrote:
> SO far this is working for me but I wondered whether other people would
> similarly want to change this behaviour and I should put together a proper
> proposal & patch?
Yes, please. This is becoming more and more necessary as monitors get
lar
Hello everyone,
I am a user of kjambunathan's org-mode-ox-odt. The odt exporter needs some
changed in the upstream org mode. Can you please kindly review the request?
Thank you so much!
diff --cc lisp/org-element.el
index cdb574e17,f7498fbd1..0
--- a/lisp/org-element.el
+++ b/lisp/org-ele
Hi Org,
Attached is a patch that adds a customization variable,
org-cycle-local-skip-subtree, which, when set to t (nil by default)
will cause the SUBTREE state to be skipped when using org-cycle
locally. All behaviour remains the same by default.
I find the SUBTREE state such an unpleasant exper
On Thu, Nov 22, 2018 at 4:06 PM Matt Price wrote:
>
>
> On Thu, Nov 22, 2018 at 1:19 PM Matt Price wrote:
>
>> It would be nice for me to overlay the macro invocations with the values
>> that they will evaluate to on export. I guess I would have to figure out
>> when to trigger recalculation of
On Thu, Nov 22, 2018 at 1:19 PM Matt Price wrote:
> It would be nice for me to overlay the macro invocations with the values
> that they will evaluate to on export. I guess I would have to figure out
> when to trigger recalculation of the values (maybe not too often, say only
> when the macro is
I've recently switched to using the current window for editing src blocks w
~(setq org-src-window-setup 'current=window)~. I like this a lot, and it
lets me swtich rapidly back and forth between the parent buffer and source
code. Often when I ma working I split some of hte other windows to display
Hi Nicolas,
This is not a bug. The function `org-list-struct' has to be called on an
> item, not anywhere within an item. BTW, it is an internal function. You
> may want to use `org-element-at-point' instead.
>
I see! I'll give it a try!
Thanks!
> Eric Abrahamsen writes:
> Hello, I wonder if there'd be any interest in changing the default
> value of `org-refile-use-outline-path' to something other than
> nil? I can't imagine the nil default would be anyone's preference
> (at least not anyone with more than a handful o
I use macros in my course syllabi to automate creation of timestamps It
looksl ike this:
# see bottom of this email for the defn of ~get-ts~
#+MACRO: ts (eval (get-ts+7))
** Week {{{n}}} ({{{ts}}}): Time Scales in Rivers, Geology, and Human
Relationships
* Week {{{n}}} ({{{ts}}}): +READING WEEK:
Hello,
I wonder if there'd be any interest in changing the default value of
`org-refile-use-outline-path' to something other than nil? I can't
imagine the nil default would be anyone's preference (at least not
anyone with more than a handful of headings in a single file). How about
'file as a more
12 matches
Mail list logo
