From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Breaking news: What did the IETF ever do for us? The *entire* list!
Date: Thu, 02 Apr 2015 04:31:31 +0200 [thread overview]
Message-ID: <87619f8dmk.fsf@debian.uxu> (raw)
The RFC memos and specifications - published by the
semi-mythical IETF - are available in the Debian
repositories as the non-free 'doc-rfc' metapackage.
After installation ('sudo aptitude install doc-rfc')
the files can be inspected in /usr/share/doc/RFC.
They are all in .gz format, but one can unzip them
with gunzip to get a neat 407M directory instead. Win!
This makes it easier to manipulate the files with
familiar and unfamiliar tools alike.
Now it gets interesting. I wrote this zsh function to
search the RFCs:
search-rfc () {
local search=$1
files=("${(@f)$(grep -i $search -l /usr/share/doc/RFC/*/**.txt)}")
for f in $files; do
local data=`grep -c -H -i $search $f`
local occs=${data##*:}
local filename=${data%:*}
echo $occs\\t$filename
done | sort -n -r
}
So now I can answer the question: What did the IETF
ever do for us? The first column is the number of hits
for the search string, in the document to the right:
"Emacs"
7 /usr/share/doc/RFC/for-your-information/rfc1580.txt
5 /usr/share/doc/RFC/informational/rfc2629.txt
5 /usr/share/doc/RFC/informational/rfc1056.txt
3 /usr/share/doc/RFC/queue/draft-ietf-lisp-22.txt
2 /usr/share/doc/RFC/proposed-standard/rfc6120.txt
2 /usr/share/doc/RFC/informational/rfc1554.txt
1 /usr/share/doc/RFC/unclassified/rfc1003.txt
1 /usr/share/doc/RFC/proposed-standard/rfc4833.txt
1 /usr/share/doc/RFC/proposed-standard/rfc1144.txt
1 /usr/share/doc/RFC/links/rfc1957.txt
1 /usr/share/doc/RFC/informational/rfc2223.txt
1 /usr/share/doc/RFC/informational/rfc1957.txt
1 /usr/share/doc/RFC/informational/rfc1842.txt
1 /usr/share/doc/RFC/informational/rfc1599.txt
1 /usr/share/doc/RFC/historic/rfc1422.txt
1 /usr/share/doc/RFC/historic/rfc1203.txt
1 /usr/share/doc/RFC/for-your-information/rfc1689.txt
"Elisp":
5 /usr/share/doc/RFC/proposed-standard/rfc4444.txt
1 /usr/share/doc/RFC/for-your-information/rfc1580.txt
... ...
"Gnus":
8 /usr/share/doc/RFC/informational/rfc2808.txt
6 /usr/share/doc/RFC/proposed-standard/rfc4867.txt
6 /usr/share/doc/RFC/informational/rfc6064.txt
4 /usr/share/doc/RFC/proposed-standard/rfc3611.txt
3 /usr/share/doc/RFC/proposed-standard/rfc5993.txt
3 /usr/share/doc/RFC/proposed-standard/rfc5404.txt
3 /usr/share/doc/RFC/proposed-standard/rfc4352.txt
3 /usr/share/doc/RFC/proposed-standard/rfc3767.txt
3 /usr/share/doc/RFC/proposed-standard/rfc2228.txt
3 /usr/share/doc/RFC/informational/rfc4613.txt
... ...
Dig, diggers!
--
underground experts united
http://user.it.uu.se/~embe8573
next reply other threads:[~2015-04-02 2:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 2:31 Emanuel Berg [this message]
2015-04-02 2:59 ` Breaking news: What did the IETF ever do for us? The *entire* list! Alexis
2015-04-02 7:11 ` tomas
2015-04-02 7:35 ` Alexis
2015-04-02 7:51 ` tomas
2015-04-02 3:27 ` Pascal J. Bourguignon
2015-04-02 22:56 ` Emanuel Berg
2015-04-03 1:42 ` Emanuel Berg
2015-04-03 1:33 ` Pascal J. Bourguignon
2015-04-04 1:30 ` Emanuel Berg
[not found] ` <mailman.3167.1427943592.31049.help-gnu-emacs@gnu.org>
2015-04-02 14:40 ` Udyant Wig
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=87619f8dmk.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
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).