Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: colourising newlines
Date: Thu, 16 Dec 2010 20:25:15 +0000	[thread overview]
Message-ID: <878vzpifgw.fsf@ucl.ac.uk> (raw)
In-Reply-To: <m3fwtyk9lz.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> Does it?  Maybe you can font-lock it to take N spaces but actually be
>> zero.
>
> I don't think that's possible with Emacs' display engine, but I'd love
> to be wrong on that point.
>
>> I don't know, honestly, but dammit I know what looks good and ragged
>> backgrounds are not it :)
>
> No, it looks quite awkward at present.  Perhaps colourising the newline
> (i.e., extending the colour block up to the right frame end) is the best
> of two not very good options.

What about using an overlay (with appropriate face) instead of
font-locking, as is done by hl-line mode (cf. hl-line.el in emacs 23.2
at least).  This mode overlays a background from the left edge of the
window to the right edge regardless of the number of characters on the
line (i.e. no space padding required) and the code in hl-line-move looks
like it could easily be extended to cover a number of lines instead of
just a single line?

Just a thought from an elisp novice...  so feel free to ignore me (as
many do ;-).

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 23.2.1 + No Gnus v0.11



  parent reply	other threads:[~2010-12-16 20:25 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1PPcjn-0002Xs-00@quimby.gnus.org>
2010-12-06 15:24 ` [gnus git] branch master updated: =2= shr: colorize only in one place ; shr: shr-colorize-region fix and stylesheet color retrieval fix Lars Magne Ingebrigtsen
2010-12-06 15:26   ` Lars Magne Ingebrigtsen
2010-12-06 15:54   ` Julien Danjou
2010-12-06 16:00     ` Lars Magne Ingebrigtsen
2010-12-06 16:03       ` Lars Magne Ingebrigtsen
2010-12-06 16:18         ` Julien Danjou
2010-12-06 16:25           ` Lars Magne Ingebrigtsen
2010-12-06 16:36             ` Julien Danjou
2010-12-06 16:41               ` Lars Magne Ingebrigtsen
2010-12-06 16:55                 ` Lars Magne Ingebrigtsen
2010-12-06 17:32                   ` colourising newlines (was: [gnus git] branch master updated: =2= shr: colorize only in one place ; shr: shr-colorize-region fix and stylesheet color retrieval fix) Lars Magne Ingebrigtsen
2010-12-14 23:51                     ` colourising newlines Ted Zlatanov
2010-12-15 19:30                       ` Lars Magne Ingebrigtsen
2010-12-15 21:03                         ` Ted Zlatanov
2010-12-15 21:30                           ` Lars Magne Ingebrigtsen
2010-12-15 21:40                             ` Ted Zlatanov
2010-12-16 15:54                               ` Lars Magne Ingebrigtsen
2010-12-16 20:43                                 ` Ted Zlatanov
2010-12-16 20:25                             ` Eric S Fraga [this message]
2010-12-17 16:43                               ` Lars Magne Ingebrigtsen
2010-12-18 19:20                                 ` Eric S Fraga
2011-01-19 22:24                             ` Ted Zlatanov
2011-01-22  3:02                               ` Lars Ingebrigtsen
2011-01-24 19:46                                 ` Ted Zlatanov
2010-12-06 16:17       ` [gnus git] branch master updated: =2= shr: colorize only in one place ; shr: shr-colorize-region fix and stylesheet color retrieval fix Julien Danjou
2010-12-06 16:22         ` Lars Magne Ingebrigtsen
2010-12-06 16:27           ` Lars Magne Ingebrigtsen
2010-12-06 16:48             ` Julien Danjou
2010-12-06 17:26               ` Lars Magne Ingebrigtsen
2010-12-06 17:30                 ` Julien Danjou
2010-12-06 17:33                   ` Lars Magne Ingebrigtsen
2010-12-06 16:33           ` Julien Danjou
2010-12-06 16:36             ` 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=878vzpifgw.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).