Skip to main content

centos6 gitweb color syntax highlighting

Install highlight

You have to enable rpmforge and epel then:

 sudo yum install source-highlight highlight 

Configure GitWeb feature

In /etc/gitweb.conf, append:

 $feature{'highlight'}{'default'} = [1]; 


  1. Hi,

    What version of git you have? I have 1.7.1 and after installing both source-highlight and highlight and enabling '$feature{'highlight'}{'default'} = [1];' in gitweb.conf, I still don't get highlighting enabled in CentOS6.


  2. Hi,

    I too have CentOS 6.4 installed and my version of git is also 1.7.1 and I don't get it to work.


  3. Despite being the latest release CentOS 6.4 does rely on an older Git release (1.7.1 instead of 1.8.4). Apparently the included Gitweb doesn't support the highlighting feature and therefore will simply ignore it.

    You can work around this issue by replacing the old gitweb.cgi with a newer one (built from gitweb.perl) from the official Github-Repo.


Post a Comment

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

dockerfile multiline to file

Outputing a multiline string from Dockerfile I motsly use a Dockerfile by sourcing from a base ditribution: CentOS or Debian. But I also have a local mirror and would like to use it for packages installation. Espacially on CentOS it is about many lines to write to the /etc/yum.repos.d/CentOS-Base.repo file. Easiest way: one RUN per line The first method that comes in mind is to issue one RUN per line to write. Here you are: RUN echo "[base] " > /etc/yum.repos.d/CentOS-Base.repo RUN echo "name=CentOS-$releasever - Base " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "baseurl= " >> /etc/yum.repos.d/CentOS-Base.repo RUN echo "gpgcheck=0 &quo

Jira workflow for new projects

Associated workflow creation I'm a Jira Cloud user and begining from some version 6, I noticed that when I create a project, it automatically creates a Workflow and Issue Scheme that is prepended by the project key and which is a copy of the default scheme. I always had to make a cleanup after creating a project. Default workflow for new projects I also miss a feature that would allow me to make a custom workflow (and globally custom project setting) the default for new projects I create. Solution: Create with shared configuration While searching, I noticed that with Jira Cloud which is version 7.1.0 at the time I write, there is a link at the bottom of the "Create project" wizard: "Create with shared configuration" will allow me to select the project I want the new one to share configuration with. The new created project will use the same configuration as the project I select There will be no creation of Workflow and Issue Scheme that