all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 12028@debbugs.gnu.org
Subject: bug#12028: Lock file name
Date: Mon, 30 Jul 2012 01:30:38 +0200	[thread overview]
Message-ID: <CAMXnza1O5Xy+f4jLMdP2duve2genAS49vVJJ5rJud8drntGsHw@mail.gmail.com> (raw)
In-Reply-To: <towr1mb1jh.fsf@fencepost.gnu.org>

Hi Glenn,

On Mon, Jul 30, 2012 at 1:17 AM, Glenn Morris <rgm@gnu.org> wrote:
> Suvayu Ali wrote:
>
>> I am using GNU Emacs 24.1.50.1 (built 2012-07-21). I see the file naming
>> scheme for lock files is `.#<old name>'. I seemed to recall there was
>> trailing hash like this `.#<old name>#'. But on the Emacs help list I
>> was told there was no trailing hash in the past. So my request is, can a
>> trailing hash be added?
>>
>> My issue in particular is, the lock file gets picked by a glob like
>> `*.cxx'; with a trailing hash, this would only match source files. This
>> can be a problem with tools that only support very basic globbing.
>
> I don't think Emacs needs to change the (very long-standing) name of
> lockfiles for the sake of inflexible tools that cannot exclude dotfiles

I guess you are right. I use the tool only because I have to, it's a
real pain. :(

> (note that normal shell globbing does not match dotfiles at all). Emacs
> 24.2 will have an option `create-lockfiles' that you can set to nil to
> disable the generation of lockfiles altogether, hopefully that works for
> you.

This will work well thank you. :)

-- 
Suvayu

Open source is the future. It sets us free.





      reply	other threads:[~2012-07-29 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  1:03 bug#12028: Lock file name Suvayu Ali
2012-07-29 23:17 ` Glenn Morris
2012-07-29 23:30   ` suvayu ali [this message]

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=CAMXnza1O5Xy+f4jLMdP2duve2genAS49vVJJ5rJud8drntGsHw@mail.gmail.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=12028@debbugs.gnu.org \
    --cc=rgm@gnu.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.