git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2018, #04; Wed, 30)
Date: Wed, 30 May 2018 09:09:08 -0700	[thread overview]
Message-ID: <20180530160908.GA8340@D-10-19-29-76.dhcp4.washington.edu> (raw)
In-Reply-To: <xmqqy3g1d4xa.fsf@gitster-ct.c.googlers.com>

On Wed, May 30, 2018 at 03:38:09PM +0900, Junio C Hamano wrote:
> * tb/grep-column (2018-05-14) 7 commits
>  - contrib/git-jump/git-jump: jump to match column in addition to line
>  - grep.c: add configuration variables to show matched option
>  - builtin/grep.c: add '--column' option to 'git-grep(1)'
>  - grep.c: display column number of first match
>  - grep.[ch]: extend grep_opt to allow showing matched column
>  - grep.c: expose matched column in match_line()
>  - Documentation/config.txt: camel-case lineNumber for consistency
>  (this branch is used by tb/grep-only-matching.)
>
>  "git grep" learned the "--column" option that gives not just the
>  line number but the column number of the hit.

The last we spoke about this, we had decided on a "min-starting,
max-ending" semantics for deciding on the columnar offset for extended
patterns like --and, --or, and --not.

I have these patches mostly updated on my copy (available at
https://github.com/ttaylorr/git/compare/tb/grep-column) but am out of
the office for the next week, so I will polish and send these on June
8th.

> * tb/grep-only-matching (2018-05-14) 2 commits
>  - builtin/grep.c: teach '-o', '--only-matching' to 'git-grep'
>  - grep.c: extract show_line_header()
>  (this branch uses tb/grep-column.)

This topic is done, but will be frustrating to merge after the changes
in tb/grep-column. I'll update this topic once tb/grep-column graduates
to master, that way they will both apply cleanly.


Thanks,
Taylor

  reply	other threads:[~2018-05-30 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  6:38 What's cooking in git.git (May 2018, #04; Wed, 30) Junio C Hamano
2018-05-30 16:09 ` Taylor Blau [this message]
2018-05-30 16:12   ` Taylor Blau
2018-06-11 20:04     ` Taylor Blau
2018-06-11 22:44       ` Junio C Hamano
2018-05-31 23:15   ` Junio C Hamano
2018-05-30 16:27 ` Duy Nguyen
2018-05-30 16:43   ` Stefan Beller
2018-05-31 23:58   ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180530160908.GA8340@D-10-19-29-76.dhcp4.washington.edu \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).