You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Rob Bloodgood <ro...@empire2.com> on 2002/03/14 20:30:54 UTC
[WOT] emacs and WEBDAV
I'm running a Mason based website, and I use Emacs when I write code.
My web designers use Dreamweaver. I've designed the site so that my web
guys have to reserve me one table cell (or more than one depending on where
in the site, but you get the point) where I put a single dispatch component
to the dynamic content appropriately.
The problem is, concurrency. Dreamweaver has versioning built in... but
emacs has no way to recognize it. So when I make a fix to a file, if the
designers aren't explicitly instructed to refresh-from-the-website-via-ftp,
my changes get hosed.
DW also speaks WEBDAV natively, but emacs does not. Emacs speaks CVS
natively, but DW does not. DW also speaks SourceSafe <shudder>, but I never
took that seriously... :-)
I've been trying, in various attempts over the past two years, to come up
with a compromise between the two. The closest I've come was somebody
mentioned a CVS emulation layer over a DAV repository... but that never came
to fruition. And even more frustrating, I haven't managed to pick up enough
eLisp to do it myself w/ vc.el <sigh>.
Does anybody have any ideas for my next direction to turn?
TIA!
L8r,
Rob
Re: [WOT] emacs and WEBDAV
Posted by Michael Alan Dorman <md...@debian.org>.
"Rob Bloodgood" <ro...@empire2.com> writes:
> DW also speaks WEBDAV natively, but emacs does not.
Not natively, but there is a DAV mode for emacs, apparently fairly
new. From the Debian package:
Package: eldav
Priority: optional
Section: net
Installed-Size: 61
Maintainer: Fumitoshi UKAI <uk...@debian.or.jp>
Architecture: all
Version: 0.0.20020311-1
Depends: emacs21 | emacsen, nd (>= 0.5.0)
Filename: pool/main/e/eldav/eldav_0.0.20020311-1_all.deb
Size: 14286
MD5sum: 71271d5d4998dcdb78f83d79e98a4f75
Description: an interface to the WebDAV servers for Emacs.
WebDAV files can be treated just like a normal file in Emacsen.
Emacs/w3 is not required. External program is used for WebDAV access.
Re: [WOT] emacs and WEBDAV
Posted by Tatsuhiko Miyagawa <mi...@edge.co.jp>.
At Thu, 14 Mar 2002 11:30:54 -0800,
Rob Bloodgood wrote:
> DW also speaks WEBDAV natively, but emacs does not. Emacs speaks CVS
Eldav: Yet another WebDAV interface for Emacsen
http://www.gohome.org/eldav/
--
Tatsuhiko Miyagawa <mi...@edge.co.jp>
Re: [WOT] emacs and WEBDAV
Posted by "Keith G. Murphy" <ke...@mindspring.com>.
Kee Hinckley wrote:
>
> Emacs over WebDAV should work fine if you run something that supports
> WebDAV as a filesystem (e.g. OSX), but that's not going to help you
> much.
>
If you're running Linux, this looks like fun:
http://sourceforge.net/projects/dav
There's also kiwifs:
http://kiwi.stanford.edu
If you're only running Linux on the server, well, maybe you could roll
something with samba (maybe you would need kernel oplocks?).
Seems like all the good stuff is for Linux, doesn't it? ;-)
RE: [WOT] emacs and WEBDAV
Posted by Rob Bloodgood <ro...@empire2.com>.
> At 11:30 AM -0800 3/14/02, Rob Bloodgood wrote:
> >The problem is, concurrency. Dreamweaver has versioning built
> >in... but emacs has no way to recognize it. So when I make a fix
> >to a file, if the designers aren't explicitly instructed to >
> >refresh-from-the-website-via-ftp, my changes get hosed.
>
> Versioning, no. Locking, yes, optionally. (Well, I guess it can do
> versioning via SourceSafe, but not via anything else.) I'm seriously
> hoping they'll address that in the next release.
<sigh> I meant locking. Not versioning. e-Foot in e-Mouth.
> Emacs over WebDAV should work fine if you run something that supports
> WebDAV as a filesystem (e.g. OSX), but that's not going to help you
> much.
If we're talking about LOCKING, is this statement still true?
> There are two options I can think of.
>
> 1. If your designers aren't making use of checkin/checkout in
> DreamWeaver, then simply make it clear to them that before they can
> save a file to the server, they have to do a sync first. Make the
> final repository sit on CVS, and do a checkin every night. So if
> something does go wrong you can at least pick up the previous day's
> work.
That (the train-them-to-sync-first part) has been what I've been forced to
do so far. I haven't gone so far as to set up a CVS for the website tho.
Thx for the, I'll look into it.
> 2. DreamWeaver's locking mechanism is handled by placing lock files
> on the server. Those files have the info about who has what. It
> ought to be possible to write an emacs extension that would use those
> files.
Certainly. But my original message mentioned the REAL source of my
frustration: I'm pretty limited at elisp, otherwise I might have already had
this worked out. :-)
L8r,
Rob
Re: [WOT] emacs and WEBDAV
Posted by Kee Hinckley <na...@somewhere.com>.
At 11:30 AM -0800 3/14/02, Rob Bloodgood wrote:
>The problem is, concurrency. Dreamweaver has versioning built in... but
>emacs has no way to recognize it. So when I make a fix to a file, if the
>designers aren't explicitly instructed to refresh-from-the-website-via-ftp,
>my changes get hosed.
Versioning, no. Locking, yes, optionally. (Well, I guess it can do
versioning via SourceSafe, but not via anything else.) I'm seriously
hoping they'll address that in the next release.
>I've been trying, in various attempts over the past two years, to come up
>with a compromise between the two. The closest I've come was somebody
>mentioned a CVS emulation layer over a DAV repository... but that never came
>to fruition. And even more frustrating, I haven't managed to pick up enough
>eLisp to do it myself w/ vc.el <sigh>.
>
>Does anybody have any ideas for my next direction to turn?
There are WebDAV extensions under development to provide versioning.
I suspect that eventually we'll see those supported. But that's got
to be a year or more down the road.
Emacs over WebDAV should work fine if you run something that supports
WebDAV as a filesystem (e.g. OSX), but that's not going to help you
much.
There are two options I can think of.
1. If your designers aren't making use of checkin/checkout in
DreamWeaver, then simply make it clear to them that before they can
save a file to the server, they have to do a sync first. Make the
final repository sit on CVS, and do a checkin every night. So if
something does go wrong you can at least pick up the previous day's
work.
2. DreamWeaver's locking mechanism is handled by placing lock files
on the server. Those files have the info about who has what. It
ought to be possible to write an emacs extension that would use those
files.
--
Kee Hinckley - Somewhere.Com, LLC
http://consulting.somewhere.com/
nazgul@somewhere.com
I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.
Re: [WOT] emacs and WEBDAV
Posted by darren chamberlain <dl...@users.sourceforge.net>.
Quoting Rob Bloodgood <ro...@empire2.com> [Mar 14, 2002 14:30]:
> I've been trying, in various attempts over the past two years,
> to come up with a compromise between the two. The closest I've
> come was somebody mentioned a CVS emulation layer over a DAV
> repository... but that never came to fruition. And even more
> frustrating, I haven't managed to pick up enough eLisp to do it
> myself w/ vc.el <sigh>.
>
> Does anybody have any ideas for my next direction to turn?
This <http://www.cvshome.org/cyclic/cvs/dev-dav.html> looks
promising...
(darren)
--
We can't all, and some of us don't. That's all there is to it.
-- Eeyore