Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: 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)
Date: Mon, 06 Dec 2010 18:32:16 +0100	[thread overview]
Message-ID: <m3aakivmcf.fsf_-_@quimbies.gnus.org> (raw)
In-Reply-To: <m3wrnmu9hj.fsf@quimbies.gnus.org>

Which reminds me: Do we want to colourise the newlines or don't we?

It can be somewhat awkward either way.  If we do, them background
colours extend to the end of the frame.  If we don't, then the
text with the background colour looks ragged.

Both look, er, non-optimal, but I think I may prefer the text to extend
to the right, now that I've used it for several minutes...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2010-12-06 17:32 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                   ` Lars Magne Ingebrigtsen [this message]
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
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=m3aakivmcf.fsf_-_@quimbies.gnus.org \
    --to=larsi@gnus.org \
    --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).