Re: [Orgmode] Re: Property inheritance for MAIL_FMT, MAIL_TO, MAIL_CC and MAIL_BCC

[Eric Schulte]

Hi Seb,

Good idea, I've just placed this behind a new
`org-mime-use-property-inheritance' variable which will default to nil.
I was originally going to have this variable default to t, but the idea
of causing people to accidentally add unintended recipients to emails is
too scary.

Thanks for the suggestion -- Eric

Sébastien Vauban <address@hidden> writes:

> Hi Eric and Niels,
>
> "Eric Schulte" wrote:
>> niels giesen <address@hidden> writes:
>>> Please see the patch below, it adds property inheritance for all
>>> MAIL_* properties, based on the value of
>>> `org-use-property-inheritance'.
>>
>> Thanks for the patch, and for the motivating usage example. -- Eric
>
> If I understand correctly, one must enable =org-use-property-inheritance= for
> the above to be in effect.
>
> Though, this is discouraged in the doc:
>
>     ,----
>     | org-use-property-inheritance is a variable defined in `org.el'.
>     | Its value is nil
>     | 
>     | Documentation:
>     | Non-nil means properties apply also for sublevels.
>     | 
>     | This setting is chiefly used during property searches.  Turning it on 
> can
>     | cause significant overhead when doing a search, which is why it is not
>     | on by default.
>     `----
>
> Couldn't we either:
>
> - consider the MAIL_* properties as the *_ALL ones that well have inheritance
>   enabled by default?
>
>     ,----
>     | However, note that some special properties use inheritance under special
>     | circumstances (not in searches).  Examples are CATEGORY, ARCHIVE, 
> COLUMNS,
>     | and the properties ending in "_ALL" when they are used as descriptor
>     | for valid values of a property.
>     `----
>
> - have a setting allowing for the inheritance of just these special
>   properties, as an extra, in order not to penalize too much the searches?
>
> Best regards,
>   Seb