List for cgit developers and users
 help / color / mirror / Atom feed
From: stefan at sevenbyte.org (Stefan Tatschner)
Subject: Fwd: Re: RESEND: syntax-highlighting.py
Date: Wed, 08 Jan 2014 17:22:08 +0100	[thread overview]
Message-ID: <52CD7B30.3010208@sevenbyte.org> (raw)
In-Reply-To: <52CD7ADF.2080903@sevenbyte.org>

Am 08.01.2014 16:19, schrieb Jason A. Donenfeld:
> Okay reading this closer, it seems what the one in-tree could benefit from is:
> 
> - Expanded list of filename mappings, made more generic than what you
> have in your script, but basically the same idea. -- { "pkgbuild":
> "bashlexer", "cmakelists.txt", "cmakelexer" }. Is there a way to do
> this that ties directly into pygment's guess_lexer_for_filename? If
> not, could you submit a patch upstream?

I have looked in pygment's sourcecode and found this [0]. I just have to
add the filenames in the lexer definitions. I will try to create an
upstream pull request. The only problem is that the latest release of
pygments is almost 1 year old. It think it will take a while until the
changes get merged...

As a workaround we could create such a dict as you suggested and check
if the filenames match.

> - We should make use of guess_lexer as you do, but perhaps not only if
> the shebang is present

At first I run guess_lexer_for_filename (line 26). It checks the content
of the file and also looks at the filename. After that I check if there
is a shebang because the script has already looked at the content with
guess_lexer_for_filename. I have tested this without the shebang
detection and especially with plaintext files it often returns crap...

> Would love for a patch against the in-tree version that gets it up to
> date like this.

:-)
It will take a few days because currently I have exams... Should I work
on the master branch or something else?

What do you want to de with the CSS definitions? Just put them into the
default cgit CSS file or maybe include it seperately?

Stefan

Links:
[0]:
https://bitbucket.org/birkenfeld/pygments-main/src/9246d7a47a42e7920c0ecee4d4946b982e9e2430/pygments/lexers/_mapping.py?at=default





-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20140108/d242b74e/attachment.asc>


       reply	other threads:[~2014-01-08 16:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <52CD7ADF.2080903@sevenbyte.org>
2014-01-08 16:22 ` stefan [this message]
2014-01-08 16:28   ` Jason
2014-01-09 19:52     ` stefan

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=52CD7B30.3010208@sevenbyte.org \
    --to=cgit@lists.zx2c4.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).