David Masterson writes:
> I'm not sure I understand 'sequence' and 'type' in org-todo-keywords.
You're over thinking it. You can define various todo keywords and they
are divided into two groups that can be thought of as "ones that need
your attention" and "ones that don't need your attention"
Daniel Fleischer [2023-01-17 Tue 10:10] wrote:
> Don't let the cyclical switching dictates the meaning, it's just an
> implementation detail, done for simplicity. Hope it helped.
Put another way, if you define A B | C D E
and the UI switching is A->B->C->D->E->A
it doesn't mean the B going
"Fraga, Eric" writes:
> I assume that, maybe, this is not org's fault but this kind of problem
> only arises when using org-cite-insert so I was wondering if indeed
> there is something I can tweak in org or oc- to get better completion
> behaviour? Or maybe something I can specify for vertico?
David Masterson writes:
> I'm not sure I understand 'sequence' and 'type' in org-todo-keywords.
> In particular, I can only think of the following simple sequence as
> being possible in org-todo-keywords:
>
> TODO -> IN-PROCESS -> DONE
>
> If I want to add in (say) WAITING, the graph
Daryl Manning writes:
> I'd argue that setting a specific datestamp and time for DST would mean that
> you expected to meet at that
> specific time and date as per DST. If the clocks changed you'd be out of luck
> (that's where I'd argue you'd
> use a non-specified timezone for a meeting that
Tom Gillespie writes:
>> > As for years BC, <-0001-...> will be a breaking change. But I do not
>> > think that we need to really worry about this. Not unless we actually
>> > get feature request. What is the practical application?
>
> Using org as a format for writing about history and being
Tim Cross writes:
> I think you run a high risk of running into GNU policy issues wrt
> licensing and free software support given this is a cleint for an AWS
> only database.
Is it because it's cloud only or because it's proprietary?
Because we already support Orcale, SAP Hana, MSSql and
Ihor Radchenko writes:
> Tim Cross writes:
>
>> It also seems that the solution will need some mechanism (possibly on a
>> per time stamp basis) for the user to specify what should happen when
>> either the time zone has a daylight savings transition, when the
>> timezone rules change or when
Detlef Steuer writes:
>> The patch only allows to the TTL globally for all the calendars.
>> However, it would make sense to specify TTL on per-file basis. WDYT?
>>
>
> Hmm. Surely it would be useful to have the option to use different TTL
> settings for different calendar exports, yes.
>
> The
Gautier Ponsinet writes:
> I would like to propose the introduction of a new face:
> org-agenda-calendar-timerange.
> It is used to show entries with a timerange in the agenda, that is,
> entries with a timestamp of the form:
> <2022-12-22 Thu>--<2023-01-01 Sun>
> At the moment, these entries
Robert Horn writes:
> Those who wanted astronomical or other relationships would usually
> specify UTC or TAI. They might use a fixed offset for UTC. People who
> are into the demands of TAI (e.g., orbital mechanics) generally don't
> want to deal with the offsets or other issues that come up
Samuel Wales writes:
> oh i was just saying what does modern org e.g. main have for ensuring
> star structure integrity, if anything. i have a git commit that has
> something similar to:
>
> * one
> ** two
>
> which seemed slightly relevant to the patch.
Sorry, but could you further
On Tuesday, 17 Jan 2023 at 08:38, Ihor Radchenko wrote:
> ⚠️ Caution: External sender
>
>
> "Fraga, Eric" writes:
>
>> I assume that, maybe, this is not org's fault but this kind of problem
>> only arises when using org-cite-insert so I was wondering if indeed
>> there is something I can tweak in
Robert Horn writes:
>> Not really. Countries may change DST at any moment in future. Or decide
>> to switch calendars (consider countries near the day transition line).
>>
>> And "past local time, according to the DST rules in effect at the time"
>> is also an option that might be useful in
Tim Cross writes:
> It also seems that the solution will need some mechanism (possibly on a
> per time stamp basis) for the user to specify what should happen when
> either the time zone has a daylight savings transition, when the
> timezone rules change or when the user's 'default' time zone
André A. Gomes writes:
> Run the command org-edit-src-code, and notice that the contents look
> correct. However, when you run the command org-edit-src-exit the org
> file shows:
>
> --8<---cut here---start->8---
> #+begin_src conf
> ,*.test
> #+end_src
>
Detlef Steuer writes:
> I tried to follow your advice to improve the patch accordingly.
> New version attached.
I have amended your patch fixing some of the spelling issues and
indentation. See the attached. Note that I used "time to live"
consistently instead of "time to life". The former is
Daniel Kraus writes:
> Tim Cross writes:
>
>> I think you run a high risk of running into GNU policy issues wrt
>> licensing and free software support given this is a cleint for an AWS
>> only database.
>
> Is it because it's cloud only or because it's proprietary?
Both. For cloud, see
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.
Tim Cross writes:
> Daryl Manning writes:
>
>> I think timezone you're in should be declared globally, surely? And then
>> defined in the timestamp?
>>
>
> Do you mean globally as in at the OS level or globally in org mode. If
> the latter, I disagree. The OS has this information and there is
Am Tue, 17 Jan 2023 09:43:18 +
schrieb Ihor Radchenko :
> Detlef Steuer writes:
>
> > I tried to follow your advice to improve the patch accordingly.
> > New version attached.
>
> I have amended your patch fixing some of the spelling issues and
> indentation. See the attached. Note that
"Fraga, Eric" writes:
>> org-cite-insert simply calls whatever is provided by the citation
>> backend you use. Please tell us which oc-*.el backend is creating the
>> problem.
>
> Maybe I'm doing something wrong somewhere because whether I try basic,
> biblatex, or csl, they appear the same in
No Wayman writes:
> Ihor Radchenko writes:
>
>> What we should not have is "make autoloads" failing without
>> internet.
>
> The attached patch should take care of that.
> If the ls-remote errors, GITVERSION will be set to N/A as when it
> is generally unavailable.
I just tried your patch
Hi Ihor,
On Tuesday, 17 Jan 2023 at 10:22, Ihor Radchenko wrote:
> In oc-basic, there is `org-cite-basic-author-column-end' and it indeed
> truncates the match. Eric, as temporary workaround, you can try to
> increase `org-cite-basic-author-column-end'.
Ah, interesting. I had to restart Emacs
Ihor Radchenko writes:
> Daniel Kraus writes:
>
>> Tim Cross writes:
>>
>>> I think you run a high risk of running into GNU policy issues wrt
>>> licensing and free software support given this is a cleint for an AWS
>>> only database.
>>
>> Is it because it's cloud only or because it's
Hi,
The reproducer using Emacs 28.2 and Org 9.6.1 both from Guix (29efa27):
--8<---cut here---start->8---
$ cd /tmp/
$ cat config.el
(setq
org-directory "/tmp/"
org-agenda-files '("example.org"))
$ cat example.org
* TODO Stuff
$ emacs -q -l config.el -f
David Masterson writes:
> The problem is (I think), when you attach @ or ! to the state and, as you
> cycle thru (S-right), new unintended notes will be added as you cycle to
> the state you're looking for. True?
If you attach @ or !, those notes are not unintended.
S-right is not for you to
Max Nikulin writes:
> https://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time
>Falsehoods programmers believe about time
Some potentially relevant items:
- Each calendar date is followed by the next in sequence, without
skipping.
- The standard library
On 1/17/23, Ihor Radchenko wrote:
>> * one
>> ** two
>>
>> which seemed slightly relevant to the patch.
>
> Sorry, but could you further elaborate? What kind of integrity and what
> kind of structure editing do you have in mind here?
maybe my comment is too unrelated to the patch, but it
David Masterson writes:
>> #+TODO: WAIT IN-PROCESS
>> #+TODO: TODO IN-PROCESS | DONE
>
> This is on a per-file basis, correct? This can't be done in
> org-todo-keywords?
It can. You can have multiple 'sequence-s there.
>> Note, however, that moving S- will be ambiguous.
>
> Ambiguous or not
Hey, thanks for the input!
My shell-file-name is indeed pointing to cmdproxy.exe, and after changing
shell-command-switch to "/k" or "-k", I get a similar output:
#+begin_src shell
echo 1
echo 2
echo 3
#+end_src
#+RESULTS:
| Microsoft| Windows | [Version | 10.0.14393] | |
Ihor Radchenko writes:
"timerange" is a bit confusing because the patch will only affect date
ranges like <2022-12-22 Thu>--<2023-01-01 Sun> and
<2022-12-22 Thu 12:00>--<2023-01-01 Sun 10:00>, but not time ranges
<2022-12-22 Thu 10:00-12:00>
Is it what you are proposing? Or do you also want
Hi Nick,
Nick Dokos writes:
> "Loris Bennett" writes:
>
>> Hi,
>>
>> I have
>>
>> (setq lb/org-directory "~/org/"))
>> (setq lb/gtd-file (expand-file-name "gtd.org" lb/org-directory))
>> (setq lb/refile-file (expand-file-name "refile.org" lb/org-directory))
>> (setq org-agenda-files
Ihor Radchenko writes:
> David Masterson writes:
>
>> The problem is (I think), when you attach @ or ! to the state and, as you
>> cycle thru (S-right), new unintended notes will be added as you cycle to
>> the state you're looking for. True?
>
> If you attach @ or !, those notes are not
Reporting this from emacs 28, but I first noticed in a freshly compiled
version of emacs.
This does NOT occur in org 9.5.5 that is included with emacs 28.
I do not have any special configuration for org babel.
Open emacs.
Open some .org file with src blocks in some folder /some.org
Notice a
*Expected behaviour*:
All lines of the shell block should be evaluated, with full output printed.
*Actual behaviour*:
All lines but the last are evaluated, the output ends with 'More?'
instead of the last command's output.
*Steps to reproduce*:
In Windows, start a clean Emacs instance (I used
Hello there, orgmode list, this is my first contribution here, so please be
gentle with me.
I've now used outlining software for the last twenty years at least and it
is my belief that when a user pastes headlines into an outline, they
usually want to make them either A) siblings of (i. e. paste
Ihor Radchenko writes:
> David Masterson writes:
>
>>> #+TODO: WAIT IN-PROCESS
>>> #+TODO: TODO IN-PROCESS | DONE
>>
>>> Note, however, that moving S- will be ambiguous.
>>
>> Ambiguous or not possible?
>
> Ambiguous is: consider a task IN-PROCESS and you press S-left. Should
> Org go to TODO
On Tue, 17 Jan 2023 14:53:39 -0500 Osher Jacob wrote ---
> changing shell-command-switch to "/k" or "-k", I get a similar output:
Thanks for checking that.
> You also mentioned the source code block is being passed through the "-c"
> flag as a command-line argument.I might be
Ihor Radchenko writes:
> Bastien, please let me know if you have any objections.
None, thanks for taking action here.
--
Bastien
Ihor Radchenko writes:
> David Masterson writes:
>
>> The problem is (I think), when you attach @ or ! to the state and, as you
>> cycle thru (S-right), new unintended notes will be added as you cycle to
>> the state you're looking for. True?
>
> If you attach @ or !, those notes are not
On 17/01/2023 01:37, Ihor Radchenko wrote:
Some formats may be confusing for users, e.g. TZ=GMT+5 actually means
-0500 offset.
Let's just recommend +- and @location in the manual. And mention
briefly that TZ format is supported in addition.
We might also provide an optional linter for GMT,
Daniel Fleischer writes:
> Daniel Fleischer [2023-01-17 Tue 10:10] wrote:
>
>> Don't let the cyclical switching dictates the meaning, it's just an
>> implementation detail, done for simplicity. Hope it helped.
>
> Put another way, if you define A B | C D E
>
> and the UI switching is
Ihor Radchenko writes:
F> David Masterson writes:
>
>> I'm not sure I understand 'sequence' and 'type' in org-todo-keywords.
>> In particular, I can only think of the following simple sequence as
>> being possible in org-todo-keywords:
>>
>> TODO -> IN-PROCESS -> DONE
>>
>> If I want to add in
Ihor Radchenko writes:
> We should fix this before Org 9.6.1.
> I will leave the decision about exact Emacs version to Bastien.
>
> One notable fact is that Debian oldstable we use on CI [1] appears to
> use Emacs 26.1. So, we are probably safe to declare Emacs 26.1
> compatibility.
>
> [1]
Ypo writes:
> Could be the headlines exported in a faster way?
>
> Could be possible to avoid the duplication of information? (To create
> the diagram directly from the headlines, without yanking a copy of them).
You can use noweb reference syntax.
#+name: collect-headings
#+begin_src
Ihor Radchenko writes:
> I am attaching tentative patch that will make
> `org-cite-basic--get-field' throw an error when the filed value is not a
> string.
Applied, onto main; with minor amendments.
I made the new code not throw error on nil return value.
Hi,
I have
(setq lb/org-directory "~/org/"))
(setq lb/gtd-file (expand-file-name "gtd.org" lb/org-directory))
(setq lb/refile-file (expand-file-name "refile.org" lb/org-directory))
(setq org-agenda-files '(lb/gtd-file lb/refile-file))
But generating the agenda fails with
Wrong type
* Ihor Radchenko [2023-01-16 14:21]:
> In another message, I also mentioned an idea of specifying time zone
> globally or per file. Other suggestion was per-heading specification. In
> addition to time zone being specified directly inside the timestamp.
Of course that is solution. iCalendar
* Ihor Radchenko [2023-01-16 22:08]:
> 1. Time (-MM-DD HH:MM) not continuous and may change arbitrarily at
>certain times a year or in future or in the past:
I am sure that system library must be responsible to know those
changes. It is not for Org.
So the calculation which transforms
* Ihor Radchenko [2023-01-16 14:25]:
> Jean Louis writes:
>
> >> I am not sure what is the problem.
> >> The timestamps that should stay in local time will be automatically
> >> updated as your system TZ is updated.
> >
> > Then Org shall know what was local time! Without being specified in
> >
"Loris Bennett" writes:
> Hi,
>
> I have
>
> (setq lb/org-directory "~/org/"))
> (setq lb/gtd-file (expand-file-name "gtd.org" lb/org-directory))
> (setq lb/refile-file (expand-file-name "refile.org" lb/org-directory))
> (setq org-agenda-files '(lb/gtd-file lb/refile-file))
>
> But
On 17/01/2023 02:07, Ihor Radchenko wrote:
https://www.youtube.com/watch?v=-5wpm-gesOY gives various examples.
More links:
- https://stackoverflow.com/tags/timezone/info
-
https://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time
Falsehoods programmers believe
#+title: Observation of hysteresis in a GNU libc time conversion function
#+begin_abstract
The ~mktime~ function in GNU libc for specific arguments
may possess properties similar to ferromagnetic materials.
Dependence of returned value on arguments passed during
earler calls gives evidences that
54 matches
Mail list logo
