From: Bastien <bzg@altern.org>
To: mail@christianmoe.com
Cc: Nicolas Goaziou <n.goaziou@gmail.com>,
Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: About commit named "Allow multi-line properties to be specified in property blocks"
Date: Wed, 02 Nov 2011 16:35:22 +0100 [thread overview]
Message-ID: <87hb2mo7ek.fsf@altern.org> (raw)
In-Reply-To: <4EAF118C.8050806@christianmoe.com> (Christian Moe's message of "Mon, 31 Oct 2011 22:22:20 +0100")
Dear all,
here is my take on this issue.
First of all, sorry that the #+begin_property caused confusion,
I'm the one responsible as I suggested this suggestion to Eric.
I can see three issues:
1) Consistent syntax for #+xxx and #+begin_xxx?
Nicolas point is valid -- #+begin_xxx syntax is about content and
formatting, not about Org's internal. #+xxx is mostly about Org's
internals (#+author, #+date, #+property, etc) and sometimes about
content, as a convenient way of inserting one-line content block
(#+html, #+LaTeX, etc)
#+begin_property does not fit well into this picture.
2) "Cumulative properties"?
Org's manual describes #+property like this:
`#+PROPERTY: Property_Name Value'
This line sets a default inheritance value for entries in the
current buffer, most useful for specifying the allowed values
of a property.
Note that #+property: var foo=1 does *not* fit into the syntax
described above. It is more something like
`#+PROPERTY: var Variable_Name=Value'
Hence the problem of accumulating the "values" of "var", which
is not really a property name, but some syntactic clue to bind
Variable_Name to its value.
Here is a suggestion: use a syntaxe like
#+var: foo 1
The difference between #+property and #+var would be that #+var
is for setting general purpoes (elisp) variables, while #+property
is for Org internals. Sorry if such a proposal has already been
made and discussed.
My feeling is that `org-accumulated-properties-alist' is complex
and can be avoided -- but I need to think more about this.
3) Wrapping/folding long #+xxx lines?
This is an independant request -- see Robert McIntyre's recent
question on the list. The problem is that fill-paragraph on
long #+xxx lines breaks the line into comment lines, which is
wrong. Filling like this:
#+TBLFM: @3$1=@1$1+@2$1::@3$2=@1$2+@2$2::...::...
: @3$2=@1$2+@2$2::...
: @3$2=@1$2+@2$2::...
would feel more natural, at least to me. But maybe generalizing
the #+begin_xxx syntax for *all* #+xxx keywords. This would make the
current org-internals-oriented/content-oriented difference between
#+xxx and #+begin_xxx obsolete, but this would spare us the cost of
new syntax. Curious about input about this as well.
Cheers,
--
Bastien
next prev parent reply other threads:[~2011-11-02 15:44 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 19:06 About commit named "Allow multi-line properties to be specified in property blocks" Nicolas Goaziou
2011-10-31 20:05 ` Eric Schulte
2011-10-31 20:49 ` Nicolas Goaziou
2011-10-31 21:30 ` Eric Schulte
2011-11-01 8:24 ` Nicolas Goaziou
2011-11-01 8:36 ` Nicolas Goaziou
2011-11-01 14:36 ` Eric Schulte
2011-11-01 15:39 ` Nicolas Goaziou
2011-11-01 16:58 ` Eric Schulte
2011-11-01 17:48 ` Christian Moe
2011-11-01 19:02 ` Eric Schulte
2011-11-01 19:45 ` Christian Moe
2011-11-01 20:22 ` Eric Schulte
2011-10-31 21:33 ` Christian Moe
2011-10-31 21:22 ` Christian Moe
2011-10-31 21:36 ` Eric Schulte
2011-11-01 7:33 ` Christian Moe
2011-11-02 15:35 ` Bastien [this message]
2011-11-02 17:39 ` Nicolas Goaziou
2011-11-03 1:26 ` Bastien
2011-11-03 8:08 ` Christian Moe
2011-11-03 15:10 ` Nick Dokos
2011-11-03 18:32 ` Eric Schulte
2011-11-03 20:01 ` Nicolas Goaziou
2011-11-03 20:18 ` Eric Schulte
2011-11-03 20:23 ` Eric Schulte
2011-11-04 8:02 ` Rainer M Krug
2011-11-04 17:48 ` Darlan Cavalcante Moreira
2011-11-04 19:25 ` Eric Schulte
2011-11-07 22:09 ` Eric Schulte
2011-11-08 8:42 ` Rainer M Krug
2011-11-08 9:31 ` Sebastien Vauban
2011-11-08 9:41 ` Rainer M Krug
2011-11-08 9:58 ` Sebastien Vauban
2011-11-08 10:06 ` Rainer M Krug
2011-11-08 14:42 ` Darlan Cavalcante Moreira
2011-11-08 15:06 ` Sebastien Vauban
2011-11-08 16:03 ` Eric Schulte
2011-11-08 22:53 ` Eric Schulte
2011-11-09 8:25 ` Rainer M Krug
2011-11-09 16:12 ` Eric Schulte
2011-11-09 17:18 ` Rainer M Krug
2011-11-09 22:31 ` Sebastien Vauban
2011-11-15 12:33 ` Rainer M Krug
2011-11-15 16:00 ` Eric Schulte
2011-11-15 16:37 ` Torsten Wagner
2011-11-15 16:56 ` Eric Schulte
2011-11-15 17:13 ` Thomas S. Dye
2011-11-15 18:22 ` Eric Schulte
2011-11-15 17:24 ` Rainer M Krug
2011-11-08 9:41 ` Sebastien Vauban
2011-11-08 9:44 ` Rainer M Krug
2011-11-08 16:01 ` Eric Schulte
2011-11-02 21:05 ` Samuel Wales
2011-11-02 21:21 ` Samuel Wales
2011-11-03 1:42 ` Bastien
2011-11-03 8:19 ` Christian Moe
2011-11-03 18:34 ` Eric Schulte
2011-11-03 18:59 ` Eric Schulte
2011-11-09 17:40 ` Samuel Wales
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=87hb2mo7ek.fsf@altern.org \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--cc=n.goaziou@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).