From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: modify face of org-scheduled-previously depending of priority
Date: Thu, 07 Nov 2013 22:15:26 +0100
Message-ID: <87r4arap75.fsf@bzg.ath.cx>
References: <uaxhabokyjx.fsf@beesknees.cern.ch>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:52897)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1VeWvQ-0004E2-Im
	for emacs-orgmode@gnu.org; Thu, 07 Nov 2013 16:15:42 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1VeWvK-0005e4-Ol
	for emacs-orgmode@gnu.org; Thu, 07 Nov 2013 16:15:36 -0500
Received: from mail-we0-x235.google.com ([2a00:1450:400c:c03::235]:35236)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@gmail.com>) id 1VeWvK-0005dv-HR
	for emacs-orgmode@gnu.org; Thu, 07 Nov 2013 16:15:30 -0500
Received: by mail-we0-f181.google.com with SMTP id t60so1114720wes.40
	for <emacs-orgmode@gnu.org>; Thu, 07 Nov 2013 13:15:29 -0800 (PST)
In-Reply-To: <uaxhabokyjx.fsf@beesknees.cern.ch> (David Belohrad's message of
	"Thu, 07 Nov 2013 16:43:14 +0100")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: David Belohrad <david@belohrad.ch>
Cc: Org-mode <emacs-orgmode@gnu.org>

Hi David,

David Belohrad <david@belohrad.ch> writes:

> is there any way how I could programmatically assign to
> org-scheduled-previously the same colors as they are by current
> priority?

Nope -- this would require changes in the code, and I don't think
this use-case is general enough to make these changes.  My own advice,
of course, other core contributors might think otherwise.

-- 
 Bastien