On Sat, Apr 14, 2001 at 04:37:26PM +0200, Ivo van der Wijk wrote:
Hmm - we can't just set it to '/', because some people have
multiple Zope instances mapped to a domain (ex: my.com/foo/
and my.com/bar/ are aliased to two different Zope instances).
I think what we need to do is figure
On Mon, Apr 16, 2001 at 08:38:16AM +0200, Martijn Pieters wrote:
On Sat, Apr 14, 2001 at 04:37:26PM +0200, Ivo van der Wijk wrote:
Hmm - we can't just set it to '/', because some people have
multiple Zope instances mapped to a domain (ex: my.com/foo/
and my.com/bar/ are aliased to two
Maybe you should into them more. I think that they are underappreciated in
the Zope world. Very rapid dev (although slower performance). A large part
of the Python dev that I am doing is geared to making ZClasses more
powerful. take a look at some of my proposals. The events in particular
Im assuming I dont have a right to do cvs checkins... so how do I get this
tiny stupid little change made, just email Brian ;P?
Make newline_to_br xml compliant br / instead of br:
--- d:\Zope-2.3.0-src\lib\python\DocumentTemplate\old_DT_Var.py Mon Apr 16
08:23
:10 2001
+++
Andy McKay wrote:
Im assuming I dont have a right to do cvs checkins... so how do I get this
tiny stupid little change made, just email Brian ;P?
Collector? Works for me 8^)
http://classic.zope.org:8080/Collector
--
| Casey Duncan
| Kaivo, Inc.
| [EMAIL PROTECTED]
`--
I suppose, its just not really a bug and I've always thought of the
collector as bug db.
Cheers.
--
Andy McKay.
- Original Message -
From: "Casey Duncan" [EMAIL PROTECTED]
To: "Andy McKay" [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, April 16, 2001 8:36 AM
Subject: Re:
For one, it doesn't seem possible to move an object more up to the root
(or anywhere not *below* the folder the object was cut/copied from). This
is partially due to the fact that the __cp (clipboard) cookie has
it's path
set to it's originating folder. I.e move /foo/bar/a to /foo/a or
to
On Mon, 16 Apr 2001, Andy McKay wrote:
I suppose, its just not really a bug and I've always thought of the
collector as bug db.
One of the options when you submit is "feature request w/patch".
So the "bug collector" probably needs a name change...
On the other hand, we all know about the
/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
Aitor Grajal Crespo
Director General
e-mail: a[EMAIL PROTECTED]
INETSYS, S.L.
ETSI Informática
Ctra. Colmenar, km. 15,500
28049 MADRID
SPAIN
Tfno : (34) 91 348 22 66 - Fax : (34) 91 348 22
66
http://www.inetsys.es
Scavenging the mail folder uncovered Aitor Grajal Crespo's letter:
Hello , my question is a bit complex ( for me ). I have :
- Linux RH 6.1
- python 1.5.2 --with-thread (source compiled)
- zope 2.2.x or zope 2.3.x (source compiled)
In any program in python with Linux (inclusive Zope),
if find(v,'\r') = 0: v=join(split(v,'\r'),'')
-if find(v,'\n') = 0: v=join(split(v,'\n'),'br\n')
+if find(v,'\n') = 0: v=join(split(v,'\n'),'br /\n')
Out of curiosity, what is the reason for using join(split(...)) instead of just
replace()? Is it really faster or something?
if find(v,'\r') = 0: v=join(split(v,'\r'),'')
-if find(v,'\n') = 0: v=join(split(v,'\n'),'br\n')
+if find(v,'\n') = 0: v=join(split(v,'\n'),'br /\n')
Out of curiosity, what is the reason for using join(split(...))
instead of just
replace()? Is it really faster or
Michael R. Bernstein wrote:
Itai Tavor wrote:
Thanks, Michael! Turns out I just had to make a few small changes in
my product to get it to work, which I discovered looking at yours.
Don't know if anything in my product that it would be interesting to
add to yours... it's aimed at
On Tue, Apr 17, 2001 at 11:11:33AM +1000, Itai Tavor wrote:
[...]
Here it is. Hope any of it is any help.
My Mutt emailer calls the .tgz file a mac-binhex and none of the
usual utilities recognize it as .tgz formatted. Anyone else have
the same problem? What's the magic key to decode this
14 matches
Mail list logo
