emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: FR: source code
Date: Wed, 16 Jan 2008 00:36:41 +0000	[thread overview]
Message-ID: <87fxwyobc6.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CF2B1348-BE3D-48A8-AAC0-5391B043D178@gmail.com> (Ed Hirgelt's message of "Wed, 9 Jan 2008 09:33:04 -0800")

Ed Hirgelt <ehirgelt@gmail.com> writes:

>> On Jan 8, 2008 8:03 AM, Bastien <bzg@altern.org> wrote:
>>> #+IF_HTML / #+ENDIF_HTML
>>> #+IF_LaTeX / #+ENDIF_LaTeX
>>> #+IF_TXT / #+ENDIF_TXT
>>>
>>> and
>>>
>>> #+BEGIN_EXAMPLE / #+END_EXAMPLE
>>> #+BEGIN myblock
>>>
>>> What people think?
>>
>> Being someone who uses org-mode primarily for the appearance in the
>> org-buffer while I'm editing and using org, I really do not like this.
>> It may format nicely after export, but it looks ugly in the buffer.
>
> I definite agree with that.  I, too, primarily use org-mode for the
> way things look in Emacs.  I occasionally export but my main use is
> within emacs.

I do agree with both reactions - I feel the same.  But this was not
really the point I was trying to make.

We already have these directives:

,----
| #+BEGIN_HTML
| #+BEGIN_LaTeX
| #+BEGIN_TXT
| #+BEGIN_EXAMPLE
| #+BEGIN myblock
`----

Would that be clearer to have:

,----
| #+IF_HTML
| #+IF_LaTeX
| #+IF_TXT
| #+BEGIN_EXAMPLE
| #+BEGIN myblock
`----

...so that the #+IF* directives tell what text to include in the target
format, while #+BEGIN* directives tell what to do with the environment:
make it an example, or insert the output of a function, etc.

But thinking about this twice, I finally think it might be better to
generalize the use of the dynamic blocks.

  #+BEGIN my_dynamic_block
  #+BEGIN 

    => inserts the output of (my_dynamic_block)

  #+BEGIN org-export :format "html"
  This will exported in HTML only.
  #+END

  #+BEGIN org-export :format "html" :fontify "emacs-lisp"
  ;; This will be exported in any format
  ;; and properly fontified thru htmlize.el
  (defgroup org nil
    "Outline-based notes management and organizer."
    :tag "Org"
    :group 'outlines
    :group 'hypermedia
    :group 'calendar)
  #+END

This way we just have one directive (#+BEGIN) and we can have several
special dynamic blocks (just as we already have one for inserting clock
reports) taking care of what we want to do with this part of the buffer.

My 2 cents,

-- 
Bastien

  parent reply	other threads:[~2008-01-16  0:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 11:22 FR: source code Phil Jackson
2008-01-08 14:03 ` Bastien
     [not found]   ` <b71b18520801082003h7baccfa9t3a0cf936c07c086a@mail.gmail.com>
2008-01-09  4:04     ` Eddward DeVilla
2008-01-09 17:33       ` Ed Hirgelt
2008-01-09 17:50         ` Russell Adams
2008-01-09 22:21           ` Adam Spiers
2008-01-16  0:36         ` Bastien [this message]
2008-01-16  1:21           ` Eddward DeVilla
2008-01-16  1:55             ` Bastien
2008-01-16  2:33           ` Tim Stewart
2008-01-16 12:05             ` Bastien
2008-01-16 16:03               ` Tim Stewart
2008-01-16 16:21 ` Carsten Dominik
2008-01-16 18:59   ` Phil Jackson
2008-01-18  8:20     ` Carsten Dominik
2008-01-18  9:59       ` Phil Jackson
2008-01-29 16:04         ` Phil Jackson
2008-01-29 18:20           ` Rick Moynihan
2008-01-29 18:32             ` Russell Adams
2008-01-29 18:49               ` Phil Jackson
2008-01-30  7:02             ` Bastien Guerry
2008-01-30  7:17           ` Bastien Guerry
2008-02-05 16:51           ` Carsten Dominik

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=87fxwyobc6.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --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).