From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: schwab@linux-m68k.org, 8159@debbugs.gnu.org
Subject: bug#8159: file-name-sans-version fails for some git files
Date: Sat, 05 Mar 2011 19:00:01 +0200 [thread overview]
Message-ID: <8362rxiju6.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTi=T5bX-x0jvMzJdZDOhR6Tez9Gh8pUC1Uet9zda@mail.gmail.com>
> Date: Sat, 5 Mar 2011 16:42:40 +0000
> From: Reuben Thomas <rrt@sc3d.org>
> Cc: schwab@linux-m68k.org, 8159@debbugs.gnu.org
>
> >> \\(?:~\\|\\.~[-[:alnum:]:#@^._]+\\(~[[:digit:]]+\\)?~\\)
> >>
> >> would cope with just the git version scheme, while not swallowing
> >> multiple backup suffixes.
> >
> > I would suggest a comment mentioning the git case with an example.
>
> So, something like:
>
> (defvar file-name-version-regexp
> "\\(?:~\\|\\.~[-[:alnum:]:#@^._]+\\(~[[:digit:]]+\\)?~\\)"
> ;; The optional ~[[:digit]]+ matches relative versions in git like `HEAD~2'
> "Regular expression matching the backup/version part of a file name.
> Used by `file-name-sans-versions'.")
>
> ?
Yes, that's fine. Thanks.
next prev parent reply other threads:[~2011-03-05 17:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 22:31 bug#8159: file-name-sans-version fails for some git files Reuben Thomas
2011-03-03 3:58 ` Eli Zaretskii
2011-03-03 12:02 ` Reuben Thomas
2011-03-03 13:36 ` Eli Zaretskii
2011-03-03 13:39 ` Reuben Thomas
2011-03-03 13:57 ` Eli Zaretskii
2011-03-03 14:00 ` Reuben Thomas
2011-03-03 15:09 ` Andreas Schwab
2011-03-03 15:26 ` Reuben Thomas
2011-03-03 16:23 ` Andreas Schwab
2011-03-03 22:58 ` Reuben Thomas
2011-03-04 7:55 ` Eli Zaretskii
2011-03-05 16:42 ` Reuben Thomas
2011-03-05 17:00 ` Eli Zaretskii [this message]
2011-03-05 20:36 ` Chong Yidong
2011-03-03 14:33 ` Andreas Schwab
2011-03-03 14:35 ` Reuben Thomas
2011-03-03 14:45 ` Andreas Schwab
2011-03-03 14:53 ` Reuben Thomas
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=8362rxiju6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=8159@debbugs.gnu.org \
--cc=rrt@sc3d.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.