Well, what DO they use? They use ange-ftp addresses
for FTP (like info.cern.ch:/pub/www/doc/*.ps),
[82] ange-ftp というのは Emacs で動作する FTP ソフトウェアがあるらしい。それのこと? このよくある書式の発祥はそのソフトだったのだろうか?
[7] null, , https://dept-info.labri.fr/~strandh/Teaching/PFS/Common/Code-examples/emacs-20.4/lisp/browse-url.el
"An alist of (REGEXP . STRING) pairs used by `browse-url-of-file'. Any substring of a filename matching one of the REGEXPs is replaced by the corresponding STRING using `replace-match', not treating STRING literally. All pairs are applied in the order given. The default value converts ange-ftp/EFS-style paths into ftp URLs and prepends `file:' to any path beginning with `/'. For example, adding to the default a specific translation of an ange-ftp address to an HTTP URL:
[231] Protect your Software from the Zero Day Wget Vulnerability, drewt, , https://jfrog.com/blog/cve-2024-10524-wget-zero-day-vulnerability/
[232] >>231 wget の入力で URL か URL の scheme + :
の省略か伝統的な FTP の表記法が指定できたため、
: を含む userinfo が指定されたとき FTP の表記法と誤認させられる脆弱性があると判断された事案。
ffap is a powerful package which extends the find-file command (the one which prompts for a file name in the minibuffer, normally bound to C-x C-f). It searches the text around the cursor position for something which might represent a filename -- a file in the current directory, a C #included file, a newsgroup reference, an ange-ftp style reference to a file on a remote machine or an URL -- and prompts you either to open that file, or to send the URL to a browser (via browse-url). Once experiencing this you quickly get sick of typing filenames into the minibuffer, and may find yourself inserting ``hyperlinks in strategic places in your files to save typing. ffap is distributed with both Emacs and XEmacs; I bind it to the F3 key as follows :
Make an ange-ftp style fullname out of HOST, USER (optional), and NAME.
My impression is that the main reason you chose the [...] syntax for
tramp is to avoid conflicts with ange-ftp; it seems cleaner and more
user-friendly to just use the same syntax for both, especially since
ange-ftp's syntax is basically a subset of tramp's, and now you have
the freedom to integrate them.
I think most people would agree that the ange-ftp-style syntax is a bit
nicer anyway (and familiar to more people), especially when most of the
details are defaulted based on the machine name or whatever.
Has anybody given any thought to a syntax with implied schemes so that
the ange-ftp style URLs and internet message ID URNs that are out
there can be used?<p>
If we reserved a character to _start_ UDIs, then we could try to infer
the scheme of strings that don't start with that char. Let's take
() for URL schemes and [] for URN schemes.
<XMP>
For example: host:path == (ANON-FTP)host:path
path@host == (ANON-FTP)host:path
<message-id@host> == [rfc-822]<message-id@host>
</XMP>
Well, I suppose this type of thing is really akin to the W3 local
UDI scheme: it's application specific.<p>