unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: Jakob <jakob@pipefour.org>, notmuch@notmuchmail.org
Subject: Re: [PATCH] vim: fix regex after "notmuch show" output change
Date: Sat, 24 Mar 2012 10:58:59 +0200	[thread overview]
Message-ID: <m2mx76idd8.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <1332390675-31273-1-git-send-email-jakob@pipefour.org>

Jakob <jakob@pipefour.org> writes:

> The new field "excluded" was added to the output and made this regex fail.
> ---

Is this regexp part below good ?

> +        ... match:\([0-9]*\) excluded:\([[0-9]*\) filename:\(.*\)$', ...

( --> excluded:\([[0-9]*\) <-- )

Otherwise lookg good (I think).

Tomi

>  vim/plugin/notmuch.vim |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/vim/plugin/notmuch.vim b/vim/plugin/notmuch.vim
> index 21985c7..92e1b50 100644
> --- a/vim/plugin/notmuch.vim
> +++ b/vim/plugin/notmuch.vim
> @@ -48,7 +48,7 @@ let s:notmuch_defaults = {
>          \ 'g:notmuch_show_part_end_regexp':          '\fpart}'                   ,
>          \ 'g:notmuch_show_marker_regexp':            '\f\\(message\\|header\\|body\\|attachment\\|part\\)[{}].*$',
>          \
> -        \ 'g:notmuch_show_message_parse_regexp':     '\(id:[^ ]*\) depth:\([0-9]*\) match:\([0-9]*\) filename:\(.*\)$',
> +        \ 'g:notmuch_show_message_parse_regexp':     '\(id:[^ ]*\) depth:\([0-9]*\) match:\([0-9]*\) excluded:\([[0-9]*\) filename:\(.*\)$',
>          \ 'g:notmuch_show_tags_regexp':              '(\([^)]*\))$'               ,
>          \
>          \ 'g:notmuch_show_signature_regexp':         '^\(-- \?\|_\+\)$'           ,
> @@ -870,7 +870,8 @@ function! s:NM_cmd_show_parse(inlines)
>                                          let msg['id'] = m[1]
>                                          let msg['depth'] = m[2]
>                                          let msg['match'] = m[3]
> -                                        let msg['filename'] = m[4]
> +                                        let msg['excluded'] = m[4]
> +                                        let msg['filename'] = m[5]
>                                  endif
>  
>                                  let in_message = 1
> -- 
> 1.7.9.1
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2012-03-24  8:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  4:31 [PATCH] vim: fix regex after "notmuch show" output change Jakob
2012-03-24  8:58 ` Tomi Ollila [this message]
2012-03-25 19:07   ` Jakob
2012-03-25 19:42     ` Tomi Ollila
2012-03-29 21:49       ` Jakob
2012-03-29 22:02         ` Jakob
2012-03-30  5:51           ` Tomi Ollila
2012-04-21  2:22           ` Felipe Contreras

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: https://notmuchmail.org/

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

  git send-email \
    --in-reply-to=m2mx76idd8.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=jakob@pipefour.org \
    --cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.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).