From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Truncating lines in the article buffer
Date: Thu, 14 Oct 2010 12:00:19 -0500 [thread overview]
Message-ID: <87lj60vhek.fsf@lifelogs.com> (raw)
In-Reply-To: <m3tykoeo8s.fsf@quimbies.gnus.org>
On Thu, 14 Oct 2010 18:24:35 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Consider using SVG to render the tables. It's scalable (including the
>> fonts) so the image will look good at any resolution (if the pixel count
>> allows it). It's really easy to insert PNG and JPEG images too. See
>> this for some good examples:
LMI> You mean render the entire table as a picture? No, I don't want that.
LMI> Emacs is about text, and if you can't display the HTML as text, it's not
LMI> Emacs. (Kill/yank/click links, etc.)
LMI> Besides, Emacs totally, utterly sucks at displaying images, and tables
LMI> used for layout are usually big. As in, the entire page is inside
LMI> nested tables.
Then you can't render HTML accurately with the current approach. You're
fighting Emacs at every step: the text layout is hard, you can't flow
around images, displaying images is a pain, etc.
Maybe we're approaching this wrong because we think a table should be
displayed like HTML does. How about unwrapping tables into lists? So
this (a 2x2 table with headers H1 and H2):
H1 H2
[aaa|bbb]
[ccc|ddd]
gets rendered as
* H1
** aaa
** ccc
* H2
** bbb
** ddd
(I've skipped out the obvious nesting example since it's simply a nested
list.)
That gives you a lot more horizontal space and laying out the text even
in nested situations becomes trivial (you always have a full line for
the table cell). The image-text flow problem is eliminated.
We'll need a keybinding to flip columns/rows I think, but otherwise this
is a pretty good *view* of the table, even if it's not an accurate
*rendering*. More importantly, it provides something usable right now
and as the Emacs display engine gets improved it can be improved too.
Ted
next prev parent reply other threads:[~2010-10-14 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 21:17 Lars Magne Ingebrigtsen
2010-10-13 21:56 ` Kevin Ryde
2010-10-13 22:01 ` Lars Magne Ingebrigtsen
2010-10-14 15:09 ` Ted Zlatanov
2010-10-14 16:24 ` Lars Magne Ingebrigtsen
2010-10-14 17:00 ` Ted Zlatanov [this message]
2010-10-14 18:19 ` Lars Magne Ingebrigtsen
2010-10-14 18:39 ` Ted Zlatanov
2010-10-14 18:53 ` Lars Magne Ingebrigtsen
2010-10-14 20:04 ` Ted Zlatanov
2010-10-14 20:13 ` Lars Magne Ingebrigtsen
2010-10-14 20:32 ` Ted Zlatanov
2010-10-14 20:40 ` Frank Schmitt
2010-10-14 20:57 ` Ted Zlatanov
2010-10-14 21:15 ` Lars Magne Ingebrigtsen
2010-10-14 21:39 ` Knut Anders Hatlen
2010-10-15 14:18 ` Lars Magne Ingebrigtsen
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=87lj60vhek.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.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 NNTP newsgroup(s).