From: "Carsten Dominik" <dominik@science.uva.nl>
To: Rustom Mody <rustompmody@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: secret of Carstens speed
Date: Sun, 2 Dec 2007 21:58:52 +0100 [thread overview]
Message-ID: <acf852aa0712021258j599f5975j5095c0a3e86654b0@mail.gmail.com> (raw)
In-Reply-To: <f46c52560712020047r3c94338ekc7e9e4c51dd7b7da@mail.gmail.com>
On 12/2/07, Rustom Mody <rustompmody@gmail.com> wrote:
> I know this is somewhat OT but... Gawd Carsten you are just too fast!
> We newbies cant keep up with learning org mode with the speed with
> which you produce it! I donwloaded one tgz yesterday (my 2nd download
> in a month, 3rd if I count the 4.67c that comes with bundled with
> etch) and theres a new one today!
>
> Can we have some tips on your productivity? Yeah sure you use emacs
> and org-mode but there must be other things as well I guess.
> What emacs modes do you (most) use.
> What are the other aspects/steps of your toolchain for rolling out a
> new release?
> etc etc
Hi Rustom,
Well, a good friend of mine saw this question from you today,
and she was kind enough to suggest to me:
> maybe you should confess that you are working on org mode
> whenever you want to avoid doing other more urgent things...
Well, think it is definitely true that I am using Org-mode to
procrastinate.
On a bright note, I believe that you can easily be efficient at
doing what you love to do. I get a big kick out of creating and
maintaining this community, there a few things I enjoy more.
To answer your question more seriously:
Much of the development around Org-mode is organized around
mail. All mails that com into emacs-orgmode I immediately sort
into bugs, other ideas I'd like to at least think about, and stuff
I don't need to do anything about (thanks to people like Bastien...)
I do have a 1 hour train ride to work and another hour back, and I
tend to spend at least one of these valuable, completely un-interrupted
time slots working on Org-mode. Plus one of two evenings a week.
I try very hard to not do anything on it at work except for an
occasional email.
I have set things up so that releasing and uploading a new version
is as easy as
make relup TAG=5.16
so it is easy to do.
My computer setup: I do work mostly on a MacBook Pro, with
x11 installed, using an X11 version of Emacs - I've spent too
many years in that environment to give that up easily.
I am not a touch typer, I use 6-8 Fingers and make lots of mistakes
as all of you know who have tried to read and fix my documentation.
So there is no secret at all, it is just the joy of doing it, the drive
of feedback from you all, and a bit of addiction.
Well, there are worse things one could be addicted to...
- Carsten
prev parent reply other threads:[~2007-12-02 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 8:47 secret of Carstens speed Rustom Mody
2007-12-02 9:09 ` Manish
2007-12-02 11:01 ` Leo
2007-12-02 12:00 ` Rustom Mody
2007-12-02 20:58 ` Eddward DeVilla
2007-12-02 20:58 ` Carsten Dominik [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=acf852aa0712021258j599f5975j5095c0a3e86654b0@mail.gmail.com \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=rustompmody@gmail.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).