From: Simon Josefsson <jas@extundo.com>
Subject: Re: Face (X-Face?)
Date: Mon, 13 Jan 2003 16:59:52 +0100 [thread overview]
Message-ID: <ilu8yxpjb0n.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m31y3hmf9c.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Michael Livshin <usenet@cmm.kakpryg.net> writes:
>
>> I'd like to ask Gnus to render those pictures on the right, so that
>> articles would look like so:
>>
>> +-------------------------------------------------------+
>> | <header...................> |
>> | <header...................> <X-face>|
>> | <header...................> |
>> | ------------------------------------------------------|
>> | <body..........................................> |
>> +-------------------------------------------------------+
>
> Unless the X/Emacs rendering system has changed lately, that's
> actually very difficult to do. I think the only way to do that is to
> insert one space at a time and query Emacs how many pixels we now
> have left. When you're far enough to the right, you insert the face.
Using the space-width it becomes a little easier (insert one space
with the space-width property and then the face, then increase the
space-width length until it can't be increased further without
wrapping the line), but I think it is impossible to get the above
because an image cannot occupy several lines as far as I know.
So it is only possible to get the following:
+-------------------------------------------------------+
| <header...................> <X-face>|
| <X-face>|
| <X-face>|
| <header...................> |
| <header...................> |
| ------------------------------------------------------|
| <body..........................................> |
+-------------------------------------------------------+
Another idea is to make use of multiple emacs buffers for this, i.e.:
+---------------------------------------------+--------+
| <header...................> |<X-face>|
| <header...................> |<X-face>|
| <header...................> |<X-face>|
| <header...................> | |
+---------------------------------------------+--------+
| <body.........................................> |
+------------------------------------------------------+
If the status bar and scrollbars can be disabled or minimized (which I
believe is the case), I think this could work rather well.
Presumably, the easiest way to implement it would be to simply disable
viewing headers in the current *Article* buffer and then add the two
other buffers with the headers and X-face, like the tree buffer is
added now. I'm not sure if it is worth the trouble.
prev parent reply other threads:[~2003-01-13 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vg0ub22b.fsf@at_ipipan.waw.pl>
2003-01-12 19:55 ` Vasily Korytov
[not found] ` <m3adi6174o.fsf@quimbies.gnus.org>
[not found] ` <87bs2ld7t9.fsf@labatt.uhoreg.ca>
[not found] ` <m3of6lmq9a.fsf@quimbies.gnus.org>
[not found] ` <878yxppdow.fsf@orebokech.com>
[not found] ` <m33cnxmk40.fsf@quimbies.gnus.org>
[not found] ` <m3znq5l53z.fsf@quimbies.gnus.org>
[not found] ` <s33cnx8du4.fsf@laredo.verisity.com.cmm>
2003-01-13 12:21 ` Karl Kleinpaste
[not found] ` <87smvwwv9i.fsf@labatt.uhoreg.ca>
2003-01-13 22:28 ` Jesper Harder
[not found] ` <m31y3hmf9c.fsf@quimbies.gnus.org>
2003-01-13 15:59 ` Simon Josefsson [this message]
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=ilu8yxpjb0n.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).