Hot to prevent emacs from generating ".#xxxx" files?

Hot to prevent emacs from generating ".#xxxx" files?

[gooood]

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? 
Or put it in another directory such as '/tmp'?
-- 
View this message in context: http://www.nabble.com/Hot-to-prevent-emacs-from-generating-%22.-xxxx%22-files--tp19235974p19235974.html
Sent from the Emacs - Help mailing list archive at Nabble.com.

Re: Hot to prevent emacs from generating ".#xxxx" files?

[David Hansen]

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

Re: Hot to prevent emacs from generating ".#xxxx" files?

[s ticket]

> 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.
>
Because when emacs exits abnormally, it may leave a lot of ".#xxx" files.
It may break some compiling as some compile tools just search all ".c" files
in the directory and complain "can't open .#xxx.c" ;


                                                     yours

                                                  jianbin

Re: Hot to prevent emacs from generating ".#xxxx" files?

[David Hansen]

On Sun, 31 Aug 2008 16:37:04 +0800 s. ticket wrote:

>> 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.
>>
> Because when emacs exits abnormally, it may leave a lot of ".#xxx" files.
> It may break some compiling as some compile tools just search all ".c" files
> in the directory and complain "can't open .#xxx.c" ;

That's exactly why you want them.  After a crash you can M-x
recover-this-file and get you changes back.

David

Re: Hot to prevent emacs from generating ".#xxxx" files?

[s ticket]

>> Because when emacs exits abnormally, it may leave a lot of ".#xxx" files.
>> It may break some compiling as some compile tools just search all ".c" files
>> in the directory and complain "can't open .#xxx.c" ;
>
> That's exactly why you want them.  After a crash you can M-x
> recover-this-file and get you changes back.
Yes. But it's better if I can put them in a special directory like
backup files and auto-save files.






                                                          Jianbin

Re: Hot to prevent emacs from generating ".#xxxx" files?

[David Hansen]

On Sun, 31 Aug 2008 17:01:55 +0800 s. ticket wrote:

>>> Because when emacs exits abnormally, it may leave a lot of ".#xxx" files.
>>> It may break some compiling as some compile tools just search all ".c" files
>>> in the directory and complain "can't open .#xxx.c" ;
>>
>> That's exactly why you want them.  After a crash you can M-x
>> recover-this-file and get you changes back.
> Yes. But it's better if I can put them in a special directory like
> backup files and auto-save files.

If such a file is present you have a far more serious problem, namely
potential data loss.  After you solved that (M-x recover-this-file) the
auto-save file will disappear automatically and the minor problem is
solved as well.

If you insist you can have a look how the tramp package works around
this.  AFAIK it doesn't use the remote directory for auto-save files, or
at least it can be configured to not do so.

David