Re: [PATCH] org-timer.el: Allow org-timer-set-timer from non-Org buffers
Hi Ian, There's a small typo in the docstring. :)
Re: Agenda: Display scheduled items only once
Have you checked these settings? M-x customize-group RET org-agenda RET Be sure to check the subgroups as well--there are many options.
Re: [PATCH] Fix typos
Kyle Meyer writes: > Jonas Bernoulli writes: > >> Please consider applying the below patch, which fixes many spelling >> errors. > > Eh, there's some good ones in there. I wish I could say that having a typo in the first sentence of the reply was intentional :/
Re: [O] [PATCH] org-manual: Dynamic Blocks: Fix explanation of :content
Sebastian Miele writes: > * doc/org-manual.org (Dynamic Blocks): Correct the information given > on :content in the plist passed to the writer function. Looks correct to me. Applied in 634880a2e. Thanks.
Re: [PATCH] Fix typos
Jonas Bernoulli writes: > Please consider applying the below patch, which fixes many spelling > errors. Eh, there's some good ones in there. Applied. > In addition to the below typos I also found some things I don't know > how to deal with: > * "visibile" as a supported value of org-s5-control-visibility With a quick scan, I couldn't figure out what the best way to deal with that would be. It looks like org-s5--build-meta-info would put the value into a string as is, so it seems likely that the typo means it doesn't behave as intended. This is in contrib/, so I've added the original author in the cc in case he wants to take a closer look. > * "ded" appearing in doc/orgcard.tex I think that's a shortening of "dedicated", presumably to squeeze things into the card. Thanks.
[PATCH] org-timer.el: Allow org-timer-set-timer from non-Org buffers
Hi. Tiny patch enclosed. From d2af2e877147cc7be1f0c40455c9091f130c2159 Mon Sep 17 00:00:00 2001 From: ian Date: Sat, 16 Nov 2019 13:18:17 -0500 Subject: [PATCH] org-timer.el: Allow org-timer-set-timer from non-Org buffers * org-timer.el (org-timer--get-timer-title): If the current buffer is not an Org buffer, use the buffer name as the timer title. Currently all of the `org-timer-' operations work from any buffer except `org-timer-set-timer' which must be run from an Org buffer. This is because `org-timer-set-timer' sets a timer name based on an Org heading or filename. By setting the timer title to the current buffer name we can use `org-timer-set-timer' from any buffer and preserve the timer naming convention of using the buffer name if there isn't an Org header. TINYCHANGE --- lisp/org-timer.el | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/lisp/org-timer.el b/lisp/org-timer.el index 9674219..4367869 100644 --- a/lisp/org-timer.el +++ b/lisp/org-timer.el @@ -466,7 +466,8 @@ time is up." (run-hooks 'org-timer-done-hook) (defun org-timer--get-timer-title () - "Construct timer title from heading or file name of Org buffer." + "Construct timer title. +Try to us an Org header, otherwise use the buffer name." (cond ((derived-mode-p 'org-agenda-mode) (let* ((marker (or (get-text-property (point) 'org-marker) @@ -482,7 +483,7 @@ time is up." ((derived-mode-p 'org-mode) (or (ignore-errors (org-get-heading)) (buffer-name (buffer-base-buffer - (t (error "Not in an Org buffer" + (t (buffer-name (buffer-base-buffer) (provide 'org-timer) -- 2.7.4
Agenda: Display scheduled items only once
Hello all, How can I tell org-mode to only show me a scheduled todo item once in my agenda? IMHO the format below becomes pretty formidable if I have a bunch of scheduled items from the past, because the items will show up on the original day (e.g. Thursday in the example below) *and* on today's date. I would like the items only to show up on today's date. Thursday 14 November 2019 Scheduled: todo [#A] Do something Saturday 16 November 2019 Sched. 2x: todo [#A] Do something This is in the default weekly / daily org-agenda-view. This seems like an odd "default" behavior - to me, seeing something has been scheduled for 2x is sufficient - I don't need to see the same entry under the past day which it was scheduled for. Am I missing some basic setting? I might change the default org-agenda-start-day to start to today's date if that would "fix" this "issue" :) Thanks, --Nate
