On Wed, 2008-09-17 at 08:20 -0400, Reid.Thompson wrote:
On Wed, 2008-09-17 at 11:22 +0530, Sankar wrote:
Will such a workflow be not best done by having vi/emacs style
key-bindings for the composer body area , rather than opening a
external program ?
Is this being implemented/considered?
I think this idea is extremely valuable and merits robust discussion to
discover ways to encourage application developers to incorporate this
way of approaching data storage.
Thank you, I'm not always as coherent as I'd like when I describe my
ideas and knowing it made sense to you gives me
I think it would be important to distinguish between a local cache of a
remote IMAP or CalDAV folder (i.e. Configuration) vs. local mail
folders, calendars, contact lists, etc. (Data).
I agree, I regretted not making a note about cache data. Caches are
temporary stores, if it makes
So here is the plan :
* Drop Evolution copyright assignments and make it really easy to
contribute to Evolution
* Move Evolution licensing to LGPL v2 and LGPL v3 to let us re-use
the code more easily around the platform. This also moves us closer to
Shouldn't the Telepathy framework be considered for storing account settings?
Evolution-hackers mailing list
Trying to build evo# on mono-2.0 we get this error:
/usr/bin/gacutil /i evolution-sharp.dll /f /package evolution-sharp /root
Failure adding assembly evolution-sharp.dll to the cache: Strong name cannot be
verified for delay-signed assembly
Nice thoughts, really nice thoughts!
But I have to defend cheese! You're right, storing the pictures in a
hidden directory is not that good! The maintainer of cheese, daniel
siegel implemented it this way, because he thought storing all these
random-crazy-looking-pictures taken with cheese in
Permission granted to relicence my code (committed as
[EMAIL PROTECTED] or [EMAIL PROTECTED]).
On Fri, 2008-07-11 at 04:21 -0600, Srinivasa Ragavan wrote:
We have had a set of problems that we are carrying around for some time like :
Since we do really want to remove the fork and pick up packages from
upstream, I can change the apis in evolution related packages if a new
set of apis with some suffix is provided from libical upstream.
Many of you have probably already read this on the libical mailing list,
but just in
On 13/09/08 11:48, Martin Owens wrote:
Technically configuration directories denoted by being hidden
(suffexed with a '.') are there to hold collections of configuration
files for the applications which they serve. But there are plenty of
programs using these directories to store the data
Mail list logo