Nelson Minar writes:
I really think it'd be good if emacs standardized on using URLs
to
specify things to load that are outside the filesystem. URLs are a
nice, standard syntax for specifying a method and a location: it
solves exactly the problem we are discussing here.
It's a problem that // means something special in emacs: could
you
maybe special case "://" to mean something different to handle URLs?
(// isn't common to all URLs, btw, although it's typical for many of
the ones that name things that look like files).
Actually, given WHAT // means, I'd just as soon pull it out -- it's
not much faster to type // as ^a^k (which does the same thing,
mostly), and normal // parsing can be done on the protocol side,
rather than the editing side; long filenames that are really much
shorter filenames shouldn't be a problem, yes?
Not to mention that I've been bit by // more often than I've
benifited from it -- as presently implemented, it's a single-keystroke
operation that can, in an instant, wipe out the last minute of hunting
around on the filesystem (even if it IS undoable). There's little
reason to have it resolve electrically, and several reasons not to.
--
Joshua Kronengold (mneme(a)mcny.com) |\ _,,,--,,_ ,)
---^---- Application Developer, Winstar Media Connection /,`.-'`' -,
;-;;'
/\\ "What part of 'Pthhhrrrrrrrrrrrrrrrrrr' |,4- ) )-,_ ) /\
-/-\\\-- didn't you understand?" '---''(_/--' (_/-'
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1.2
GCS d- a- C+++$ U+++$(++++) P+++$ L++$ E+ W++$ N++ K++ w-- !O
!M V-- PS+++ PE Y+ PGP !t 5++ !X R++@ !tv b++++ DI++++ D- G
e+@ h! r++ y+* s:
------END GEEK CODE BLOCK------