From: David Hansen <david.hansen@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Hot to prevent emacs from generating ".#xxxx" files?
Date: Sun, 31 Aug 2008 09:43:44 +0200 [thread overview]
Message-ID: <878wudpr2n.fsf@localhorst.mine.nu> (raw)
In-Reply-To: 19235974.post@talk.nabble.com
On Sat, 30 Aug 2008 11:57:51 -0700 (PDT) gooood wrote:
> When edit files with emacs, emacs will generate a broken symbolic link.
> For example if you open ~/a.txt in emacs and type some words,
> there will be a symbolic lnk named .#a.txt in your home directory.
> Is there some method to prevent emacs from generating this file?
Why would you want to do that? Emacs uses them for locking and auto
saving. Unless you like painful data loss you should be happy they are
there.
> Or put it in another directory such as '/tmp'?
I don't think so.
David
next prev parent reply other threads:[~2008-08-31 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 18:57 Hot to prevent emacs from generating ".#xxxx" files? gooood
2008-08-31 7:43 ` David Hansen [this message]
2008-08-31 8:37 ` s ticket
2008-08-31 8:41 ` David Hansen
2008-08-31 9:01 ` s ticket
2008-08-31 9:21 ` David Hansen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878wudpr2n.fsf@localhorst.mine.nu \
--to=david.hansen@gmx.net \
--cc=help-gnu-emacs@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.
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).