git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: しらいしななこ <nanako3@bluebottle.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	git@vger.kernel.org
Subject: Re: [PATCH] Per-path attribute based hunk header selection.
Date: Sun, 8 Jul 2007 12:58:21 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707081254450.4248@racer.site> (raw)
In-Reply-To: <7v1wfj4auu.fsf@assigned-by-dhcp.cox.net>

Hi,

On Sun, 8 Jul 2007, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> >> > +	if (!strcmp(ident, "tex"))
> >> > +		return "^\\\\\\(sub\\)*section{";
> >
> > It is always easier, and will never require C skills, to put this into the 
> > config. With Junio's current version:
> >
> > 	echo '*.tex funcname=tex' >> .gitattributes
> > 	echo '[funcname] tex = ^\(\\\(sub\)*section{.*\)' >> .git/config
> >
> > The problem is of course that the backslashes have to be escaped _both_ in 
> > C and in regexps.
> 
> I think giving a reasonable set of basic language support as
> built-in patterns is important for usability.  Otherwise the
> users end up needing to have them in their $HOME/.gitconfig.

I agree.

> I am not sure if Java and LaTeX qualify as the first two most important 
> cases, but they are what we already have demonstrated.

Java and LaTeX are the two languages I use, for which the inbuilt funcname 
default is absolutely unusable.  Given that Java is the only language with 
a notable git-related code base, for which the default fails, Java is the 
prime (if not the only) reason I wanted this whole patch series in the 
first place.

> How about doing something like this?

I do not see how a table in diff.c could be easier to maintain than a 
small part in a small function in diff.c.  It would make sense, though, to 
move the table to xdiff-interface.[ch].

Ciao,
Dscho

  reply	other threads:[~2007-07-08 12:05 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04 18:06 [PATCH 2/2] diff: add custom regular expressions for function names Johannes Schindelin
2007-07-04 18:41 ` Linus Torvalds
2007-07-04 18:45   ` Johannes Schindelin
2007-07-04 20:44   ` Junio C Hamano
2007-07-04 21:20     ` Johannes Schindelin
2007-07-05  5:00     ` Junio C Hamano
2007-07-05  5:02       ` [PATCH 1/2] Future-proof source for changes in xdemitconf_t Junio C Hamano
2007-07-05 11:01         ` Johannes Schindelin
2007-07-05  5:02       ` [PATCH 2/2] WIP per-path attribute based hunk header selection Junio C Hamano
2007-07-05 11:25         ` Johannes Schindelin
2007-07-05 16:43           ` Junio C Hamano
2007-07-06  8:37           ` [PATCH 1/3] Introduce diff_filespec_is_binary() Junio C Hamano
2007-07-06 12:20             ` Johannes Schindelin
2007-07-06  8:39           ` [PATCH] Per-path attribute based hunk header selection Junio C Hamano
2007-07-06 12:38             ` Johannes Schindelin
2007-07-06 17:59             ` Linus Torvalds
2007-07-07  2:00               ` Junio C Hamano
2007-07-07 10:08                 ` しらいしななこ
2007-07-07 10:22                   ` Junio C Hamano
2007-07-07 12:17                     ` Johannes Schindelin
2007-07-07 20:36                       ` Junio C Hamano
2007-07-08  7:23                       ` Junio C Hamano
2007-07-08 11:58                         ` Johannes Schindelin [this message]
2007-07-09  3:22                 ` Nicolas Pitre
2007-07-09  5:05                   ` Junio C Hamano
2007-07-09 11:40                     ` Johannes Schindelin
2007-07-07 10:12               ` [PATCH] Fix configuration syntax to specify customized hunk header patterns Junio C Hamano
2007-07-05  8:24       ` [PATCH 2/2] diff: add custom regular expressions for function names Florian Weimer
2007-07-05 11:44       ` Johannes Schindelin

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=Pine.LNX.4.64.0707081254450.4248@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=nanako3@bluebottle.com \
    --cc=torvalds@linux-foundation.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).