Hello
What's a type of timestamp <2022-10-15 Sat 10:00-13:00>?
From org-manual:
the definition for a timestamp is:
A timestamp is a specification of a date (possibly with a time or
a range of times) in a
special format, either '<2003-09-16 Tue>' or '<2003-09-16 Tue
09:39>'
or ‘<2003-09-16
Ihor Radchenko writes:
> Hi,
>
> I would like to assess the efficiency of one of search optimizations used
> in org-element.el [1]
>
> The statistics about efficiency is collected by Org, but obviously not
> shared without your consent.
>
> If you are ok with sharing the statistics, and you are r
On Sat, 11 Feb 2023 06:44:56 -0500 Ihor Radchenko wrote ---
> 1. You should provide all the docstrings.
> 2. I generally feel that separate async and separate session code are
>either duplicating the same code or edge cases considered by session
>code may popup in async code
On Sat, 11 Feb 2023 15:56:00 -0500wrote ---
> org-babel-comint-async-filter is capable of taking a similar approach,
> and reading/writing to tempfile.
There is some precedence in ob-shell for this. Currently, the cmdline, stdin,
and shebang headers use temp files. It may be that
Arthur Miller writes:
> And for the last time: I am not using this version of read-string, I don't
> need
> it myself; it was just me thinking how to implement something after reading a
> blog post. Anyway, thanks for the input, it was valuable to me.
Note that Emacs 29 has `read-string-from-bu
Bruno Barbier writes:
> Hi Arthur,
>
> Arthur Miller writes:
>
>> Bruno Barbier writes:
>>
>> ... but I feel a
>> bit of passive aggressivity here, for no good reason tbh.
>
> I'm just trying to help, giving some valid or invalid advices. I'm
> sorry that what I wrote, and how I wrote it, mad
alain.coch...@unistra.fr writes:
> Ihor Radchenko writes on Sat 11 Feb 2023 18:22:
>
> > We can indeed at such warning, but it will probably be not very
> > helpful.
>
> I don't understand this. And isn't it better to have a more accurate
> manual anyway?
Sure. But I want to implement more gen
On Sun, Feb 12, 2023 at 12:33:40PM +0300, Jean Louis wrote:
> * Ihor Radchenko [2023-02-10 13:48]:
> > Jean Louis writes:
> >
> > > If you start adding in Org "fixed" time with UTC offset, that is a new
> > > type of timestamp, as it is not common in world.
> >
> > It is how ISO8601 defines off
Could it be reasonable to collect the hypothetical cases where relative
timestamps would be used?
So, alternatives and solutions could be evaluated more easily.
For example:
| External Input | User's
input | Org output
* Max Nikulin [2023-02-11 07:47]:
> On 10/02/2023 10:29, Jean Louis wrote:
> > 2030-02-09 12:00 -08 @UTC -- this time CANNOT be said to be "fixed
> > UTC"
>
> I do not see any reason why obviously invalid timestamp draws so much
> attention.
>
> Resolution may be rather concise: behavior is *und
* Ihor Radchenko [2023-02-10 13:48]:
> Jean Louis writes:
>
> > If you start adding in Org "fixed" time with UTC offset, that is a new
> > type of timestamp, as it is not common in world.
>
> It is how ISO8601 defines offsets.
- did you say you wish to represent time with UTC time zone by usin
Hi Arthur,
Arthur Miller writes:
> Bruno Barbier writes:
>
> ... but I feel a
> bit of passive aggressivity here, for no good reason tbh.
I'm just trying to help, giving some valid or invalid advices. I'm
sorry that what I wrote, and how I wrote it, made you feel that way.
>>
>> Yes, let b
12 matches
Mail list logo
