Re: [O] [RFC] Org Num library

Nicolas Goaziou writes: > Hello, > > Marco Wahl writes: > >> Just one idea came to my mind. What about adding an option to restart >> the numbering at 1 for the first heading in the case when narrowing is >> in effect? > > AFAICT, detecting narrowing changes requires using >

[O] (no subject)

At the bottom of this is a description of adding a `org-store-link` inside of a babel code block edit called with C-c ' , however, it doesn't seem to work with C-c l , although M-x org-store-line does work. Or am I seeing, doing this wrong? LB

Re: [O] org-today broken

Hi Marco, Marco Wahl writes: > Occasionally I like to bend time to see what the agenda would look like > if another day was current. This can be achieved conveniently when > solely function "current-time" is the source for the current time. > > So I'm all for using the explicit calls to

Re: [O] Bug: org-copy-subtree: Invalid function: org-preserve-local-variables

I just updated emacs to 27.0.50 and I am seeing the exact same error. I think org-preserve-local-variables is in org-macs which is part of org-mode source code. On Sun, Feb 3, 2019 at 4:14 PM Kyle Meyer wrote: > > Hello, > > Abdo Haji-Ali writes: > > > On the latest org-mode version, 9.2, I

Re: [O] Org Elpa deployment failing for past 2 weeks

Hi Detlef, thanks for reporting this -- I manually uploaded the elpa and elpaplus packages. Can you check it is okay now? The process is broken on the server, I need to investigate a bit to fix it. Thanks, -- Bastien

Re: [O] Org 9.2.1 release?

Hello Nicolas, > If there is no objection, I think it is time for a bugfix release. Yes, this is done now, Org 9.2.1 is out. Thanks! -- Bastien

Re: [O] Closing a task yesterday (or changing the day cutoff to 4am)

Also see variable org-use-effective-time On Sat, 2 Feb 2019, at 15:30, Leo Gaspard wrote: > Uwe Koloska writes: > > Maybe the variable 'org-extend-today-until' can help. > > Indeed, thank you! >

Re: [O] Bug: org-copy-subtree: Invalid function: org-preserve-local-variables

Hello, Abdo Haji-Ali writes: > On the latest org-mode version, 9.2, I keep receiving the error > 'org-copy-subtree: Invalid function: org-preserve-local-variables' > whenever I try to move a subtree or when I access my agenda. > > This happens even if I run emacs with '-Q'. > > Emacs : GNU

Re: [O] [PATCH 1/3] org-habit: Add org-habit-scheduled-past-days

OK I guess in fact I'm 1. supposed to attach the patches (?) and 2. they contain hashes so I guess I should reattach them all together, having changed the first. Here they are. Sorry, I'm new to this email workflow. The new thing here since Nicolas reviewed this last year (apart from applying

[O] [PATCH 1/3] org-habit: Add org-habit-scheduled-past-days

* lisp/org-habit.el (org-habit-scheduled-past-days): New variable * lisp/org-agenda.el (org-agenda-get-scheduled): override `org-scheduled-past-days' for habits if `org-habit-scheduled-past-days` is not nil TINYCHANGE --- lisp/org-agenda.el | 4 +++- lisp/org-habit.el | 15 +++

Re: [O] org-habit: allow overriding org-scheduled-past-days and always including time of day

On Sun, 18 Nov 2018, at 23:40, Nicolas Goaziou wrote: > * lisp/org-habit.el (org-habit-scheduled-past-days): New variable. > > > (when (or (and (> ddays 0) (< diff ddays)) > > - (> diff org-scheduled-past-days) > > + (> diff (if habitp > > +

[O] Bug: org-copy-subtree: Invalid function: org-preserve-local-variables

On the latest org-mode version, 9.2, I keep receiving the error 'org-copy-subtree: Invalid function: org-preserve-local-variables' whenever I try to move a subtree or when I access my agenda. This happens even if I run emacs with '-Q'. Emacs : GNU Emacs 25.3.1 (x86_64-redhat-linux-gnu, GTK+

[O] [PATCH 3/3] org-habit: Use face 'org-agenda-done for habits scheduled for future

* lisp/org-agenda.el (org-agenda-get-scheduled): Use the face. This has the effect that if you just did the habit, it is "greyed out" in the agenda. TINYCHANGE --- lisp/org-agenda.el | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index

[O] [PATCH 2/3] org-habit: Always show time of day designation for habits

* org-agenda.el (org-agenda-get-scheduled): Always show the time of day designation for habits TINYCHANGE --- lisp/org-agenda.el | 14 +++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 9145cafa8..39ae85f30 100644 ---

[O] [PATCH 1/3] org-habit: Add org-habit-scheduled-past-days

* lisp/org-habit.el (org-habit-scheduled-past-days): New variable * lisp/org-agenda.el (org-agenda-get-scheduled): override `org-scheduled-past-days' for habits if `org-habit-scheduled-past-days` is not nil TINYCHANGE --- lisp/org-agenda.el | 8 +++- lisp/org-habit.el | 15

Re: [O] Mark vacation days

I don't know a good way to do this out of the box. Here are two ways you could go about it, but they both involve a bit of programming. They would all use org-agenda-day-face-function similar to the code you already posted. 1. Least programming: Add emacs diary entries (rather than recording

[O] Org 9.2.1 release?

Hello, If there is no objection, I think it is time for a bugfix release. Bastien, WDYT? Regards, -- Nicolas Goaziou

Re: [O] [PATCH] Add feature to org-drill to auto pronounce word

Hello, Stig Brautaset writes: > stardiviner writes: > > [...] > >> @@ -1486,7 +1521,7 @@ the current topic." >> (funcall test)) >> (hide-subtree)) >> (push (point) drill-sections))) >> - "" 'tree)) >> + nil 'tree)) >> (reverse

Re: [O] latest org-mode ignores visibility property selectively

Hello, Michael Maurer writes: > Ok, I figured it out. If the top headline has a "visibility: folded" > property, and one of its children has that property as well, the > parents property gets disabled, for some reason. Guess it's a bug? Fixed. Thank you! Regards, -- Nicolas Goaziou

Re: [O] [RFC] Org Num library

Hello, Marco Wahl writes: > Just one idea came to my mind. What about adding an option to restart > the numbering at 1 for the first heading in the case when narrowing is > in effect? AFAICT, detecting narrowing changes requires using `post-command-hook'. Therefore an update to numbering,