From: Eric Schulte <schulte.eric@gmail.com>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: About commit named "Allow multi-line properties to be specified in property blocks"
Date: Tue, 15 Nov 2011 09:00:15 -0700 [thread overview]
Message-ID: <87zkfxml4g.fsf@gmail.com> (raw)
In-Reply-To: <CAGhLh6EKhiYkS8vkbKzgO3owypuvEH-XBNPaQtGah=H4+sF1oQ@mail.gmail.com> (Rainer M. Krug's message of "Tue, 15 Nov 2011 13:33:13 +0100")
Rainer M Krug <r.m.krug@gmail.com> writes:
> Is that patch on git yet? i.e. if can I switch back to HEAD and change my
> files accordingly?
>
Hi Rainer,
I've must merged all of the pending code block changes into the master
branch of the Org-mode git repository. So now would be a good time to
re-sync with the master branch.
Best -- Eric
>
> Cheers,
>
> Rainer
>
>
> On Wed, Nov 9, 2011 at 11:31 PM, Sebastien Vauban <
> wxhgmqzgwmuf@spammotel.com> wrote:
>
>> Hi Eric,
>>
>> Eric Schulte wrote:
>> > Rainer M Krug <r.m.krug@gmail.com> writes:
>> >
>> >> On Tue, Nov 8, 2011 at 11:53 PM, Eric Schulte <schulte.eric@gmail.com
>> >wrote:
>> >>
>> >>> > Perhaps inserting an assumed space separator would be more intuitive?
>> >>> > If we were to go that way it may be possible to allow variable
>> >>> > specifications such as
>> >>> >
>> >>> > #+PROPERTY: var foo=1 bar=2
>> >>> >
>> >>> > in which case properties could be easily specified on multiple lines
>> >>> > using a default space separator.
>> >>> >
>> >>> > If this seems like a good way to go I can try to update my previous
>> >>> > patch.
>> >>>
>> >>> I've updated the patch, the newest version is attached. It results in
>> >>> the following behavior.
>> >>
>> >> Looks good to me - that leaves just the question, what would hppen when
>> >> doing the following:
>> >>
>> >> #+property: var foo=1
>> >> #+property: var+ 2
>> >
>> > The above is equivalent to,
>> >
>> > #+header: :var foo=1 2
>> >
>> > which due to interaction with some logic put in place to allow the
>> > specification of un-named variables in call lines results in the
>> > following.
>> >
>> > #+property: var foo=1
>> > #+property: var+ 2
>> > #+begin_src emacs-lisp
>> > foo
>> > #+end_src
>> >
>> > #+results:
>> > : 2
>> >
>> > #+begin_src emacs-lisp :var bar=1 2
>> > bar
>> > #+end_src
>> >
>> > #+results:
>> > : 2
>> >
>> > Although generally I would say that both
>> >
>> > #+header: :var foo=1 2
>> >
>> > and
>> >
>> > #+property: var foo=1
>> > #+property: var+ 2
>> >
>> > are mal-formed variable assignments.
>>
>> I was amazed, yesterday, when you told about `foo' becoming `12' (with `1'
>> on
>> the assignment line and `2' on the continuation), but I'm glad you consider
>> this as rather ill-formed.
>>
>> >> and
>> >>
>> >> #+property: var foo="Hello "
>> >> #+property: var+ "world"
>> >
>> > This is exactly analogous to
>> >
>> > #+header: :var foo="hello" "world"
>> >
>> > which raises the expected error
>> > ``variable ""world"" must be assigned a default value''
>> >
>> > the following alternative however works as expected
>> >
>> > #+property: var foo="Hello
>> > #+property: var+ world"
>> > #+begin_src emacs-lisp
>> > foo
>> > #+end_src
>> >
>> > #+results:
>> > : Hello world
>>
>> That said, all of these seem excellent trade-off between the different
>> alternatives that have been discussed and analyzed, and they respect
>> important
>> aspects: simplicity (intuitive on reading) and powerfulness.
>>
>> Just perfect!
>>
>> Best regards,
>> Seb
>>
>> --
>> Sebastien Vauban
>>
>>
>>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-11-15 16:00 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zkfxml4g.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.