* 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
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
* 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
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
about what I'm trying to do.
--
Trevor Murphy
GnuPG Key: 0x83881C0A
to discover -
https://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
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.
Thanks for taking a look!
--
Trevor
* 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
/.emacs.d/elpa/org-20140613/) --
Trevor Murphy
GnuPG Key: 0x83881C0A
'
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
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
attempted solution is brain-damaged please
let me know a better way to manage the time grid lines.
--
Trevor Murphy GnuPG Key: 0xCB06EAAF
-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
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
* 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
* 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
the frame on startup.
--
Trevor Murphy
GnuPG Key: 0xCB06EAAF
,
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
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 b...@gnu.org wrote:
Hi Trevor,
Trevor Murphy trevor.m.mur
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
* 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
Ack, what? Please disregard, I slipped a double negative in somehow.
On Sat, May 25, 2013 at 3:17 AM, Trevor Murphy trevor.m.mur...@gmail.comwrote:
* 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
Very sorry about the email spam. This fixes the blindingly obvious
double negative in my previous submission.
Thanks,
Trevor
* 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
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
25 matches
Mail list logo
