emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Eric Schulte" <schulte.eric@gmail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Property inheritance for MAIL_FMT, MAIL_TO, MAIL_CC and MAIL_BCC
Date: Fri, 14 Jan 2011 06:32:57 -0700	[thread overview]
Message-ID: <87sjwv7gfh.fsf@gmail.com> (raw)
In-Reply-To: 80aaj3bzps.fsf@missioncriticalit.com

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 <wxhgmqzgwmuf@spammotel.com> writes:

> Hi Eric and Niels,
>
> "Eric Schulte" wrote:
>> niels giesen <niels.giesen@gmail.com> 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

     prev parent reply	other threads:[~2011-01-14 13:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 22:47 Property inheritance for MAIL_FMT, MAIL_TO, MAIL_CC and MAIL_BCC niels giesen
2011-01-14  0:11 ` Eric Schulte
2011-01-14  9:29   ` Sébastien Vauban
2011-01-14 13:32     ` Eric Schulte [this message]

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=87sjwv7gfh.fsf@gmail.com \
    --to=schulte.eric@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

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).