From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Re: FR: source code Date: Wed, 16 Jan 2008 01:55:21 +0000 Message-ID: <87abn6mt4m.fsf@bzg.ath.cx> References: <87bq7w5zp0.fsf@shellarchive.co.uk> <87hchoh0tj.fsf@bzg.ath.cx> <87fxwyobc6.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JExV2-0005tQ-0g for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 20:55:28 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JExV0-0005t5-EY for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 20:55:27 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JExV0-0005t2-A9 for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 20:55:26 -0500 Received: from fg-out-1718.google.com ([72.14.220.156]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JExV0-0002oJ-A0 for emacs-orgmode@gnu.org; Tue, 15 Jan 2008 20:55:26 -0500 Received: by fg-out-1718.google.com with SMTP id d23so80738fga.30 for ; Tue, 15 Jan 2008 17:55:25 -0800 (PST) In-Reply-To: (Eddward DeVilla's message of "Tue, 15 Jan 2008 19:21:35 -0600") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eddward DeVilla Cc: emacs-orgmode@gnu.org "Eddward DeVilla" writes: >> ,---- >> | #+BEGIN_HTML >> | #+BEGIN_LaTeX >> | #+BEGIN_TXT >> | #+BEGIN_EXAMPLE >> | #+BEGIN myblock >> `---- > > I know. I don't care for these. There really only useful if you are > exporting. For the #+BEGIN_* you're right. But dynamic blocks are useful for doing anything (clock reports, etc.) - not only exporting. > (By that I mean they are ugly (in my opinion) in the org-buffer.) Ugly but useful :/ > I'd rather see a way to mark things up so they are meaningful in the > buffer as well as export. Hence my proposal to refactor these directives and only use the dynamic block feature. When a block should be dynamically handled would depend on the associated function, not on the directive itself. > I may be a little quick on the knee jerk. In buffer markup recently > got a little weaker and I'd like for it not to be over looked with the > expectation that you can just use inline html or latex. Right, understood! -- Bastien