From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-devel@gnu.org
Subject: Re: file://host/location URLs
Date: Mon, 19 Nov 2012 18:16:06 +0100 [thread overview]
Message-ID: <87obit5x9l.fsf@Rainer.invalid> (raw)
In-Reply-To: 87haom6yef.fsf@uwakimon.sk.tsukuba.ac.jp
Stephen J. Turnbull writes:
> I disagree. To me, it's the obvious RFC-standardized way to write an
> ssh/scp/sftp URL[1] for fetching a file from a specific host, where
> the user of the URL is expected to be able to access the same file
> system on that host as the writer, but without constraining the user
> to a possibly inconvenient transport protocol.
Yes, and that is what I use them for: if I need to point to a file that
resides on a specific host that I may or may not have direct access to
depending on where I am, then specifying that resource as a non-local
file URI is mightily convenient. If it resolves to localhost then it
should be a normal file access, if the target file system is already
mounted or reachable via a network file system, then I'd like to use
that access path and if all else fails, then try scp, ssh or ftp or even
avian carrier (see RFC1149/2549).
If there's anything to fix in Emacs then it is its insistence to only
try FTP for those (if I always wanted to use FTP then I'd use an FTP
URI). If it warned users about obviously malformed URIs and offered
sensible corrections that would also be nice.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2012-11-19 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 23:43 file://host/location URLs Daniel Colascione
2012-11-16 14:18 ` Stefan Monnier
2012-11-17 0:58 ` James Cloos
2012-11-17 3:00 ` Daniel Colascione
2012-11-17 8:25 ` Achim Gratz
2012-11-17 20:16 ` James Cloos
2012-11-18 8:12 ` Chong Yidong
2012-11-18 15:31 ` Daniel Colascione
2012-11-19 3:54 ` Stephen J. Turnbull
2012-11-19 17:16 ` Achim Gratz [this message]
2012-11-20 12:54 ` Jason Rumney
2012-11-20 20:07 ` Daniel Colascione
2012-11-20 20:52 ` Achim Gratz
2012-11-21 6:33 ` joakim
2012-11-21 8:29 ` Andreas Schwab
2012-11-22 8:50 ` joakim
2012-11-18 15:27 ` Stephen J. Turnbull
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87obit5x9l.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).