On Fri, 14 Jul 2006 00:17:27 +
Hannes Janetzek [EMAIL PROTECTED] wrote:
Moin,
ich hab es wirklich nur für meine Zwecke zum laufen gebracht, das
theme ist hardcoded und schlimmeres... Ach ja, aufgeräumt hab ich den
code auch nicht. :)
Ich hab jetzt noch nicht reingesehen, aber es ist doch
phriedrich wrote:
Which version of e and eloquence are you running? My e is about one week
olde (because of the CVS problems) but I had no problems at all.
Maybe cleaning away your ~/.e/e/config/default/*eloquence* helps.
Sorry, it's not the configuration dialog per se -- i did some more
Hi,
thanks for bringing this topic up.
I think we could do this without getting into problems as eloquence is
pretty stable right now and is to compiled and running without any
problems as far as I know, I got very positive feedback for it within
last time.
In past I were successful at keeping
On 3/22/06, phriedrich [EMAIL PROTECTED] wrote:
Hi,
thanks for bringing this topic up.
I think we could do this without getting into problems as eloquence is
pretty stable right now and is to compiled and running without any
problems as far as I know, I got very positive feedback for it
On Wednesday 22 March 2006 14:46, phriedrich wrote:
There's only one small point about modules and CVS in but this is not
eloquence specific: All the modules that were taken to the CVS are not
longer appearing on get-e. This isn't a problem for us using CVS and know
what modules are in, but
On Wed, 22 Mar 2006 16:03:01 -0600
Brian Mattern [EMAIL PROTECTED] wrote:
On Wednesday 22 March 2006 14:46, phriedrich wrote:
I think we should have the modules-section of get-e.org mentioning
all the modules, maybe even the ones coming with e itself and have
a note like built in or get it
Brian Mattern wrote:
How about releasing tarballs at stable points in module dev, and sticking
those up on get-e? The modules are in cvs to facilitate development (and not
as an alternative distribution method), so its still up to the maintainer to
release packages (binary or source) for
On Wed, 22 Mar 2006 17:33:26 -0500
Mike Russo [EMAIL PROTECTED] wrote:
phriedrich wrote:
I think this would be a good idea. Stable snapshots of the modules on
get-e.org and the devel-versions on CVS.
But nevertheless, I'd also mention CVS-only modules on get-e.org, just
because a list
On 3/22/06, Brian Mattern [EMAIL PROTECTED] wrote:
On Wednesday 22 March 2006 14:46, phriedrich wrote:How about releasing tarballs at stable points in module dev, and stickingthose up on get-e? The modules are in cvs to facilitate development (and notas an alternative distribution method), so its
On Wed, 22 Mar 2006 19:41:09 -0500 Ryan Little [EMAIL PROTECTED]
wrote:
On 3/22/06, Brian Mattern [EMAIL PROTECTED] wrote:
On Wednesday 22 March 2006 14:46, phriedrich wrote:
How about releasing tarballs at stable points in module dev, and
sticking those up on get-e? The modules are in
I've noticed that evolume was placed into CVS last night or the day
before and I was wondering what it would take for us to be able to get
eloquence into CVS as well ? phreidrich is the maintainer of
Eloquence and I think it would be a great addition to have in CVS
since quite a few users seem to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 13 Jan 2006, phriedrich wrote:
On Thu, 12 Jan 2006 16:51:38 -0800 (PST)
Eric Sandall [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have enlightenment from 20060110 and no prior installation of
eloquence
On Sat, 21 Jan 2006 11:15:37 +
Foxy [EMAIL PROTECTED] wrote:
[...]
thanks a lot!
I hope it works now.
http://www.phriedrich.artfact.at/eloquence.php
(eloquence-0.4.7.tar.gz)
Also includes updates to work with config_dialog changes from this
afternoon.
signature.asc
Description: PGP
On Tue, 17 Jan 2006 22:31:08 +
Foxy [EMAIL PROTECTED] wrote:
thanks a lot. It compiles now but segfaults when I try to enable it :(
Try to delete eloquence' old config then, look into the README for that.
Right on the end there's described how to do that.
Regards,
Friedrich
14 matches
Mail list logo
