From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: :session question -- and changes to #+Property: syntax Date: Sat, 08 Jun 2013 12:08:40 -0600 Message-ID: <878v2kmoyv.fsf@gmail.com> References: <51501AF2.1070405@easy-emacs.de> <8738vjugwd.fsf@gmail.com> <51516699.6090604@gmail.com> <87ip4ezf93.fsf@med.uni-goettingen.de> <87fvzi72ve.fsf@gmail.com> <87ip4e5gai.fsf@gmail.com> <87k3nmd5es.fsf@Rainer.invalid> <87sj264o0f.fsf@gmail.com> <87k3n8gf47.fsf@Rainer.invalid> <878v2l7v7s.fsf@Rainer.invalid> <87txl9u4c4.fsf_-_@gmail.com> <87bo7h82mr.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:53877) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UlNyW-0001FW-8B for emacs-orgmode@gnu.org; Sat, 08 Jun 2013 14:34:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UlNyT-0004By-Kw for emacs-orgmode@gnu.org; Sat, 08 Jun 2013 14:34:52 -0400 Received: from mail-pd0-f170.google.com ([209.85.192.170]:64939) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UlNyT-0004Bg-Ep for emacs-orgmode@gnu.org; Sat, 08 Jun 2013 14:34:49 -0400 Received: by mail-pd0-f170.google.com with SMTP id x11so262423pdj.15 for ; Sat, 08 Jun 2013 11:34:48 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org Achim Gratz writes: > Eric Schulte writes: >> As I recall I was fully in favor of applying these changes, however I am >> not qualified to address the changes to property behaviors. Hopefully >> someone who works more on that side of things can address those aspects. > > Oh wait, now I understand what you're getting at, let me explain. The > first patch that makes Org use the same regex in all places where a > property is used does indeed change some behaviour, but not the syntax > of the property line: > > :PROPERTY: VALUE > > where PROPERTY can contain any non-whitespace character (in > correspondence to how the keyword PROPERTY is treated in org.el since it > is not explicitly specified in org-element). > > However, there were other places in Org where a more restricted syntax > for properties in property drawers was used, which would have precluded > the use of ":" in property names and made it impossible to overwrite an > inherited property from a #+PROPERTY: line that has such a property > name. > > I've taken org-element as the authoritative source for the syntax and > eliminated the other interpretations based on the fact that while the > behaviour visible in the buffer (highlighting, prompts, etc.) would hint > differently, the actual property handling was using the syntax used in > org-element already. Hence if documents existed that had mistakenly > made use of these differences, they were already broken and would be > interpreted via the property API as they are now also shown after this > change. > Great. Would you be willing to go ahead and apply these changes (including documentation)? If it upsets anyone we'll sort things out on the mailing list. There are stable releases precisely so that we can experiment interactively on the development head. Thanks, -- Eric Schulte http://cs.unm.edu/~eschulte