[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#34911: 26.1; doc about lock file names

From: Drew Adams
Subject: bug#34911: 26.1; doc about lock file names
Date: Tue, 19 Mar 2019 13:15:00 -0700 (PDT)

> > 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.
> Then maybe we need to change the default value, but that's a separate
> issue.  AFAIU, the bug report was about documentation.

Yes, improving the default value is welcome (and needed).
But currently it is unchanged.  As a result there is a
doc bug because what the doc says about the default value
is incorrect.  If you fix the default value to be what
the doc says then the doc will not need to change.  Else
it does need to change.

BTW, I think (but am not 100% sure) that `^' and `$' are
the wrong things to use here.  Instead, `\`' and `\''
should be used.

> > Also, please add a doc string for `dired-omit-regexp',
> > referring to `dired-omit-files' (where this missing doc
> > will hopefully be added) and `dired-omit-extensions', as
> > is done for `dired-mark-omitted', for example.
> Another separate issue, unrelated to file locks, AFAIU.

Do you need a separate bug report for that?

> > Does this clarify what I meant by "the default value only
> > approximately matches auto-save files (and lock files?)"?
> Yes, but I don't necessarily see that as a problem.

Why not?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]