user/dev discussion of public-inbox itself
 help / color / Atom feed
From: SZEDER Gábor <>
Subject: syntax highlighting bug with lines containing '>'
Date: Mon, 4 Feb 2019 11:54:54 +0100
Message-ID: <> (raw)


First of all, thanks you very much for adding syntax highlighting for
patch emails, it's fantastic!

However, I noticed that a patch I recently sent to the Git mailing
list got bogus syntax highlighting, as the added line is colored as

Perhaps the '>' shell redirection operator causes troubles?  I clicked
around in the list archives, and sure enough found other occurrance of
this bug, that also seems to suggest that a '>' might be problematic
only when it's on the first added line:

Dunno, I have no idea how any of this works, so I stop spinning
theories about what could possibly be the cause.


             reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 10:54 SZEDER Gábor [this message]
2019-02-04 11:49 ` [PATCH] viewdiff: group path match to not be confused by "/dev/null" Eric Wong

Reply instructions:

You may reply publically 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone public-inbox