emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: LanX <lanx.perl@googlemail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Embedding org-syntax in program source
Date: Wed, 14 Apr 2010 01:54:13 +0200	[thread overview]
Message-ID: <w2vec36f5051004131654oc62ea56if149e0be824e43ef@mail.gmail.com> (raw)
In-Reply-To: <87k4sbrqdf.fsf@stats.ox.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 2257 bytes --]

Hi Dan


>
> Right. Given the present forum I presume you are using emacs, so that
> shouldn't be a problem per se?
>

Well, don't you think that telling other people that changing the
_source_-code requires emacs might be a problem?


>
> I think you may have formed an inaccurate idea of how people are working
> with source code in org-mode.
>
> maybe... and I have to admit my knowledge of LP is theoretical (but at
least I investigated  the sources of TeX long ago! :)

my idea for the beginning was to extend my codes with org-modes folding,
linking and some TODO features in perl comments. Maybe automatically
switching the mode when the cursor is entering/leaving comments.

Multiline wouldn't be a problem since I can include them in POD (perl's
simplified approach to LP)

or I could embrace them in heredocs, for instance the following is legal
perlcode as long as the last line is empty (no whitespaces allowed).

<<;
* block1
** [test] bla


> And relying on an extra step for code generation is dangerous...
>
> You would have to explain that assertion.


Sorry, no offence intended, this is the common sense of perlmonks when
talking about run time code generation and adding extra dependencies. (Maybe
not the appropriate slang here...)

I wouldn't find many to join my projects when relying on extra make files
and I suppose running emacs in batch mode to tangle the code is not that
stable.

> This is for sure acceptable with elisp or multilanguage projects.

I didn't understand this.
>

emacs is a natural habitat of elisp , like unix is one for C.

And multilanguage projects would naturally rely on some make mechanisms.




> > PS: I forgot to mention that when switching to other modes the
> highlighting
> > will also get confused and fly-make will report plenty of syntax
> problems.
>
> I'm not sure what you mean here. When working with code in org-mode, one
> uses C-c ' to switch to a language major-mode buffer containing the body
> of the source code block. Is that working OK for you?
>

hm, yes ...but if I do this I could equally embrace all org-mode-stuff in
between "=pod"-lines or prepend a # to each line when switching to
cperl-mode.

Hooking this to save would guaranty to always have legal perlcode...

bye
  Rolf

[-- Attachment #1.2: Type: text/html, Size: 3420 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2010-04-13 23:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 10:32 Embedding org-syntax in program source LanX
2010-04-13 15:08 ` Eric Schulte
     [not found]   ` <y2wec36f5051004130835k5d850907h35f6645b5f5fef17@mail.gmail.com>
2010-04-13 15:40     ` LanX
2010-04-13 16:47       ` Eric Schulte
2010-04-13 21:31       ` Dan Davison
2010-04-13 23:54         ` LanX [this message]
2010-04-14 12:39           ` Sebastian Rose
2010-04-14 15:22           ` Dan Davison
2010-04-13 16:12 ` Dan Davison

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=w2vec36f5051004131654oc62ea56if149e0be824e43ef@mail.gmail.com \
    --to=lanx.perl@googlemail.com \
    --cc=davison@stats.ox.ac.uk \
    --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).