From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] mkindex of dict(7)
Date: Mon, 5 Jan 2009 09:13:21 -0500 [thread overview]
Message-ID: <fa65e4a923dd7e008ba6456be5f2a33f@quanstro.net> (raw)
In-Reply-To: <b53ffa62b680cb7b2a65caa1cb9c4305@sounine.nanosouffle.net>
> /sys/src/cmd/dict/dict.c states:
> /*
> * Assumed index file structure: lines of form
> * [^\t]+\t[0-9]+
> * First field is key, second is byte offset into dictionary.
> * Should be sorted with args -u -t' ' +0f -1 +0 -1 +1n -2
> */
>
> whereas, /sys/src/cmd/dict/mkindex outputs:
> <byte offset> <key>
> i.e.,
> 0 ヽ [くりかえし]
>
> Perhaps, before I dive into thinking I'm fixing things,
> someone would be kind enough to look into the above?
> ak
clearly there was some post processing.
why do you need to regenerate the index?
- erik
next prev parent reply other threads:[~2009-01-05 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 6:08 Akshat Kumar
2009-01-05 7:15 ` Akshat Kumar
2009-01-05 14:13 ` erik quanstrom [this message]
2009-01-05 14:41 ` erik quanstrom
2009-01-06 5:34 ` Akshat Kumar
2009-01-06 12:41 ` Fazlul Shahriar
2009-01-06 12:50 ` Akshat Kumar
2009-01-05 7:27 Akshat Kumar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa65e4a923dd7e008ba6456be5f2a33f@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).