From: Torsten Wagner <torsten.wagner@gmail.com>
To: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: are super-hidden technical blocks required?
Date: Tue, 31 Jul 2012 11:48:51 +0900 [thread overview]
Message-ID: <CAPaq-gPffs_KOZA4HWj+kfFt6d19N-v-JtMZXby3P2c8P=5E-Q@mail.gmail.com> (raw)
In-Reply-To: <CAPaq-gPEPrun74X_m-ULQpZgs3BLu_zTG0WR=9B9DoJQkok6wg@mail.gmail.com>
Hi,
I was aware that some people would prefer a more transparent way.
I think a technical property block accessible for third party sync
tools would make it much easier for the developers of those tools.
On the other hand I understand that people want to know what is stored
along within there org-files.
One Idea I had and which was mentioned by Rasmus already too, would be
to use the same property block but being able to hide certain
properties
#+ HIDE_PROP: ID, UUID, ODF_PROP, MOBILE_ORG_PROP
I guess many people use only one or the other third party tool and
hence once set-up correctly in there files, its rather easy to mask
them invisible or visible depending on personal preferences and needs.
This approach makes people also actively aware of those properties and
does not try to hide them.
Maybe for the upcoming future if programs would like to introduce
rather many properties the list could be sensitive to wildcards?!
so #+ HIDE_PROP: ODF_*
would hide all properties introduced for ODF in- and export.
even a pure technical block could be realized by this if there is a
rule to start properties of sole technical purpose by a certain
key-character e.g. a underline (if this is legal as property name, not
sure about). Then _* would hide all technical properties. _ODF_* hides
all technical properties for ODF _OM_* does the same for orgmobile,
etc. Developers could decide whether a property is more of technical
nature or if user should be more aware of it (and possibly change it).
Using not only wildcards but real regular expression (which might not
be to difficult in elisp) would make this even more flexible.
To indicate that a property block contains hidden technical properties
I guess, as usual in org-mode a line of "..." could indicate this.
E.g.,
#+ HIDE_PROP: _*
* Test
:PROPERTIES:
:name: Max Muster
:address: Muster-Street 1,
:tel: 11223344
...
:END:
#+ HIDE_PROP:
* Test
:PROPERTIES:
:name: Max Muster
:address: Muster-Street 1,
:tel: 11223344
:_UUID: 123j2k2j32kj332k1j2h1ghj1g321
:_OM_COLOUR: red
:_OM_image: ./max_muster.jpg
:_SYNC_TS_UNIX: 1342483647
:_OR_CODE: ./max_muster_QR.png
:END:
I guess this solution would fit to everyone, people who like to know
what is stored within there org-files and people who want a clutter
free org-file for easy reading (and sure people can easily switch
between both approaches). Finally, developers would have a rather easy
and out-of-the-way possibility to save as much information within the
org-file as needed to e.g. enable 2-way syncs with other programs.
After all, everything still keeps plain text.
Any thoughts?
Torsten
next prev parent reply other threads:[~2012-07-31 2:48 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 [this message]
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
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='CAPaq-gPffs_KOZA4HWj+kfFt6d19N-v-JtMZXby3P2c8P=5E-Q@mail.gmail.com' \
--to=torsten.wagner@gmail.com \
--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).