bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Glenn Morris]

[ This ended up at the wrong address (because of the weird To:).
I am resending it so it appears on bug-gnu-emacs.
Please followup to the OP and 11681@debbugs. ]


From: Olaf <is.er@inter.net>
Subject: bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug
To: gnu-emacs-bug@moderators.isc.org
Date: Tue, 12 Jun 2012 13:00:28 +0200

Hi,

using the GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) binary package from
ftp.gnu.org on C-x C-s the status bar shows "-\**- Filename" and the
message comes Saving file ... but the file isn't saved! It contains the
old contents!

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Eli Zaretskii]

> From: Glenn Morris <rgm@gnu.org>
> Date: Tue, 12 Jun 2012 13:24:11 -0400
> 
> using the GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) binary package from
> ftp.gnu.org on C-x C-s the status bar shows "-\**- Filename" and the
> message comes Saving file ... but the file isn't saved! It contains the
> old contents!

What kind of file is it? on a local filesystem or a remote (networked)
one?

Also, are you sure the file is not in one of the directories that are
protected by the OS?  Such files are written to the Virtual Store,
into a shadow directory.

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Eli Zaretskii]

> From: Glenn Morris <rgm@gnu.org>
> Date: Tue, 12 Jun 2012 13:24:11 -0400
> 
> 
> [ This ended up at the wrong address (because of the weird To:).
> I am resending it so it appears on bug-gnu-emacs.
> Please followup to the OP and 11681@debbugs. ]

The response to the OP bounced.

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Olaf]

Sorry four response email bounds - it's to avoid spam. I'm using the
news server.

>> using the GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) binary package from
>> ftp.gnu.org on C-x C-s the status bar shows "-\**- Filename" and the
>> message comes Saving file ... but the file isn't saved! It contains the
>> old contents!
> 
> What kind of file is it? on a local filesystem or a remote (networked)
> one?

it's a local file. The same did work with the old windows port 23.1.
Please note, that the message is Save ... and no Wrote ... has been seen.

The message buffer is

For information about GNU Emacs and the GNU system, type C-h C-a.
SignumDP.v has auto save data; consider M-x recover-this-file
Loading vc-hg...done
Saving file
d:/work/StructuralHealth/Software/PSoC5/Harvester/SignumComparator/SignumDP.cydsn/SignumDP/ms/SignumDP.v...
Auto-saving...


Auto save file #filename# appears in the directory!

> Also, are you sure the file is not in one of the directories that are
> protected by the OS?  Such files are written to the Virtual Store,
> into a shadow directory.

I'm sure, it's a standard ntfs file system where the common file/dir
permissions are. As mentioned before the prior used emacs did not have
this problem.

I start emacs by runemacs. running emacs from console by emacs -Q -q it
susccessfully wrote the file.

emacs origin is the binary (with elisp) http://ftp.gnu.org/pub/gnu/emacs/

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Eli Zaretskii]

> From: Olaf <is.er@inter.net>
> Date: Wed, 13 Jun 2012 07:40:01 +0200
> 
> Sorry four response email bounds - it's to avoid spam. I'm using the
> news server.

It's too bad we cannot communicate with you directly.  It means we
need to edit the headers of the messages we send in response manually,
or risk sending them to a bit bucket.

> it's a local file. The same did work with the old windows port 23.1.
> Please note, that the message is Save ... and no Wrote ... has been seen.
> 
> The message buffer is
> 
> For information about GNU Emacs and the GNU system, type C-h C-a.
> SignumDP.v has auto save data; consider M-x recover-this-file
> Loading vc-hg...done
> Saving file
> d:/work/StructuralHealth/Software/PSoC5/Harvester/SignumComparator/SignumDP.cydsn/SignumDP/ms/SignumDP.v...
> Auto-saving...

Does this happen for every file you save, or just for some?  If the
latter, can you try finding out what those files have in common?

> I start emacs by runemacs. running emacs from console by emacs -Q -q it
> susccessfully wrote the file.

So you are saying that if you start Emacs by clicking the runemacs
icon, then you cannot save any files, whereas if you start Emacs by
running emacs.exe directly, the problem goes away, is that right?

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Olaf]

>> it's a local file. The same did work with the old windows port 23.1.
>> Please note, that the message is Save ... and no Wrote ... has been seen.
>>
>> The message buffer is
>>
>> For information about GNU Emacs and the GNU system, type C-h C-a.
>> SignumDP.v has auto save data; consider M-x recover-this-file
>> Loading vc-hg...done
>> Saving file
>> d:/work/StructuralHealth/Software/PSoC5/Harvester/SignumComparator/SignumDP.cydsn/SignumDP/ms/SignumDP.v...
>> Auto-saving...
> 
> Does this happen for every file you save, or just for some?  If the
> latter, can you try finding out what those files have in common?

for every file, every local drive (network drives not tested)

>> I start emacs by runemacs. running emacs from console by emacs -Q -q it
>> susccessfully wrote the file.
> 
> So you are saying that if you start Emacs by clicking the runemacs
> icon, then you cannot save any files, whereas if you start Emacs by
> running emacs.exe directly, the problem goes away, is that right?

It seems to be only if I start the emacs starts by modelsim. Than
procexp shows:

"C:\Program Files (x86)\emacs-24.1\bin\emacs.exe" +1
"D:\work\StructuralHealth\Software\PSoC5\Harvester\SignumComparator\SignumDP.cydsn\SignumDP\ms\SignumDP.v"

If I run runemacs by clicking the icon and drag&drop my file to the
emacs windows from windows explorer procexp show:

"C:\Program Files (x86)\emacs-24.1\bin\emacs.exe"

I can successfully save the file. Even If I start the emacs by left
click "open with ..."!

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Eli Zaretskii]

> From: Olaf <is.er@inter.net>
> Date: Fri, 15 Jun 2012 09:02:29 +0200
> 
> > So you are saying that if you start Emacs by clicking the runemacs
> > icon, then you cannot save any files, whereas if you start Emacs by
> > running emacs.exe directly, the problem goes away, is that right?
> 
> It seems to be only if I start the emacs starts by modelsim.

What is "modelsim"?  And how did you set up modelsim, whatever it is,
to invoke Emacs?

> Than procexp shows:
> 
> "C:\Program Files (x86)\emacs-24.1\bin\emacs.exe" +1
> "D:\work\StructuralHealth\Software\PSoC5\Harvester\SignumComparator\SignumDP.cydsn\SignumDP\ms\SignumDP.v"
> 
> If I run runemacs by clicking the icon and drag&drop my file to the
> emacs windows from windows explorer procexp show:
> 
> "C:\Program Files (x86)\emacs-24.1\bin\emacs.exe"
> 
> I can successfully save the file. Even If I start the emacs by left
> click "open with ..."!

And if you invoke Emacs manually with the +1 switch as ProcExp shows,
can you then reproduce the problem?

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Olaf]

>>> So you are saying that if you start Emacs by clicking the runemacs
>>> icon, then you cannot save any files, whereas if you start Emacs by
>>> running emacs.exe directly, the problem goes away, is that right?
>>
>> It seems to be only if I start the emacs starts by modelsim.
> 
> What is "modelsim"?  And how did you set up modelsim, whatever it is,
> to invoke Emacs?

Modelsim is a simulation program (www.model.com)

Mmmh, how did I setup - good question. I did not found any settings here
to set up ann external editor. I assume it's started by registry
settings. Do you know the key?

>> Than procexp shows:
>>
>> "C:\Program Files (x86)\emacs-24.1\bin\emacs.exe" +1
>> "D:\work\StructuralHealth\Software\PSoC5\Harvester\SignumComparator\SignumDP.cydsn\SignumDP\ms\SignumDP.v"
>>
>> If I run runemacs by clicking the icon and drag&drop my file to the
>> emacs windows from windows explorer procexp show:
>>
>> "C:\Program Files (x86)\emacs-24.1\bin\emacs.exe"
>>
>> I can successfully save the file. Even If I start the emacs by left
>> click "open with ..."!
> 
> And if you invoke Emacs manually with the +1 switch as ProcExp shows,
> can you then reproduce the problem?

No, it works even with the command line argument +1 correct.

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Eli Zaretskii]

> From: Olaf <is.er@inter.net>
> Date: Mon, 18 Jun 2012 11:48:36 +0200
> 
> >>> So you are saying that if you start Emacs by clicking the runemacs
> >>> icon, then you cannot save any files, whereas if you start Emacs by
> >>> running emacs.exe directly, the problem goes away, is that right?
> >>
> >> It seems to be only if I start the emacs starts by modelsim.
> > 
> > What is "modelsim"?  And how did you set up modelsim, whatever it is,
> > to invoke Emacs?
> 
> Modelsim is a simulation program (www.model.com)
> 
> Mmmh, how did I setup - good question. I did not found any settings here
> to set up ann external editor. I assume it's started by registry
> settings. Do you know the key?

??? You mean, modelsim detected automatically that Emacs is installed
and automatically adapted itself to invoke Emacs as its editor?  I'd
be surprised.

The registry keys set by Emacs are these:

 "SOFTWARE\GNU\Emacs"
 "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\emacs.exe"
 "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\runemacs.exe"

> > And if you invoke Emacs manually with the +1 switch as ProcExp shows,
> > can you then reproduce the problem?
> 
> No, it works even with the command line argument +1 correct.

That probably means that the problem is in how modelsim invokes Emacs.
I know nothing about modelsim; any chance you could ask its
maintainers about this problem?

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Stefan Monnier]

> That probably means that the problem is in how modelsim invokes Emacs.
> I know nothing about modelsim; any chance you could ask its
> maintainers about this problem?

Maybe checking the value of command-line-args would give us a clue?


        Stefan

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Eli Zaretskii]

> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Cc: 11681@debbugs.gnu.org
> Date: Mon, 18 Jun 2012 16:31:35 -0400
> 
> > That probably means that the problem is in how modelsim invokes Emacs.
> > I know nothing about modelsim; any chance you could ask its
> > maintainers about this problem?
> 
> Maybe checking the value of command-line-args would give us a clue?

Couldn't hurt, although I don't hold my breath, since the OP already
reported the same information as seen by the Process Explorer program.

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Olaf]

>>>>> So you are saying that if you start Emacs by clicking the runemacs
>>>>> icon, then you cannot save any files, whereas if you start Emacs by
>>>>> running emacs.exe directly, the problem goes away, is that right?
>>>>
>>>> It seems to be only if I start the emacs starts by modelsim.
>>>
>>> What is "modelsim"?  And how did you set up modelsim, whatever it is,
>>> to invoke Emacs?
>>
>> Modelsim is a simulation program (www.model.com)
>>
>> Mmmh, how did I setup - good question. I did not found any settings here
>> to set up ann external editor. I assume it's started by registry
>> settings. Do you know the key?
> 
> ??? You mean, modelsim detected automatically that Emacs is installed
> and automatically adapted itself to invoke Emacs as its editor?  I'd
> be surprised.

Probably not. I assume that it uses the registry settings. Modelsim
looks that it has its root at unix (TCL for scripting etc).

> The registry keys set by Emacs are these:
> 
>  "SOFTWARE\GNU\Emacs"
not exist, even on CURRENT USER and LOCAL_MACHINE

>  "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\emacs.exe"
>  "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\runemacs.exe"

also not found, I'm using win7 x64!

>>> And if you invoke Emacs manually with the +1 switch as ProcExp shows,
>>> can you then reproduce the problem?
>>
>> No, it works even with the command line argument +1 correct.
> 
> That probably means that the problem is in how modelsim invokes Emacs.
> I know nothing about modelsim; any chance you could ask its
> maintainers about this problem?

I will check it again

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Juanma Barranquero]

On Tue, Jun 19, 2012 at 7:37 AM, Olaf <is.er@inter.net> wrote:

>>  "SOFTWARE\GNU\Emacs"
> not exist, even on CURRENT USER and LOCAL_MACHINE

Try HLKM\SOFTWARE\Wow6432Node\GNU\Emacs

>>  "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\emacs.exe"
>>  "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\runemacs.exe"
>
> also not found, I'm using win7 x64!

"HLKM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths" does exist
on win7 64-bit. If the emacs.exe and runemacs.exe keys do not exist,
that could mean that addpm.exe has not run, or that it somehow didn't
have permission to write these to the registry.

    Juanma

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 19 Jun 2012 13:28:49 +0200
> Cc: gnu-emacs-bug@moderators.isc.org
> 
> "HLKM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths" does exist
> on win7 64-bit. If the emacs.exe and runemacs.exe keys do not exist,
> that could mean that addpm.exe has not run, or that it somehow didn't
> have permission to write these to the registry.

Which of course is not a problem in itself, because Emacs does not
need these registry entries to work correctly.

I only mentioned the keys because Olaf asked about them, thinking that
perhaps modelsim somehow accessed and/or used them.

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Olaf]

>>>  "SOFTWARE\GNU\Emacs"
>> not exist, even on CURRENT USER and LOCAL_MACHINE
> 
> Try HLKM\SOFTWARE\Wow6432Node\GNU\Emacs
> 
>>>  "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\emacs.exe"
>>>  "SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\runemacs.exe"
>>
>> also not found, I'm using win7 x64!
> 
> "HLKM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths" does exist
> on win7 64-bit. If the emacs.exe and runemacs.exe keys do not exist,
> that could mean that addpm.exe has not run, or that it somehow didn't
> have permission to write these to the registry.

OK; I update my simulation program (reinstall modelsim) and did run
addpm as normal user and administrator. The registry keys are here. The
problem still exist.

Running 'open with' on explorer works so the problem seems to be related
to modelsim ...

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Achim Gratz]

Olaf writes:
> OK; I update my simulation program (reinstall modelsim) and did run
> addpm as normal user and administrator. The registry keys are here. The
> problem still exist.

So maybe Modelsim comes with a captive installation of Emacs and
runemacs and runemacs then follows PATH to find a different Emacs than
the one provided with Modelsim?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

bug#11681: GNU Emacs 24.1.1 (i386-mingw-nt6.1.7601) Save bug

[Lars Ingebrigtsen]

Achim Gratz <Stromeko@nexgo.de> writes:

> Olaf writes:
>> OK; I update my simulation program (reinstall modelsim) and did run
>> addpm as normal user and administrator. The registry keys are here. The
>> problem still exist.
>
> So maybe Modelsim comes with a captive installation of Emacs and
> runemacs and runemacs then follows PATH to find a different Emacs than
> the one provided with Modelsim?

More information was requested, but no response was given within a few
months, so I'm closing this bug report.  If the problem still exists,
please reopen this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no