emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Tim O'Callaghan" <tim.ocallaghan@gmail.com>
To: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: emacs IDE and org
Date: Fri, 9 May 2008 18:31:22 +0200	[thread overview]
Message-ID: <3d6808890805090931o8c731d7u20a9344d0f5235f8@mail.gmail.com> (raw)
In-Reply-To: <41DF74B043F8694186F5CC610060065F22935F@srv060fssmx.ssd.fsi.com>

2008/5/9 Rockefeller, Harry <Harry.Rockefeller@flightsafety.com>:
> Is anyone using org mode in a software development process? An IDE, emacs is
> no exception, assumes the source code is primary, having tools and methods
> to edit source code files but not org files.  org files, however, appear to
> have all those other features desired in a development process: todo items,
> requirements specifications, reference links, tabular and spreadsheet data,
> etc.  Export of various parts of the org file at different times of
> development may coincide with software process milestones.
>
>

I use Emacs for development, and have used Org to group together file
links and notes
for various projects.

>
> Org to source code seems straight forward via QUOTE, for example.  From
> source to org may be set up using special 'org import' markers such as
>
> //* Top item
>
> //  bla bla
>
> //** Sub item
>
> // bla bla
>
> where the cpp source comment character may get snipped off to use source to
> generate an org file.  Either the source or the org file may be primary.  Or
> maybe the org file is primary early in this process and eventually is
> replaced by source toward the end?
>

This sounds a bit like you want to use org for something like
"Literate Programming"?

Tim.

  reply	other threads:[~2008-05-09 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 16:18 emacs IDE and org Rockefeller, Harry
2008-05-09 16:31 ` Tim O'Callaghan [this message]
2008-05-12 20:05   ` Rockefeller, Harry

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=3d6808890805090931o8c731d7u20a9344d0f5235f8@mail.gmail.com \
    --to=tim.ocallaghan@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).