emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcelo de Moraes Serpa <celoserpa@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: [OT] Automating the process of creating 'buildlogs'
Date: Thu, 13 Sep 2012 15:14:09 -0500	[thread overview]
Message-ID: <CACHMzOHZvKyvzLm5WJG9ePyEcdikxUPd-59UzQLusHdKg2dJMg@mail.gmail.com> (raw)

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

This is kind of OT, but still relevant to org, I think..

I spend most of my day coding, and sometimes doing devops stuff. When I
can't (don't have the time, or the client just doesn't want to) automate it
with a scm system like Chef, I rely on buildlogs (all of them saved as org
files). However, I find buildlogs a pain to build manually, specially when
you are int the middle of the task - in the zone - typing, retyping,
researching etc, and still have to stop and take notes in a document.

My perfect workflow would be something like: automatically capture
everything you wrote in the terminal to a file. Then, based off this file,
add the step descriptions and any other additional information. No need to
manually copy pieces of data from the terminal to the document, risking
forgetting a step in the process.

I was wondering if any of you guys ever thought about this or done anything
to automate it? I don't use the shell from emacs, I use iTerm. One
alternative I think is to use GNU Screen and set it up to log the input (I
know a colleague of mine did that once). Another one is to setup something
from emacs that automatically saves the input data in a temp buffer and
then converts it to a org file.

I'll try one of those tonight, but if any of you guys have insights you'd
like to share, it'd be superb :)


- Marcelo.

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

                 reply	other threads:[~2012-09-13 20:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  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=CACHMzOHZvKyvzLm5WJG9ePyEcdikxUPd-59UzQLusHdKg2dJMg@mail.gmail.com \
    --to=celoserpa@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).