Unable to save a file #52228
Comments
|
(Experimental duplicate detection) |
|
Please provide more details. |
|
After updating vs code to the latest version
Whenever i am making any changes in the file and try to save it
Its giving me an error that the content on the disk is newer and you might
want to compare it
But its contain the old changes
So i am unable to save the current file
I need to close the file and open it again to add my new changes to it.
I am mostly working on php files
So i dont know about other file types,
Its very frustrating to use VS Code in such conditions.
…On Tue, Jun 19, 2018 at 2:42 PM, Christof Marti ***@***.***> wrote:
Please provide more details.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52228 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY0CmPkUSWPWYwNHs6net3xXRcIQ_TF5ks5t-MB2gaJpZM4UsVJk>
.
|
|
Maybe you have a background task that touches the file? Which OS are you on? |
|
I wonder if this issue is being caused by an installed extension. Can you try to run VS Code without extensions? From the command line (NOT the integrated terminal in Code), execute: |
|
I tried disabling the vs code extension but still i am getting the same
issue
I tried using this
code --disable-extensions
but it doesn't causing any effect
as I am getting some unexpected error from php intellisense
Which are not correct, Its giving me an error on a perfect syntax statement
And after some time i realise that if i changed the language from php to
html
I am not getting this type of error
…On Wed, Jun 20, 2018 at 1:39 PM, Benjamin Pasero ***@***.***> wrote:
I wonder if this issue is being caused by an installed extension. Can you
try to run VS Code without extensions? From the command line (NOT the
integrated terminal in Code), execute: code --disable-extensions and try
your steps again to see if it reproduces. If you see it is an issue with
the extension, please file it against the extension repository itself.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#52228 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY0CmOl4b6HAFz56GfNzAwx2xhDfbcJcks5t-gNCgaJpZM4UsVJk>
.
|
|
@neodisk17 are you using a remote file system maybe or is this a local disk? |
|
No ,I am using local disk.
The file is saved in my local system
And I am not using any remote connection
…On Mon, Jun 25, 2018 at 10:29 AM, Benjamin Pasero ***@***.***> wrote:
@neodisk17 <https://github.com/neodisk17> are you using a remote file
system maybe or is this a local disk?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#52228 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY0CmFG9APS5jVfVdzykfudXGw_JjsP8ks5uAG4qgaJpZM4UsVJk>
.
|
|
@neodisk17 but you already verified that this only happens for some file types but not all? |
|
Yes, Its happenng only for PHP files. But my majority of work is on PHP Please help me how can i solve this problem. |
|
@neodisk17 do you have any tool running outside of VSCode that could touch/write the PHP files? |
|
Only my git bash is running in the backgroung. |
|
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/ |
|
ok
I will try using it.
…On Tue, Jun 26, 2018 at 10:15 AM, Benjamin Pasero ***@***.***> wrote:
Can you try to reproduce with our nightly insider builds? You can give our
preview releases a try from: https://code.visualstudio.com/insiders/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#52228 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY0CmCZN5MdOfAZSOghlGgfjvWmOOHlmks5uAbxhgaJpZM4UsVJk>
.
|
|
I had tried the insider builds,it was great, I am not getting any file saving issues while using it. |
|
@neodisk17 what if you configure the exact same settings and install the exact same extensions you have in the stable version for that insiders version, does it still work? |
|
Nope I haven't install all the extension.
I had only installed which were important for me at that time.
I will try to install all the extension and let you know
…On Sat, Jun 30, 2018 at 1:24 PM, Benjamin Pasero ***@***.***> wrote:
@neodisk17 <https://github.com/neodisk17> what if you configure the exact
same settings and install the exact same extensions you have in the stable
version for that insiders version, does it still work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#52228 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY0CmBIlm4n0NZRaSm6xYiJ_W8yP5SCZks5uBy64gaJpZM4UsVJk>
.
|
|
I had use the same configuration and install the same extensions as of the
stable version,
But it seems that there are no problems while saving files that arise in
stable version
I just wanted to know that when will be the insiders preview will be
merged in the stable version?
…On Sat, Jun 30, 2018 at 11:39 PM, LOKESH KUMAR ***@***.***> wrote:
Nope I haven't install all the extension.
I had only installed which were important for me at that time.
I will try to install all the extension and let you know
On Sat, Jun 30, 2018 at 1:24 PM, Benjamin Pasero ***@***.***
> wrote:
> @neodisk17 <https://github.com/neodisk17> what if you configure the
> exact same settings and install the exact same extensions you have in the
> stable version for that insiders version, does it still work?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#52228 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AY0CmBIlm4n0NZRaSm6xYiJ_W8yP5SCZks5uBy64gaJpZM4UsVJk>
> .
>
|
|
Insiders from when you reported it working has been released as the new stable version last Wednesday. Let us know when you see this again. Thanks. |
We have written the needed data into your clipboard because it was too large to send. Please paste.
The text was updated successfully, but these errors were encountered: