bug#1687: emacs bug 1687

bug#1687: emacs bug 1687

[Relson, David]

Found the cause !!

File c:/user/.emacs.desktop.lock contains the PID in the error message.

Deleting the file makes the warning go away.

I've done some further testing.  With emacs open, the lock file is
created.  If I open a second copy of emacs, the message appears.  

This is a change in behavior.  I used to be able to open multiple copies
of emacs without error messages.

FWIW, due to a hard drive upgrade I have a new installation of emacs
(v22.1.50.10).  Previously I was running v22.1.1

bug#1687: emacs bug 1687

[Juanma Barranquero]

On Thu, Jan 29, 2009 at 15:29, Relson, David <david.relson@orion-sys.com> wrote:

> Deleting the file makes the warning go away.
>
> I've done some further testing.  With emacs open, the lock file is
> created.  If I open a second copy of emacs, the message appears.

Of course.

> This is a change in behavior.  I used to be able to open multiple copies
> of emacs without error messages.

Yes. It first appeared (in a released version) in Emacs 22.2.

You seem to prefer avoiding the warning and risking losing your desktop. Weird.

> FWIW, due to a hard drive upgrade I have a new installation of emacs
> (v22.1.50.10).  Previously I was running v22.1.1

Yes, the feature was added three weeks after the 22.1 release.

Why are you running 22.1.50? I'd recommend getting 22.3, which has
many bugfixes over what you're using now.

    Juanma

bug#1687: emacs bug 1687

[Relson, David]

I've compared old and new copies of desktop.el, i.e.

 49240 Aug 18  2007 c:/Program Files/GNU/ntemacs22/lisp/desktop.el
 45692 Apr 12  2007 d:/Program Files/GNU/emacs-22.1/lisp/desktop.el

And found the appearance of the PID message within the few months from
April to August !

Letting the last instance of emacs overwrite the desktop is not a big
deal.  Since multiple instances start with the same desktop, they'll be
writing similar desktop files, so it's likely that little, or no,
information will be lost.

>> Why are you running 22.1.50? I'd recommend getting 22.3, which has
many bugfixes over what you're using now.

Because when I did a websearch for ntemacs 22.1.50 is what was found.

bug#1687: emacs bug 1687

[Juanma Barranquero]

On Thu, Jan 29, 2009 at 16:29, Relson, David <david.relson@orion-sys.com> wrote:

> I've compared old and new copies of desktop.el, i.e.
>
>  49240 Aug 18  2007 c:/Program Files/GNU/ntemacs22/lisp/desktop.el
>  45692 Apr 12  2007 d:/Program Files/GNU/emacs-22.1/lisp/desktop.el
>
> And found the appearance of the PID message within the few months from
> April to August !

2007-06-24, to be exact. Three weeks after the release of 22.1.

> Letting the last instance of emacs overwrite the desktop is not a big
> deal.  Since multiple instances start with the same desktop, they'll be
> writing similar desktop files, so it's likely that little, or no,
> information will be lost.

Most of the time. Once or twice, just to keep you on your toes, you
will set up Emacs with lots of loaded files that you need for some
project, and then you'll overwrite the carefully laid desktop with an
empty desktop from a forgotten Emacs instance ;-)

> Because when I did a websearch for ntemacs 22.1.50 is what was found.

If you're using Emacs on Windows, you can download much more
up-to-date versions from here:

http://ourcomments.org/Emacs/EmacsW32.html

    Juanma

bug#1687: emacs bug 1687

[Relson, David]

>> If you're using Emacs on Windows, you can download much more
>> up-to-date versions from here:

>> http://ourcomments.org/Emacs/EmacsW32.html

Thanks!  I wasn't aware of ourcomments.org.  I'm downloading the latest
& greatest as I write this.

David