emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <r.m.krug@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: About commit named "Allow multi-line properties to be specified in property blocks"
Date: Tue, 8 Nov 2011 10:41:30 +0100	[thread overview]
Message-ID: <CAGhLh6Gkb+449h2ddpfJmkpakK04OxYRCH0heDq7Rrgfv08=Gg@mail.gmail.com> (raw)
In-Reply-To: <80d3d3neof.fsf@somewhere.org>

[-- Attachment #1: Type: text/plain, Size: 3212 bytes --]

On Tue, Nov 8, 2011 at 10:31 AM, Sebastien Vauban <
wxhgmqzgwmuf@spammotel.com> wrote:

> Hi Eric,
>
> (Due to a high "buzyness" level, I've been a bit out of the discussion for
> one
> week or so)
>
> Eric Schulte wrote:
> > The attached patch implements this latest "propname+" suggestion.  When
> > applied it results in the behavior shown below.
> >
> > I'm inclined to go with this as a solution moving forward.
> >
> > Thoughts?
> >
> > #+property: var    foo=1
> > #+property: var+ , bar=2
> > #+begin_src emacs-lisp
> >   (+ foo bar)
> > #+end_src
>
> So, in a way, adding the + after `var' is how you tell Org that this is an
> accumulated property?
>
> Two questions:
>
> 1. Why not the + after the property keyword (property+)? I guess because
> it's
>   more against other aspects of Org internals?  Anyway, putting + after the
>   var sounds as right to me -- maybe better even if we consider that you
>   declare var as accumulated, writing so.
>
> 2. Must there be a first `var' without `+'?  Accepted, tolerated or wrong?
>  I
>   mean, I'm sure that, due to heavy file editing, we'll sometimes have:
>

Might be a good idea to tolerate this.


>
>   #+property: var+   foo=1
>   #+property: var+ , bar=2
>   #+begin_src emacs-lisp
>     (+ foo bar)
>   #+end_src
>
> > #+results:
> > : 3
> >
> > #+begin_src emacs-lisp
> >   (org-entry-get (point) "var" t)
> > #+end_src
> >
> > #+results:
> > : foo=1, bar=2
> >
> > * overwriting a file-wide property
> >   :PROPERTIES:
> >   :var:      foo=7
> >   :END:
> >
> > #+begin_src emacs-lisp
> >   foo
> > #+end_src
> >
> > #+results:
> > : 7
> >
> > #+begin_src emacs-lisp
> >   (org-entry-get (point) "var" t)
> > #+end_src
> >
> > #+results:
> > : foo=7
> >
> > * appending to a file-wide property
> >   :PROPERTIES:
> >   :var+:      , baz=3
> >   :END:
>
> To be honest, the only thing that I dislike is the comma in the above line.
> Not intuitive at all. Quite hard to read.
>
> Can't the comma be implicitly added by the `+' after the property name?
>

On the one hand, it might have one additional advantage:

  #+property: var   foo="This is a very long text"
  #+property: var+ "with even more."

Would foo be:
"This is a very long text with even more"

Could one make the "," implicit, if the value follows the

x=y

style, while otherwise just concatenate the value to the one before?




> That would allow one to simply write:
>
>   * appending to a file-wide property
>     :PROPERTIES:
>     :var+:        baz=3
>     :END:
>
> and have the correct values.
>
> > #+begin_src emacs-lisp
> >   (+ foo bar baz)
> > #+end_src
> >
> > #+results:
> > : 6
> >
> > #+begin_src emacs-lisp
> >   (org-entry-get (point) "var" t)
> > #+end_src
> >
> > #+results:
> > : foo=1, bar=2, baz=3
>
> Thanks.
>
> Best regards,
>  Seb
>
> --
> Sebastien Vauban
>
>
>


-- 
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)

Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa

Tel :       +33 - (0)9 53 10 27 44
Cell:       +33 - (0)6 85 62 59 98
Fax (F):       +33 - (0)9 58 10 27 44

Fax (D):    +49 - (0)3 21 21 25 22 44

email:      Rainer@krugs.de

Skype:      RMkrug

[-- Attachment #2: Type: text/html, Size: 4704 bytes --]

  reply	other threads:[~2011-11-08  9:41 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 [this message]
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='CAGhLh6Gkb+449h2ddpfJmkpakK04OxYRCH0heDq7Rrgfv08=Gg@mail.gmail.com' \
    --to=r.m.krug@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wxhgmqzgwmuf@spammotel.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).