From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Truncating lines in the article buffer
Date: Thu, 14 Oct 2010 15:04:36 -0500 [thread overview]
Message-ID: <87lj60tuaz.fsf@lifelogs.com> (raw)
In-Reply-To: <m38w207gis.fsf@quimbies.gnus.org>
On Thu, 14 Oct 2010 20:53:15 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Why not walk through the buffer and apply the equivalent of
>> truncate-lines to every line? You could set some text property to
>> indicate it's needed.
LMI> truncate-lines doesn't truncate lines. :-) It only stops them from
LMI> being wrapped. You can scroll to the right to see the end of the
LMI> lines.
Ah, well that makes sense. Sorry for being dense.
>> You could display the image as an icon (the size of a character) and the
>> user can toggle it to full size with RET or mouse-1.
LMI> Images are currently displayed in tables as [img], and you can `I' them
LMI> to insert them.
I would show them as a tiny icon the size of a character. It should at
least be an option (and in fact would be great for NSFW images, since it
would offer a tiny preview). Then `I' can just toggle between the
scaled and full-size versions of the same image.
Ted
next prev parent reply other threads:[~2010-10-14 20:04 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
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 [this message]
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=87lj60tuaz.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).