From: Junio C Hamano <gitster@pobox.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Jean-Baptiste Quenot <jbq@caraldi.com>
Subject: Re: [PATCH] gitweb: Better chopping in commit search results
Date: Sat, 23 Feb 2008 14:04:05 -0800 [thread overview]
Message-ID: <7vd4qn1ga2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 200802222014.13205.jnareb@gmail.com
Jakub Narebski <jnareb@gmail.com> writes:
> # regexps: ending and beginning with word part up to $add_len
> my $endre = qr/.{0,$len}[^ \/\-_:\.@]{0,$add_len}/;
> my $begre = qr/[^ \/\-_:\.@]{0,$add_len}.{0,$len}/;
I have no idea what these line noise characters inside [] are.
Did you mean something like "\w"?
I have a suspicion that it may be easier to read and could be
even more efficient to split an overlong line at word boundaries
and to remove elements from the end you are removing from until
it fits.
sub chop_whence {
my ($line, $max, $slop, $where) = @_;
my $len = length($line);
if ($len < $max + $slop) {
return $line;
}
# Cut at word boundaries
my @split = split(/\b/, $line);
my $filler = "...";
while ((2 < @split)) {
my $removed;
my $splice_at;
if ($where eq 'left') {
$removed = shift @split;
} elsif ($where eq 'right') {
$removed = pop @split;
} else {
my $splice_at = int($#split / 2);
$removed = splice(@split, $splice_at, 1);
}
$len -= length($removed) + length($filler);
if ($len < $max + $slop) {
if ($where eq 'left') {
unshift @split, $filler;
} elsif ($where eq 'right') {
push @split, $filler;
} else {
my $splice_at = int($#split / 2);
splice(@split, $splice_at, 0, $filler);
}
return join('', @split);
}
}
# give up
return $line;
}
next prev parent reply other threads:[~2008-02-23 22:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 17:37 [PATCH] Do not chop HTML tags in commit search result Jean-Baptiste Quenot
2008-02-13 19:16 ` Jakub Narebski
2008-02-13 19:43 ` Junio C Hamano
2008-02-22 16:33 ` [PATCH] gitweb: Better chopping in commit search results Jakub Narebski
2008-02-22 17:14 ` Junio C Hamano
2008-02-22 17:49 ` Jakub Narebski
2008-02-22 19:14 ` Jakub Narebski
2008-02-23 21:44 ` [RFC/PATCH] gitweb: Option to chop at beginning and in the middle in chop_str Jakub Narebski
2008-02-23 22:04 ` Junio C Hamano [this message]
2008-02-23 23:36 ` [PATCH] gitweb: Better chopping in commit search results Jakub Narebski
2008-02-24 13:01 ` [RFC/PATCH v2] gitweb: Option to chop at beginning and in the middle in chop_str Jakub Narebski
2008-02-25 1:46 ` Junio C Hamano
2008-02-25 20:07 ` [RFC/PATCH v3] gitweb: Better cutting matched string and its context Jakub Narebski
2008-02-25 20:18 ` Junio C Hamano
2008-02-23 9:27 ` [PATCH] gitweb: Better chopping in commit search results Karl Hasselström
2008-02-23 10:20 ` Jakub Narebski
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=7vd4qn1ga2.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jbq@caraldi.com \
--cc=jnareb@gmail.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).