Re: [9fans] acme multi-line tags (or maybe, efficient message stores)

[Paul Lalonde <paul.a.lalonde@gmail.com>]

Not as far as I know.  The grief comes with mixed fonts in the same column.  As the tag grows it breaks the column layout height.  You wind up with the choice of pushing the windows below around (ugly and unusable) or winding up with fractional lines in each window whose font is not the tag font.  The layout logic doesn't handle that gracefully as it only counts text lines, not pixel heights, and I didn't have the time to make that change.
That said, I find acme (and Edit in particular) damned near unusable without multi-line tags now.
Paul

Sent from my iPad

On 2011-10-09, at 12:48, "Lyndon Nerenberg (VE6BBM/VE7TFX)"  <lyndon@orthanc.ca> wrote:

> After the previous round of arguments about (native plan9) acme multi-line
> window tags, did anyone ever come up with a patch that at least some
> people were happy with?
> 
> --lyndon
> 
> P.S.  Is there any point to keeping mailing list archives any more?
> With every messsage including the history of every discussion before
> it, the concept of search is rendered obsolete.
> 
> P.P.S.  Of course, nobody gives a fsck about history any more.
> 
> P.P.P.S.  [P.S.] introduces an interesting idea.  Instead of storing
> message text in a file, place each line of text into venti as a block,
> then store the message as a list of venti hashes pointing to the
> per-line content.  With all the duplicate included text, this should
> be good for a 90% reduction in venti block storage for most mail
> servers.  The 'included line' prefixes would have to be stored
> seperately for this to work.
> 
> --lyndon
> 
>