git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] gitweb: blame: Print just a single new line char per table row
Date: Wed, 4 Oct 2006 23:48:17 -0700 (PDT)	[thread overview]
Message-ID: <20061005064817.21552.qmail@web31804.mail.mud.yahoo.com> (raw)
In-Reply-To: <7vejtnij5n.fsf@assigned-by-dhcp.cox.net>

--- Junio C Hamano <junkio@cox.net> wrote:
> I have to say the browser is seriously broken if whitespaces
> between <tr> and <td>, </td> and next <td>, </td> and </tr>
> makes a difference to its behaviour.  Aren't there a way to tell
> the browser to cut "visually"?  E.g. "The area I want to cut is

I'm not sure, I'm using latest Firefox.

> from this data column, and lines from here to there.  I do not
> want the leftmost two columns (commit-8 and lineno)".
> 
> I do not mind applying this, but that is only because it does
> not make its source any less readable.  It does make things
> harder to debug if somebody is debugging its output by reading
> the generated raw HTML, so it is not like there is no downside.

If you think that this could be a problem or affects negatively,
please don't apply.  cut-paste-edit is a small price to pay
as opposed to messing up the code and output.

> You might want to run links (or lynx) in screen ;-).  Screen
> supports left- (or right-, or both-sides) bounded cut which I
> find extremely useful.

Ok, I'll try that.

    Luben

  reply	other threads:[~2006-10-05  6:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05  0:59 [PATCH 1/2] gitweb: blame: Print just a single new line char per table row Luben Tuikov
2006-10-05  2:35 ` Junio C Hamano
2006-10-05  6:48   ` Luben Tuikov [this message]
2006-10-05  8:13     ` perhaps time to remove git_blame from gitweb, and git-annotate? Junio C Hamano
2006-10-06 13:07       ` Johannes Schindelin
2006-10-06 17:52         ` Luben Tuikov
2006-10-07  5:37           ` Martin Langhoff (CatalystIT)
2006-10-06 16:16       ` Petr Baudis
2006-10-06 18:55         ` Luben Tuikov
2006-10-06 19:08           ` Petr Baudis
2006-10-06 20:21             ` Luben Tuikov
2006-10-09 10:32       ` [PATCH 1/1] Remove git-annotate.perl and create a builtin-alias for git-blame Ryan Anderson
2006-10-09 10:37       ` perhaps time to remove git_blame from gitweb, and git-annotate? Ryan Anderson
2006-10-09 22:33         ` Obituary for git-annotate Junio C Hamano

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=20061005064817.21552.qmail@web31804.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).