* org-agenda.el (org-agenda--insert-overriding-header): Allow
`org-agenda-overriding-header' to be a function in addition to a
string or nil. When the custom agenda is created or updated, call that
function and insert the string it returns as the agenda header.
This allows custom commands to
I thought this would be a nice extension to an existing customization
option for org-agenda. Commit message has an example and rationale.
Comments and amendments welcome, of course. I signed FSF copyright
assignment previously. Thanks, Chris
On Thu, Aug 12, 2021 at 1:19 PM John Kitchin wrote:
> so, I guess I am in agreement that it is option 2, and that there needs to be
> a single entry point for each one.
+1
So I guess open questions:
1. a new syntax that mirrors cite (and accompanying new
cross-reference element?), per
[PATCH] ox: Italian smart quotes
* ox.el (org-export-smart-quotes-alist): Added support for italian smart quotes.
>From 97a45353d19be98bcf0d94da0d902a025408fa3a Mon Sep 17 00:00:00 2001
From: DPDmancul
Date: Wed, 11 Aug 2021 18:21:55 +0200
Subject: [PATCH] ox: Italian smart quotes
* ox.el
> As I have thought about this more, the line between citations and
> > cross-references has blurred. In org-ref, they were handled the same
> > way, with org-links (although each link had its own export function).
> > For both cites and refs, the links are just pointers, and in both cases
> > it
On 30/06/2021 20:30, Michael Dauer wrote:
I've the following:
(defun ct-action-plan ( up recently-done)
...
(push '("action_plan" . "(eval (ct-action-plan $1 $2))")
org-export-global-macros)
Didn't you report that adding macros directly to
`org-export-global-macros' are not supported by
On Wed, Aug 11, 2021 at 1:31 PM John Kitchin wrote:
...
> > It's just there needs to be some way to distinguish among types of
> > targets, I think.
>
> At the risk of repeating myself, I don't think this is true.
Just to clarify ...yes, I agree with you; I wrote that before the
subsequent
On 12/08/2021 04:17, Marco Wahl wrote:
Maxim Nikulin writes:
Compiling single /home/ubuntu/org-mode/lisp/org-compat.el...
In end of data:
org-compat.el:1255:1:Warning: the function ‘directory-empty-p’ is not
known to
be defined.
...
How make the compiler happy?
I have never fought
Michael Dauer writes:
> If I did not miss it there is no way to specify arguments as optional for a
> macro definition.
You are right.
> Is this a bug? Any ideas for a work-around to avoid confusion for my users.
AFAIU it is not a bug, but rather a missing feature.
Best,
Ihor
It is for me. However, this all depends on how you configure things.
In my case, I have a standard structure for my org files. I have a
different org file for each 'topic' and each org file has headings for
* Tasks
* Notes
* Resources
* Comms
* General
and each of those headings has a
10 matches
Mail list logo
