From: "Zoë Blade" <zoe@bytenoise.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] userdiff: add support for Fountain documents
Date: Sun, 19 Jul 2015 13:30:28 +0100 [thread overview]
Message-ID: <562D4AFF-BFC1-4234-8362-656D1F54DFD0@bytenoise.co.uk> (raw)
In-Reply-To: <xmqq380m1k3g.fsf@gitster.dls.corp.google.com>
On 17 Jul 2015, at 23:43, Junio C Hamano <gitster@pobox.com> wrote:
> * Although uppercase is recommended for Scene Headings to increase
> readability, it is not required.
>
> * A line beginning with any of the following, followed by either a
> dot or a space, is considered a Scene Heading (unless the line is
> preceded by an exclamation point !). Case insensitive.
>
> INT
> EXT
> EST
> INT./EXT
> INT/EXT
> I/E
>
> * You can "force" a Scene Heading by starting the line with a
> single period.
>
> * Scene Headings can optionally be appended with Scene
> Numbers. Scene numbers are any alphanumerics (plus dashes and
> periods), wrapped in #.
>
> So, it appears wrong to insist on capital letters in the patterns.
> The pattern in the patch does not even accept punctuations on the
> line other than apostrophe. I won't judge if it is OK to limit to
> US-ASCII ;-)
>
> IPATTERNS("fountain",
> "^([.][^.]|(INT|EXT|EST|INT./EXT|INT/EXT|I/E)[. ]",
> "[^ \t-]+"),
>
> or something like this, perhaps?
Good points, thanks!
This regex should be a bit sturdier:
$ cat scenes.txt
int. yes - day
INT. YES - DAY #1A#
EXT. YES - DAY
.YES TOO
!EXT. NO
INT/EXT YES - DAY
INT./EXT YES - DAY
I/E YES - DAY
no
NO
NO.
!.NO.
int yes - day
est yes - day
!EXT. NO - DAY
$ grep -E "^((\.|(([Ii][Nn][Tt]|[Ee][Ss][Tt]|[Ee][Xx][Tt])?\\.?|[Ii]([Nn][Tt])?\.?/[Ee]([Xx][Tt])?\.?) ).+)$" scenes.txt
int. yes - day
INT. YES - DAY #1A#
EXT. YES - DAY
.YES TOO
INT/EXT YES - DAY
INT./EXT YES - DAY
I/E YES - DAY
int yes - day
est yes - day
Revised version of patch incoming...
next prev parent reply other threads:[~2015-07-19 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 14:21 [PATCH] userdiff: add support for Fountain documents Zoë Blade
2015-07-17 17:12 ` Junio C Hamano
2015-07-17 22:43 ` Junio C Hamano
2015-07-19 12:30 ` Zoë Blade [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-07-21 13:22 Zoë Blade
2015-07-21 19:33 ` Junio C Hamano
2015-07-22 16:31 ` Zoë Blade
2015-07-29 11:19 ` Zoë Blade
2015-07-19 12:31 Zoë Blade
2015-07-20 21:17 ` Junio C Hamano
2015-07-21 13:23 ` Zoë Blade
2015-07-17 11:59 Zoë Blade
2015-07-17 13:03 ` Johannes Schindelin
2015-07-17 14:03 ` Zoë Blade
2015-07-17 16:20 ` 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
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=562D4AFF-BFC1-4234-8362-656D1F54DFD0@bytenoise.co.uk \
--to=zoe@bytenoise.co.uk \
--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).