From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Derek Feichtinger <dfeich@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/)
Date: Thu, 21 Jan 2016 10:47:02 +0100 [thread overview]
Message-ID: <87oacfjmcp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CALGTQTbNKKn1J5f05HObc2eT=4N80-uCnoy-pTq0tOwWtvFPAQ@mail.gmail.com> (Derek Feichtinger's message of "Thu, 21 Jan 2016 10:26:56 +0100")
Hello,
Derek Feichtinger <dfeich@gmail.com> writes:
> The thing which made it hard for me to identify the initial problem was
> that the test CLOCK lines I had in the testing file where placed there
> without a heading. When later in the day I wanted to clock in to my tasks,
> I then just ended up with a "outline-back-to-heading: before first
> heading" error, but with no indicator which of my ~60 open org files was
> the culprit. Maybe one could insert the file location in that error
> message?
Actually, that is the very point of `org-back-to-heading' but... it
wasn't used. I fixed it. Thank you.
> Since org is so extremely useful, and I almost spend 80% of my day in org
> files (also some of my collaborators are beginning to use it... it is
> viral), I often have >50 files with all kinds of purposes open: agenda,
> various notes, beamer, html-exports, wiki-authoring, project-organization,
> bookkeeping... the thing is just too useful. So, I think clashes between
> the many uses of org files probably are natural.
>
> This being emacs :-) I just decided to advise org-resolve-clocks.
Exactly. Thanks to Emacs, you can bend any part of Org to your needs.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2016-01-21 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 20:22 Bug: org-resolve-clocks should not iterate over non-agenda org files [8.3.3 (8.3.3-elpaplus @ /home/dfeich/.emacs.d/elpa/org-plus-contrib-20160108/) Derek Feichtinger
2016-01-20 13:14 ` Nicolas Goaziou
2016-01-21 9:26 ` Derek Feichtinger
2016-01-21 9:47 ` Nicolas Goaziou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oacfjmcp.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=dfeich@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).