From: Robert Horn <rjhorn@alum.mit.edu>
To: Torsten Wagner <torsten.wagner@gmail.com>, orgmode@grierwhite.com
Cc: emacs-orgmode@gnu.org
Subject: Re: are super-hidden technical blocks required?
Date: Tue, 07 Aug 2012 10:30:39 -0400 [thread overview]
Message-ID: <m3fw7ybwq8.fsf@quad.robs.office> (raw)
In-Reply-To: <CAPaq-gPRoYVC3+Wf7y_6jcMev4f4VZx=aPX7hvsO54YByFOyKQ@mail.gmail.com>
Separating out the issue of how to hide and expose the content, why not
use s-expressions for the hidden content? Org is built on a lisp engine
and these will fit nicely into automation. It avoids a lot of parsing
and other headaches, and an s-expression can hold any of the discussed information.
It could be an a-list that is designed for the purpose, or it could be a
list structured like the custom configuration list used in emacs config.
I think of the latter when considering the potential to steal code for
using the contents, updating the contents, and providing a user
interface when that is needed. It also provides a model for sharing the
list among independent groups of developers with overlapping interests.
It permits automatically generated comments, advice, and warnings for
those who look at it, much like you find when looking over the tail end
of a .emacs file.
The property construction could then be a simple
:HIDDEN-ALIST-PROPERTIES: (( stuff ........))
It would be very unreadable and unfriendly to the novice, but that is
already a characteristic of the data being discussed.
R Horn
rjhorn@alum.mit.edu
next prev parent reply other threads:[~2012-08-07 14:30 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 2:26 are super-hidden technical blocks required? Torsten Wagner
2012-07-30 7:26 ` Bastien
2012-07-30 10:27 ` Rasmus
2012-07-30 14:27 ` Russell Adams
[not found] ` <CAPaq-gMV-+n6OAN4PnBsh1eiJ5wA=Ns_m_qwHqz1pxbOxeYCCQ@mail.gmail.com>
2012-07-31 2:04 ` Fwd: " Torsten Wagner
2012-07-30 14:42 ` Ivy Foster
2012-07-30 15:23 ` Jonathan Leech-Pepin
2012-07-31 13:23 ` Robert Horn
2012-07-31 13:47 ` Torsten Wagner
2012-08-04 18:10 ` Ilya Shlyakhter
2012-08-05 9:16 ` Bastien
2012-08-05 20:04 ` Ilya Shlyakhter
2012-08-05 22:20 ` Nicolas Goaziou
2012-08-05 22:50 ` Ilya Shlyakhter
2012-08-06 2:46 ` Torsten Wagner
2012-08-06 3:01 ` Ilya Shlyakhter
2012-08-06 12:12 ` Jonathan Leech-Pepin
2012-08-06 17:25 ` Ilya Shlyakhter
2012-08-06 18:16 ` Allen S. Rout
2012-08-06 19:01 ` Michael Brand
2012-08-07 21:29 ` Ilya Shlyakhter
2012-07-31 2:48 ` Torsten Wagner
2012-08-01 13:29 ` Bastien
2012-08-02 1:19 ` Torsten Wagner
2012-08-06 15:02 ` Christopher J. White
2012-08-01 17:11 ` Achim Gratz
2012-08-01 18:39 ` Bernt Hansen
2012-08-01 18:49 ` Achim Gratz
2012-08-02 1:16 ` Torsten Wagner
2012-08-02 15:10 ` Bastien
2012-08-07 21:33 ` Ilya Shlyakhter
2012-08-02 13:01 ` babel awk with table input: Code block produced no output Greg Minshall
2012-08-02 13:21 ` Sebastien Vauban
2012-08-03 2:08 ` [BUG] Traceback on Org-Export Luis Anaya
2012-08-03 7:19 ` Bastien
2012-08-03 10:27 ` Luis Anaya
2012-08-04 13:06 ` Achim Gratz
2012-08-04 14:13 ` Achim Gratz
2012-08-04 17:58 ` Bastien
2012-08-04 21:07 ` Achim Gratz
2012-08-05 9:44 ` Bastien
2012-08-05 15:44 ` Achim Gratz
2012-08-03 10:43 ` Luis Anaya
2012-08-03 11:17 ` Giovanni Ridolfi
2012-08-03 11:32 ` Luis Anaya
2012-08-03 14:34 ` Nick Dokos
2012-08-03 20:09 ` Achim Gratz
2012-08-05 23:57 ` babel awk with table input: Code block produced no output Greg Minshall
2012-08-06 1:36 ` Thomas S. Dye
2012-08-06 4:59 ` Greg Minshall
2012-08-06 15:37 ` Change: no longer automatically evaluate embedded elisp in code block output Was: " Eric Schulte
2012-08-08 5:00 ` Greg Minshall
2012-08-07 3:12 ` are super-hidden technical blocks required? Torsten Wagner
2012-08-07 10:23 ` Bastien
2012-08-07 13:20 ` Torsten Wagner
2012-08-07 13:39 ` Christopher J. White
2012-08-07 14:11 ` Torsten Wagner
2012-08-07 14:30 ` Robert Horn [this message]
2012-08-14 9:58 ` Bastien
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=m3fw7ybwq8.fsf@quad.robs.office \
--to=rjhorn@alum.mit.edu \
--cc=emacs-orgmode@gnu.org \
--cc=orgmode@grierwhite.com \
--cc=torsten.wagner@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 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).