reassign 463777 dict-jargon 4.4.4-6.1
thanks
Aleksey Cheusov writes:
Hi,
Okay, so I suppose my initial instinct was correct and it's probably
the dict-jargon file itself that has the bogus linebreaks after all.
Yes. The problem comes from dict-jargon package.
I'm reassigning the bug to the
On Wed, Feb 06, 2008, Robert Luberda wrote:
Yes, I've noted this. I'm wondering why Mohammed had orphaned only 3 his
packages instead of all of them.
Probably by mistake :-)
--
Mohammed Adnène Trojette
Quoth Aleksey Cheusov [EMAIL PROTECTED], on 2008-02-05 12:40:32 +0200:
First, show your FULL command. Lines are wrapped in dictionary file.
What dictionary you use? What server? Show your FULL command! ;)
I thought I mentioned that. I may have forgotten, since I was
originally going to report
This is accessing dict-jargon through a local dictd.
ii dict-jargon4.4.4-6.1 Jargon File 4.4.4
ii dictd 1.10.10.dfsg-1 Dictionary Server
The full command is just:
$ dict foo
Show the result of the following command
Quoth Aleksey Cheusov [EMAIL PROTECTED], on 2008-02-05 14:48:02 +0200:
Show the result of the following command
zcat /usr/share/dictd/jargon.dict.dz | grep -C10 'Army slang acronym'
Ah, they're sufficiently plain-text for that to work? Using -C2
instead:
When `foo' is used in connection
Show the result of the following command
zcat /usr/share/dictd/jargon.dict.dz | grep -C10 'Army slang acronym'
Ah, they're sufficiently plain-text for that to work?
Both .index and .dict are plain text by design. .dict.dz - compressed
using dictzip format - modification of gzip format,
Package: dict
Version: 1.10.10.dfsg-1
Severity: normal
An excerpt from the output of [dict foo]:
When `foo' is used in connection with `bar' it has generally traced
to
the WWII-era Army slang acronym {FUBAR} (`Fucked Up Beyond All
Repair'
or `Fucked Up Beyond All
7 matches
Mail list logo
