From: Marcin Borkowski <mbork@mbork.pl>
To: Sacha Chua <sacha@sachachua.com>
Cc: Adam Porter <adam@alphapapa.net>, emacs list <emacs-orgmode@gnu.org>
Subject: Re: An Org-based productivity tool
Date: Mon, 29 Oct 2018 18:17:02 +0100 [thread overview]
Message-ID: <871s8865bl.fsf@mbork.pl> (raw)
In-Reply-To: <CAJGZZeLiqhFxGsBbi9JeBO54wz=KiJmBikxUBrHAm3L3SC4RBA@mail.gmail.com>
On 2018-10-29, at 13:31, Sacha Chua <sacha@sachachua.com> wrote:
> On Mon, Oct 29, 2018, 05:19 Marcin Borkowski, <mbork@mbork.pl> wrote:
>
>>
>> Well, I think I have something even better -
>> https://github.com/akirak/counsel-org-clock (I find Counsel/Ivy
>> interface much superior to the default refiling one). I have my
>
> Oh, I should switch to that! Thanks for the recommendation.
You're welcome!
> Definitely! As of now, the main use is to make sure I don't get
>> distracted too much at work so that I can actually make ends meet (I'm
>> paid by an hour), so this is a crucial part of my work infrastructure.
>> Also, this means it /must/ be a harsh taskmaster (at least for some
>> time).
>
> I remember liking the combination of org-capture (for ideas and tasks that
> might otherwise interrupt my flow), effort estimates, looking at the
I don't use effort estimates. I'll try them one day.
> current clocked task in the modeline, and making myself take notes
> along
As for the clocked task in the modeline, I have a command to switch
between various settings - basically "all", "today" and "this clock".
Quite useful (from time to time).
> the way using org-babel. You probably already have a more sophisticated
> workflow, but in case any of those habits could use practising or tweaking,
> maybe that could help.
Thanks!
> I wonder if it makes sense to set up pomodoros, so you have the time
> structure to accommodate interruptions/distractions as well as a regular
> reminder to check if you're still on-task.
This is a very good idea. I was thinking about it, but I have yet to
find a way to incorporate that into my workflow.
> I look forward to reading your usual awesome blog post about whatever
> workflow you figure out! :)
Thanks, now I feel quite obliged to describe it in detail! :-)
Best,
--
Marcin Borkowski
http://mbork.pl
next prev parent reply other threads:[~2018-10-29 17:18 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 16:15 An Org-based productivity tool Marcin Borkowski
2018-10-10 16:50 ` William Denton
2018-10-10 20:10 ` Marcin Borkowski
2018-10-10 20:45 ` Samuel Wales
2018-10-11 13:16 ` Roland Everaert
2018-10-11 13:25 ` Ihor Radchenko
2018-10-11 13:44 ` Roland Everaert
2018-10-11 13:56 ` Ihor Radchenko
2018-10-11 20:05 ` Samuel Wales
2018-10-11 20:05 ` Samuel Wales
2018-10-14 8:08 ` Marcin Borkowski
2018-10-16 21:04 ` Samuel Wales
2018-10-29 9:05 ` Marcin Borkowski
2018-10-11 8:58 ` Ihor Radchenko
2018-10-14 8:22 ` Marcin Borkowski
2018-10-11 14:03 ` Bingo
2018-10-11 14:57 ` Peter Neilson
2018-10-11 15:08 ` Ihor Radchenko
2018-10-14 8:19 ` Marcin Borkowski
2018-10-14 8:19 ` Marcin Borkowski
2018-10-27 7:38 ` stardiviner
2018-10-28 1:24 ` Samuel Wales
2018-10-29 9:19 ` Marcin Borkowski
2018-10-29 21:03 ` Samuel Wales
2018-10-14 8:15 ` Marcin Borkowski
2018-10-16 20:39 ` Adam Porter
2018-10-16 21:43 ` Sacha Chua
2018-10-27 7:41 ` stardiviner
2018-10-29 9:17 ` Marcin Borkowski
2018-10-29 12:31 ` Sacha Chua
2018-10-29 17:17 ` Marcin Borkowski [this message]
2018-10-25 9:45 ` Ihor Radchenko
2018-10-29 9:08 ` Marcin Borkowski
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=871s8865bl.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=sacha@sachachua.com \
/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).