emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Tassilo Horn <tassilo@member.fsf.org>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Using orgstruct-mode to structure source code
Date: Wed, 03 Sep 2008 17:39:29 +0200	[thread overview]
Message-ID: <87tzcxdyry.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87ej41s37q.fsf@gmail.com> (Eric Schulte's message of "Wed, 03 Sep 2008 07:39:53 -0700")

"Eric Schulte" <schulte.eric@gmail.com> writes:

Hi Eric,

> Instead of putting org into the source file, would it make sense to
> put the source code into an org file.  Using MuMaMo-Mode
> http://www.emacswiki.org/cgi-bin/wiki/MuMaMo and delimiters like
>
> #+BEGIN_LISP
>
> #+END_LISP
>
> it would be possible to activate the appropriate source mode inside of
> the blocks, and it shouldn't be too hard to define an
> `org-export-to-source-code' function.

I wouldn't like that for at least two reasons.  

1) Not all files I where I use headlines for structuring are private to
   me.  Such a headline doesn't disturb anybody, but your suggestion
   works out only if everybody who needs to edit those files uses emacs
   and org.

2) All the links to files you get with `describe-function' and friends
   would point to generated files.  If I want to change something, I'd
   have to find the corresponding org file first.

Bye,
Tassilo

next prev parent reply	other threads:[~2008-09-03 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03  8:32 Using orgstruct-mode to structure source code Tassilo Horn
2008-09-03  9:36 ` Carsten Dominik
2008-09-03 10:20   ` Tassilo Horn
2008-09-03 14:39     ` Eric Schulte
2008-09-03 15:39       ` Tassilo Horn [this message]
2008-09-05  7:15     ` Carsten Dominik
2008-09-05  8:02       ` Tassilo Horn
2008-09-05  9:07         ` Carsten Dominik
2008-09-05  9:41           ` Tassilo Horn

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=87tzcxdyry.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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

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