Nicolas Goaziou, 2018-01-31 20:12:
Nikolai Weibull <n...@disu.se> writes:
At first I figured that the rules had changed and that the
:PROPERTY: drawer must come first
That's correct.
but then I tried it out and Org would gladly create a new
:LOGBOOK: drawer for an entry that alrea
Hi!
I’m doing some restructuring of my Org files and I’m getting a lot
of claims that I have malformed drawers. Some of these files are
quite old, so at first this seemed like a reasonable problem, but
when I looked closer everything looked fine. The problem was that
I had :LOGBOOK:
* org-agenda.el (org-agenda-insert-diary-strategy): Add new value
'date-tree-last.
(org-agenda-insert-diary-make-new-entry): Handle
`org-agenda-insert-diary-strategy' set to 'date-tree-last.
To allow for diary entries to be entered in time order in the date tree,
add a new value to
---
etc/ORG-NEWS | 3 +++
1 file changed, 3 insertions(+)
diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS
index f1d85c1..dc0d8b1 100644
--- a/etc/ORG-NEWS
+++ b/etc/ORG-NEWS
@@ -12,6 +12,9 @@ Please send Org bug reports to emacs-orgmode@gnu.org.
** New features
*** Org linter
~org-lint~ can check
On Sun, Aug 23, 2015 at 9:40 AM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
+ (let ((last (eq org-agenda-insert-diary-strategy 'date-tree-last))
+ (has-children (save-excursion (org-goto-first-child
+(if (not (and last has-children))
+ (outline-next-heading)
+
Here’s a patch that I hope I managed to compile correctly via git-send-email.
* org-agenda.el (org-agenda-insert-diary-strategy): Add new value
'date-tree-last.
(org-agenda-insert-diary-make-new-entry): Handle
`org-agenda-insert-diary-strategy' set to 'date-tree-last.
To allow for diary entries to be entered in time order in the date tree,
add a new value to
* org-agenda.el (org-agenda-maybe-redo): Test for
org-agenda-this-buffer-name as well.
The Agenda buffer will have a different name if it’s in sticky mode,
but some commands that alter the agenda should still redo it, for
example, org-agenda-remove-restriction-lock, just like
* org-agenda.el (org-agenda-maybe-redo): Test for
org-agenda-this-buffer-name as well.
The Agenda buffer will have a different name if it’s in sticky mode,
but some commands that alter the agenda should still redo it, for
example, org-agenda-remove-restriction-lock, just like
* org-agenda.el (org-agenda-maybe-redo): Test for
org-agenda-this-buffer-name as well.
The Agenda buffer will have a different name if it’s in sticky mode,
but some commands that alter the agenda should still redo it, for
example, org-agenda-remove-restriction-lock, just like
I am so disappointed with everything that has to do with e-mail right
now. For some reason the e-mail isn’t being delivered. I assume it’s
not being accepted by the mailing list, but I can’t see why. I’m not
getting any error message.
Anyway, here’s the relevant part (and let’s see if this
Here’s the patch again, as I don’t think the one I sent yesterday got
through. My FSF papers are signed, by the way.
On Sun, Mar 8, 2015 at 6:59 PM, Achim Gratz strom...@nexgo.de wrote:
Nikolai Weibull writes:
Is trying to manage it via git+make oneself less likely to cause
incidents?
There's a bunch of people who seem to manage it just fine.
Did I say otherwise?
Does this preclude making an alternative
On Sun, Mar 8, 2015 at 3:17 PM, Aaron Ecay aarone...@gmail.com wrote:
IMO this is a bad idea. The bleeding edge version is expected to be
somewhat unstable, and exposing it via ELPA will lead to foot-shooting
incidents.
Is trying to manage it via git+make oneself less likely to cause
Hi!
Would it be of interest to anyone else if the bleeding edge version
was available via elpa?
On Sat, Mar 7, 2015 at 3:47 PM, Xavier Maillard xav...@maillard.im wrote:
Nikolai Weibull n...@disu.se writes:
Would it be of interest to anyone else if the bleeding edge version
was available via elpa?
Isn't it already available via M-x package interface ?
No, only the version based
On Mon, Jul 28, 2014 at 4:20 PM, Bastien b...@gnu.org wrote:
Nikolai Weibull n...@disu.se writes:
Here’s a suggested solution. We keep track of whether the parent
entry already has any children, then we call org-insert-heading with
two universal arguments to add an entry at the end
On Mon, Jan 19, 2015 at 6:38 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
Nikolai Weibull n...@disu.se writes:
On Sun, Jan 18, 2015 at 11:39 PM, Nicolas Goaziou
It could make sense, but the current behaviour is simple and
consistent : always refresh manually, no exception.
I don’t
On Sun, Jan 18, 2015 at 11:39 PM, Nicolas Goaziou
m...@nicolasgoaziou.fr wrote:
Nikolai Weibull n...@disu.se writes:
I realize that you have to update it manually, but wouldn’t it make
sense to have it be updated automatically when you call
org-agenda-(set|remove)-restriction-lock? At least
On Sun, Jan 18, 2015 at 11:26 AM, Nicolas Goaziou
m...@nicolasgoaziou.fr wrote:
Nikolai Weibull n...@disu.se writes:
I’m bumping this again, as this feels like a bug and I’m surprised
that no one has at least responded to it.
On Wed, Jan 7, 2015 at 6:51 PM, Nikolai Weibull n...@disu.se
I’m bumping this again, as this feels like a bug and I’m surprised
that no one has at least responded to it.
On Wed, Jan 7, 2015 at 6:51 PM, Nikolai Weibull n...@disu.se wrote:
Hi!
Anyone else experiencing this? Or is my configuration wrong in some way?
On Mon, Dec 22, 2014 at 7:10 PM
Hi!
Anyone else experiencing this? Or is my configuration wrong in some way?
On Mon, Dec 22, 2014 at 7:10 PM, Nikolai Weibull n...@disu.se wrote:
Hi!
It seems that agendas created when org-agenda-sticky-mode is t aren’t
automatically redone when calling
org-agenda-(set|remove)-restriction
Hi!
It seems that agendas created when org-agenda-sticky-mode is t aren’t
automatically redone when calling
org-agenda-(set|remove)-restriction-lock. The reason is that
(org-agenda-maybe-redo) checks whether there’s a window displaying a
buffer named org-agenda-buffer-name.
Hi!
The documentation for org-agenda-insert-diary-make-new-entry says that
it adds the entry as the last child, but it seems that it’s adding it
as the first child instead. (My org-agenda-insert-diary-strategy is
'date-tree.)
On Fri, May 30, 2014 at 2:10 PM, Bastien b...@gnu.org wrote:
Nikolai Weibull n...@disu.se writes:
The documentation for org-agenda-insert-diary-make-new-entry says that
it adds the entry as the last child, but it seems that it’s adding it
as the first child instead. (My org-agenda-insert
On Fri, May 30, 2014 at 4:04 PM, Bastien b...@gnu.org wrote:
Nikolai Weibull n...@disu.se writes:
Wouldn’t it be better to fix the function? I’m thinking that you
probably want entries added later during the day to appear later in
the file, right?
Personally, I prefer to have recent
On Fri, May 30, 2014 at 5:24 PM, Bastien b...@altern.org wrote:
Hi Nikolai,
Nikolai Weibull n...@disu.se writes:
When set to 'top-level, the documentation mentions that it adds it to
the end of the file and testing confirms this. It thus seems more
consistent to always add entries towards
On Wed, May 21, 2014 at 4:35 AM, Bastien b...@gnu.org wrote:
Hi Nikolai,
Nikolai Weibull n...@disu.se writes:
It seems that if you use
#+STARTUP: indent
the org-hide face used for the hidden stars will remain when using the
org-columns view, resulting on, in my case, white on gray
On Wed, May 21, 2014 at 1:31 PM, Bastien b...@altern.org wrote:
Nikolai Weibull n...@disu.se writes:
Yes, the hiding of the stars is cancelled, but it seems that the
org-hide face is still being applied and leaking unto the whole
headline. I got around this by adjusting the org-column face
On Wed, May 21, 2014 at 3:48 PM, Nikolai Weibull n...@disu.se wrote:
On Wed, May 21, 2014 at 1:31 PM, Bastien b...@altern.org wrote:
Nikolai Weibull n...@disu.se writes:
Yes, the hiding of the stars is cancelled, but it seems that the
org-hide face is still being applied and leaking unto
On Sat, May 10, 2014 at 1:35 PM, Nikolai Weibull n...@disu.se wrote:
Hi!
It seems that if you use
#+STARTUP: indent
the org-hide face used for the hidden stars will remain when using the
org-columns view, resulting on, in my case, white on gray.
To clarify, this leaks out over the whole
Hi!
It seems that if you use
#+STARTUP: indent
the org-hide face used for the hidden stars will remain when using the
org-columns view, resulting on, in my case, white on gray.
Is there a workaround to this that I’m not thinking of?
On Tue, Mar 18, 2014 at 4:27 PM, Bastien b...@gnu.org wrote:
Nikolai Weibull n...@disu.se writes:
(org-mode): When loading Org buffers through desktop
I'm not sure what the above means, can you explain it?
Also, what is exactly the bug this fixes (beyond setting
something that does
Hi!
I would like to use Org mode with MobileOrg over Dropbox and have all
my org-agenda-files synced between all my computers, that is, my home
computer, my work computer, and my mobile. Currently, as I understand
MobileOrg and org-mobile-push/-pull, MobileOrg is only really designed
to sync
34 matches
Mail list logo
