emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Sacha Chua <sacha@sachachua.com>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Adam Porter <adam@alphapapa.net>, emacs list <emacs-orgmode@gnu.org>
Subject: Re: An Org-based productivity tool
Date: Mon, 29 Oct 2018 08:31:26 -0400	[thread overview]
Message-ID: <CAJGZZeLiqhFxGsBbi9JeBO54wz=KiJmBikxUBrHAm3L3SC4RBA@mail.gmail.com> (raw)
In-Reply-To: <87efc95czv.fsf@mbork.pl>

[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]

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.

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
current clocked task in the modeline, and making myself take notes along
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.

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.

I look forward to reading your usual awesome blog post about whatever
workflow you figure out! :)

Sacha

[-- Attachment #2: Type: text/html, Size: 2097 bytes --]

  reply	other threads:[~2018-10-29 12:31 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 [this message]
2018-10-29 17:17         ` Marcin Borkowski
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='CAJGZZeLiqhFxGsBbi9JeBO54wz=KiJmBikxUBrHAm3L3SC4RBA@mail.gmail.com' \
    --to=sacha@sachachua.com \
    --cc=adam@alphapapa.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    /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).