all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Modern conventions for structuring Emacs Lisp libraries
Date: Sun, 06 Oct 2013 14:13:07 -0400	[thread overview]
Message-ID: <jwv8uy6l1bw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87vc1ae1on.fsf@gmail.com> (Thorsten Jolitz's message of "Sun, 06 Oct 2013 19:42:16 +0200")

> The first thing when looking at a library is getting an overview about
> its structure - with tools like e.g. navi-mode.
> For me its a huge difference then if I look at a well balanced and
> logical hierachical tree-structure (org-element.el and ox.el are perfect
> examples for this) or at something that seems inherently wrong and
> illogical at first sight.

Then fix navi-mode to show you the structure you want.  It's not like
the info is missing.

> This seems the least important point, but again I ask myself: why
> continue recommend the colons, when it turns out they don't look so
> good in exports?

Because I have much better things to do with my time than have to deal
with such nasty decades-long transitions.

>> Damn!  You skipped the part I was looking for: the "Commentary:"
>> section.  I do want this part to be refined.  More specifically, I'd
>> like someone to come up with a description of a markup format to use
>> there (99% compatible with what we already have), together with code
>> that can turn such a Commentary section into nicely rendered text in an
>> Emacs buffer.

> If I understand you right, maybe there is good news. Install and load
> outshine.el and outorg.el, move point on the "Commentary:" header and do
> 'M-x outorg-edit-as-org' (or M-# M-#).

> Then you will be offered that headline converted to Org in a temporary
> Org-mode edit buffer (*outorg-edit-buffer*). In that buffer, you can use
> the power of Org-mode for writing really complex commentary text, even
> using Org-Babel for executing code and inserts results, and then export
> the commentary section nicely formatted to HTML, LaTeX, ODT, ASCII and
> other backends.

Exporting to HTML will be useful, but I first and foremost want it to be
displayed nicely in an Emacs buffer.  The markup should be simple enough
that existing Commentary sections mostly follow it already, and that you
mostly don't need any extra support to write it.


        Stefan



  reply	other threads:[~2013-10-06 18:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 13:31 Modern conventions for structuring Emacs Lisp libraries Thorsten Jolitz
2013-10-05 16:52 ` Richard Stallman
2013-10-06 16:40   ` Thorsten Jolitz
2013-10-06 18:04     ` Stefan Monnier
2013-10-07  0:36     ` Xue Fuqiao
2013-10-05 16:52 ` Richard Stallman
2013-10-05 19:18   ` Daniel Colascione
2013-10-06  8:20     ` legalese haters club Stephen J. Turnbull
2013-10-06 19:21     ` Modern conventions for structuring Emacs Lisp libraries Richard Stallman
2013-10-06 16:51   ` Thorsten Jolitz
2013-10-06 18:07     ` Stefan Monnier
2013-10-06  0:42 ` Stefan Monnier
2013-10-06  3:20   ` Xue Fuqiao
2013-10-06  4:47     ` Drew Adams
2013-10-06 17:42   ` Thorsten Jolitz
2013-10-06 18:13     ` Stefan Monnier [this message]
2013-10-06 19:31     ` Josh
2013-10-06 19:58       ` Pascal J. Bourguignon

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv8uy6l1bw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=tjolitz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.