[O] [PATCH] New user option for org-agenda-show-and-scroll-up

ustomizing it to nil gives the alternate behavior I prefer. My not-so-secret hope is that this patch is suitable for applying to master. Please let me know if that's the case, or if there are some changes I can make that would get it there. I'm fine signing copyright assignment papers

[O] [PATCH] org-agenda: Customize agenda-show's drawer hide/show behavior.

* lisp/org-agenda.el (org-agenda-show-and-scroll-up-show-drawers): New user option. Controls whether `org-agenda-show-and-scroll-up' hides or shows drawers without a prefix arg. Pre-patch behavior corresponds to setting this to t (the default). * lisp/org-agenda.el (org-agenda-show-and-scro

Re: [O] TODO keyword highlighting for headings with properties broken

://elpa.gnu.org/packages/org.html. For those who want an easy way to roll back to the 8/25 snapshot. -- Trevor Murphy GnuPG Key: 0x83881C0A

[O] What is the deal with `org-agenda-skip-deadline-prewarning-if-scheduled', 'pre-scheduled, and specific deadline lead times?

vior for when there is no prewarning suppression and the specific warning period just happens to be longer than the user option `org-deadline-warning-days'. If you're still reading, thanks. Please let me know if you have any suggestions, questions, or comments about what I'm trying to do. -- Trevor Murphy GnuPG Key: 0x83881C0A

[O] How do you use `pre-scheduled' deadline skipping with repeaters?

figuring out where to hook into `org-todo'. Or do I want to hook into `org-auto-repeat-maybe'? So, yeah. Do others use this `pre-scheduled' workflow for repeating deadlines? If so, is there an obvious solution to this little nuisance that I'm not seeing? -- Trevor Murphy, ASA, MAAA GnuPG Key: 0x83881C0A

[O] Bug: "Lisp error: (void-variable org-babel-tangle-lang-exts)" when loading languages at startup

Hi, all. First bug report here, so please let me know if I can be more helpful / less verose. I didn't see this previously reported on the mailing list and I'm not yet familiar enough to patch it myself. After updating, I'm receiving the error in the subject line. For reference, I'm running Arch a

[O] [PATCH] org.el: Don't flyspell check within source code blocks

Hi, list. I recently started using flyspell, but I wasn't pleased with the spell checking in my source code blocks. After digging a bit for a solution, I found a post to the list with a nice solution[0]. However, it seems no patch was ever submitted. So, here goes. If there's a deeper reason t

[O] [PATCH] org.el: Don't flyspell check within source code blocks

* lisp/org.el (org-mode-flyspell-verify): Check if `org-element-at-point' is of type `src-block', and don't flyspell if that's the case. TINYCHANGE --- lisp/org.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 94078f9..81428f5 100644 ---

Re: [O] [PATCH] org.el: Don't flyspell check within source code blocks

Ack, what? Please disregard, I slipped a double negative in somehow. On Sat, May 25, 2013 at 3:17 AM, Trevor Murphy wrote: > * lisp/org.el (org-mode-flyspell-verify): Check if > `org-element-at-point' is of type `src-block', and don't flyspell if > that&#x

[O] [PATCH] Take 2 on org.el: Don't flyspell check within source code blocks

Very sorry about the email spam. This fixes the blindingly obvious double negative in my previous submission. Thanks, Trevor

[O] [PATCH] org.el: Don't flyspell check within source code blocks

* lisp/org.el (org-mode-flyspell-verify): Check if `org-element-at-point' is of type `src-block', and don't flyspell if that's the case. TINYCHANGE --- lisp/org.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 94078f9..ce48bb0 100644 ---

[O] [PATCH v2] org.el: Don't flyspell check within source code blocks

* lisp/org.el (org-mode-flyspell-verify): Add check for `org-in-src-block-p'. TINYCHANGE --- lisp/org.el | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 94078f9..77de2d7 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -23596,7 +23596,8 @@ To g

Re: [O] [PATCH] org.el: Don't flyspell check within source code blocks

Thanks, Bastien. Your suggestion has been working perfectly fine for me. Updated patch sent in reply to the first in the chain (I hope ... still trying to master git send-email). Trevor On Sat, May 25, 2013 at 11:52 AM, Bastien wrote: > Hi Trevor, > > Trevor Murphy writes: > >

[O] How can I set the maximum height of the other window created with org-agenda-follow-mode?

to maximize the frame on startup. -- Trevor Murphy GnuPG Key: 0xCB06EAAF

Re: [O] How can I set the maximum height of the other window created with org-agenda-follow-mode?

0% of the frame, respectively (as expected), but as soon as I moved to an agenda item the follow window stole half the frame. -- Trevor Murphy GnuPG Key: 0xCB06EAAF

[O] [PATCH] Timestamps: Handle sub-10-min ranges when updating timestamps

* lisp/org.el (org-get-compact-tod): Pad with "0" if # of minutes is less than 10. TINYCHANGE --- lisp/org.el | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 26e653f..89e023c 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -16088,9 +16088

Re: [O] [PATCH] Timestamps: Handle sub-10-min ranges when updating timestamps

d" dm)) I tested that and it felt noticeably slower when I called `org-reschedule'. The extra `if' and `concat' did not feel slower. I didn't do explicit timings because of the subjective feel (also because I'm not really sure how to do those tests yet). That being said, I agree with you. If you prefer, I'll resubmit the patch without the if => when and using the format string. Let me know if you'd prefer I do some timing tests on format vs if/concat. -- Trevor Murphy GnuPG Key: 0xCB06EAAF

[O] [PATCH v2] Timestamps: Handle sub-10-min ranges when updating timestamps

* lisp/org.el (org-get-compact-tod): Always pad minutes to two places. TINYCHANGE --- lisp/org.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index b1a2fa8..e13c2b8 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -16077,7 +16077,7 @@ with the curren

[O] Can I ask "Which day is it?" when filtering org-agenda views?

y isn't put into the item until /after/ the filter-function gets a chance to process it. Alternatively, if my attempted solution is brain-damaged please let me know a better way to manage the time grid lines. -- Trevor Murphy GnuPG Key: 0xCB06EAAF

Re: [O] Can I ask "Which day is it?" when filtering org-agenda views?

n-from-absolute (org-today)) for example. Bah! That's what I get for training myself to ignore dynamic variables. Thank you, this is precisely the suggestion I was looking for. -- Trevor Murphy GnuPG Key: 0xCB06EAAF

[O] Why does the clocking format in the mode line string look like this?

Hey, list! When I clock into a task, I get a nice notification in my mode line. Except there's always been this one thing that confuses me. With an effort property on the task, the mode line looks like this: [0:00/0:30] (the task headline) But with no effort property set, the mode line look

[O] [PATCH] Place `org-clock-heading' outside clock time.

* org-clock.el (org-clock-get-clock-string): When `org-clock-effort' is nil, arrange the format string components separately, similar to how they are arranged when o-c-e is not-nil. --- lisp/org-clock.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org-clock.el b/li

Re: [O] Get a list of tasks completed today

;mood"). But I got stuck pulling all the closed items, because `org-tags-view' and friends all build an agenda as a side effect. Is my best bet simply re-implementing the parts of `org-tags-view' that I need? Or is there a more common way to use the org machinery to work with items in lisp code? Thanks! -- Trevor Murphy GnuPG Key: 0x83881C0A

Re: [O] Get a list of tasks completed today

Boo, reflowed text or some nonsense. Let's see if this works better: (add-to-list 'org-agenda-custom-commands '("." "Closed this week." tags "CLOSED>\"<-1w>\"" ((org-agenda-sorting-strategy '(priority-down) -- Trevor Murphy GnuPG Key: 0x83881C0A

[O] Bug: Commit cece23 'fix'-ed call to 'type' breaks my agenda sorting [8.2.7 (8.2.7-elpa @ /home/trevor/.emacs.d/elpa/org-20140613/)]

d-extra-i686-juergen Package: Org-mode version 8.2.7 (8.2.7-elpa @ /home/trevor/.emacs.d/elpa/org-20140613/) -- Trevor Murphy GnuPG Key: 0x83881C0A

[PATCH] org-eldoc: Fix compatibility with eldoc 1.11 and Emacs 27

* contrib/lisp/org-eldoc.el (org-eldoc-documentation-function): Check before invoking elisp eldoc functions from Emacs 28. The previous check assumed that the presence of eldoc 1.11 bindings implied elisp-mode bindings that come with Emacs>=28, but eldoc 1.11 is available on GNU Elpa so the assu

[BUG] org-goto does not show local context around visible headlines [9.7.11 (release_9.7.11 @ /usr/share/emacs/30.1/lisp/org/)]

, I've attached a minimal patch that removes the invisibility checks within org-goto. I ran the org tests per https://orgmode.org/worg/org-contribute.html#first-patch and everything seemed fine (one test failed, but it's test-org-publish/resolve-external-link and that seems to als