git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Hagander <magnus@hagander.net>
To: git@vger.kernel.org
Cc: Magnus Hagander <magnus@hagander.net>
Subject: [PATCH] Allow gitweb tab width to be set per project.
Date: Tue, 28 Sep 2010 13:35:09 +0200	[thread overview]
Message-ID: <1285673709-24924-1-git-send-email-magnus@hagander.net> (raw)

Allow the gitweb.tabwidth option to control how many spaces a tab
gets expanded to.

Signed-off-by: Magnus Hagander <magnus@hagander.net>
---

In the PostgreSQL project, we're using 4-space tabs, but we have other projects
as well on our gitweb server, so we need to be able to control this on a
per-project basis.


 gitweb/gitweb.perl |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index a85e2f6..ef92a4f 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -1465,9 +1465,11 @@ sub unquote {
 # escape tabs (convert tabs to spaces)
 sub untabify {
 	my $line = shift;
+	my $tabwidth = git_get_project_config('tabwidth', '--int');
+	$tabwidth = 8 if ($tabwidth <= 0);
 
 	while ((my $pos = index($line, "\t")) != -1) {
-		if (my $count = (8 - ($pos % 8))) {
+		if (my $count = ($tabwidth - ($pos % $tabwidth))) {
 			my $spaces = ' ' x $count;
 			$line =~ s/\t/$spaces/;
 		}
-- 
1.7.0.4

             reply	other threads:[~2010-09-28 11:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28 11:35 Magnus Hagander [this message]
2010-09-28 12:25 ` [PATCH] Allow gitweb tab width to be set per project Jakub Narebski
2010-09-29  8:39   ` Magnus Hagander
2010-09-29  9:22     ` Jakub Narebski
2010-10-01 11:56       ` Magnus Hagander
2010-10-01 21:02         ` Jakub Narebski
2010-10-18 10:31           ` Magnus Hagander
2010-10-18 10:41             ` Magnus Hagander

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=1285673709-24924-1-git-send-email-magnus@hagander.net \
    --to=magnus@hagander.net \
    --cc=git@vger.kernel.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).