From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: "Roger C. Soares" <rogersoares@intelinet.com.br>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: faster egit history page and a pure java "gitk"
Date: Tue, 25 Mar 2008 19:48:48 +0000 [thread overview]
Message-ID: <200803252048.48531.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <47E90246.3030509@intelinet.com.br>
Den Tuesday 25 March 2008 14.46.46 skrev Roger C. Soares:
> I understand that you guys use a lot of ASCII art and wrapping can mess
> this. But here we track more things in bugzilla and there's some
> copy&pasting going on, so wrapping makes comments more readable.
> Currently it's a toogle preference in the local toolbar menu (like the
> CVS plugin).
It seems to me ASCII art should be auto-detectable... Maybe enough to
make the wrap flag unneeded in most cases. (wrap/nowrap/auto). At first
I was thinking about looking for special chars, but then it may be simpler
and just as useful to look for comment lines start with spaces ane a few
special characters.
Try this command: git log | sed 's/^ [\t |\\\/>]/| /' | less. It seems
to detect lines that I do not want wrapped pretty well.
-- robin
next prev parent reply other threads:[~2008-03-25 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 9:27 faster egit history page and a pure java "gitk" Shawn O. Pearce
2008-03-24 13:33 ` Roger C. Soares
2008-03-24 14:10 ` Robin Rosenberg
2008-03-25 4:43 ` Shawn O. Pearce
2008-03-25 12:33 ` Roger C. Soares
2008-03-24 14:06 ` Robin Rosenberg
2008-03-25 5:10 ` Shawn O. Pearce
2008-03-24 14:31 ` faster egit history page and a pure java "gitk" so Robin Rosenberg
2008-03-25 4:48 ` Shawn O. Pearce
2008-03-25 5:07 ` faster egit history page and a pure java "gitk" Roger C. Soares
2008-03-25 5:36 ` Shawn O. Pearce
2008-03-25 8:09 ` Shawn O. Pearce
2008-03-25 13:46 ` Roger C. Soares
2008-03-25 19:48 ` Robin Rosenberg [this message]
2008-03-26 1:37 ` Roger C. Soares
2008-03-26 4:52 ` Shawn O. Pearce
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=200803252048.48531.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--cc=rogersoares@intelinet.com.br \
--cc=spearce@spearce.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).