From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 34911@debbugs.gnu.org
Subject: bug#34911: 26.1; doc about lock file names
Date: Sun, 19 May 2019 16:29:37 +0000 (UTC) [thread overview]
Message-ID: <4a06302a-e494-45bc-bdb2-06d2fe68974b@default> (raw)
In-Reply-To: <87y332bhsi.fsf@gmail.com>
> >> >> The default value is "^\\.?#\\|^\\.$\\|^\\.\\.$".
> >> >>
> >> >> \\.?# matches only the first char of an auto-save file
> >> >> name, and the first two chars of a lock file name. It
> >> >> does not match the full name, requiring it to end with
> >> >> `#'. That means that (1) it cannot be used as is for,
> >> >> say, font-locking such a (complete) name, and (2) as
> >> >> it is now, it can falsely identify files that are not
> >> >> auto-save or lock files.
> >> >
> >> > It's a regexp, so of course you can name files which aren't auto-save or
> >> > lock files in such a way that they match it.
> >>
> >> After looking at it some more, I realize you were probably suggesting
> >> that the regexp should have something like "^.#\\|^#.*#$" instead of
> >> "^\\.?#"
> >
> > No, I don't think so. It is correct, I think, to
> > say that the beginning matches .# (or the whole
> > thing matches . or ..) - that is, the dot is literal.
>
> Sorry, forgot to escape the dot, I meant
>
> "^\\.#\\|^#.*#$" instead of "^\\.?#"
I don't think so. More like this, I think:
"^\\.?#[^#]#$\\|^\\.$\\|^\\.\\.$" or preferably this:
"\\`\\.?#[^#]#\\'\\|\\`\\.\\'\\|\\`\\.\\.\\'"
But maybe .* is better than [^#]; dunno.
I don't have time to check right now, but I think
the names to match, besides . and .., start with
.# or # and end with #. The idea is to match the
start and end, and whatever is between the two.
next prev parent reply other threads:[~2019-05-19 16:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<db8aca56-6185-4e1a-a627-53aed26103c2@default>
[not found] ` <<83bm27uzbr.fsf@gnu.org>
2019-03-19 14:54 ` bug#34911: 26.1; doc about lock file names Drew Adams
2019-03-19 18:23 ` Eli Zaretskii
2019-05-12 16:34 ` Noam Postavsky
2019-05-19 14:43 ` Noam Postavsky
2019-05-19 15:04 ` Drew Adams
2019-05-19 15:11 ` Noam Postavsky
2019-05-19 16:29 ` Drew Adams [this message]
2019-05-19 17:22 ` Noam Postavsky
2019-05-19 19:49 ` Drew Adams
2020-08-26 10:39 ` Lars Ingebrigtsen
2020-08-26 16:55 ` Drew Adams
[not found] <<<db8aca56-6185-4e1a-a627-53aed26103c2@default>
[not found] ` <<<83bm27uzbr.fsf@gnu.org>
[not found] ` <<a916e9f9-e66e-40b8-b02d-1d697108774e@default>
[not found] ` <<83r2b2u3j4.fsf@gnu.org>
2019-03-19 20:15 ` Drew Adams
2019-03-19 20:23 ` Eli Zaretskii
2019-03-18 22:47 Drew Adams
2019-03-18 23:17 ` Glenn Morris
2019-03-19 0:28 ` Drew Adams
2019-03-19 7:07 ` Eli Zaretskii
2019-03-19 6:56 ` Eli Zaretskii
2019-03-19 11:49 ` Eli Zaretskii
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=4a06302a-e494-45bc-bdb2-06d2fe68974b@default \
--to=drew.adams@oracle.com \
--cc=34911@debbugs.gnu.org \
--cc=npostavs@gmail.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 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.