Now I get it. Thank you for explanation.
On Sat, Oct 14, 2023 at 9:39 PM Ihor Radchenko wrote:
> Sławomir Grochowski writes:
>
> > But I'm talking about:
> > (":mean" . org-columns--summary-mean-time)
> > not ("@mean" . org-columns--summary-mean-age).
> >
> > So this is the right function (":
Sławomir Grochowski writes:
> But I'm talking about:
> (":mean" . org-columns--summary-mean-time)
> not ("@mean" . org-columns--summary-mean-age).
>
> So this is the right function (":mean" . org-columns--summary-mean-time)?
> Or do I need to write a new one?
I think you still need to write a n
But I'm talking about:
(":mean" . org-columns--summary-mean-time)
not ("@mean" . org-columns--summary-mean-age).
So this is the right function (":mean" . org-columns--summary-mean-time)?
Or do I need to write a new one?
On Sat, Oct 14, 2023 at 9:19 PM Ihor Radchenko wrote:
> Sławomir Grochowsk
Sławomir Grochowski writes:
> In ex. I want to have an average time when I go to bed.
> So on Monday I went to bed at 22:00 and on Tuesday at 02:00.
> So the average time would be midnight 00:00.
> But it returns 12:00 which is noon.
As I said, it is because it does not calculate an average time
In ex. I want to have an average time when I go to bed.
So on Monday I went to bed at 22:00 and on Tuesday at 02:00.
So the average time would be midnight 00:00.
But it returns 12:00 which is noon.
On Sat, Oct 14, 2023 at 8:50 PM Ihor Radchenko wrote:
> Sławomir Grochowski writes:
>
> > I'm
Sławomir Grochowski writes:
> I'm not sure if this is a bug or I need to change something?
>
> (org-columns--summary-mean-time '("17:00" "18:00") nil) ;=> "17:30" ; ok
> (org-columns--summary-mean-time '("22:00" "02:00") nil) ;=> "12:00" ;
> should be 00:00
> (org-columns--summary-mean-time '("22
Dear All,
I'm not sure if this is a bug or I need to change something?
(org-columns--summary-mean-time '("17:00" "18:00") nil) ;=> "17:30" ; ok
(org-columns--summary-mean-time '("22:00" "02:00") nil) ;=> "12:00" ;
should be 00:00
(org-columns--summary-mean-time '("22:00" "03:00") nil) ;=> "12:30"
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
Ihor Radchenko writes:
> In the absence of an API, the best I can see you can do is automating
> the cleanup. Either using text manipulation in Elisp or some kind of
> HTML parsing library (for example, see
> https://github.com/yantar92/org-capture-ref/blob/master/org-capture-ref.el#L1026
> where
>From 0d8067348d033e159a460233773e442c0775a8bb Mon Sep 17 00:00:00 2001
From: Elias Kueny
Date: Sat, 14 Oct 2023 00:20:55 +0200
Subject: [PATCH] lisp/ob-shell.el: Adapt the `:var' header parameter to fish
* ob-shell.el (org-babel-variable-assignments:shell): allow the `:var'
keyword on fish code
Cletip Cletip writes:
> I know how to create a custom agenda block, but how insert this ? Can I
> just have some leads ?
No, I did not mean custom agenda block. I meant custom agenda block
_type_ (just like agenda, alltodo, tags, etc).
Implementing a new custom block type involves writing a lot
I know how to create a custom agenda block, but how insert this ? Can I
just have some leads ?
Le jeu. 12 oct. 2023 à 13:39, Ihor Radchenko a écrit :
> Cletip Cletip writes:
>
> > Here's an example for clarification:
> > Consider this line in org-agenda:
> >
> > 14:08-14:10 Clocked: (0:02) name
Very cool, thanks !
Le mer. 11 oct. 2023 à 11:03, Ihor Radchenko a écrit :
> Ihor Radchenko writes:
>
> >> if I have the following heading :
> >>
> >> * A test
> >> [2023-10-10 Tue 17:25]--[2023-10-10 Tue 17:30]
> >> <2023-10-10 Tue 17:25>--<2023-10-10 Tue 17:30>
> >>
> >> The "org interval"
Rudolf Adamkovič writes:
>> What about [[Link][link]]?
>
> That makes Org documents hard to read in *plain text*, that is without
> the "descriptive links" fontification. Here is my note again, compare:
>
> EXAMPLE 1: Hard-to-read, unhelpful markup:
>
> The set of [[Cellular membrane][cellular
Max Nikulin writes:
>> May you elaborate? I am not talking about implementation details, but
>> about the reasonable defaults for the export. Not necessary ASCII, but
>> other backends as well.
> I am rather skeptical concerning a variant that is pleasant to read in
> all cases. That is why I su
Hi Ihor
It seems Rick gave a step towards the direction of links to points? It
would seem that if the Search Option would be available for internal
links, it would work. Then maybe we would just miss a convenient way for
generating unique <>.
Bests.
On 09/10/2023 13:24, Ihor Radchenko wrote
16 matches
Mail list logo
