Sublime Forum

Atomic save not atomic?

#1

Hey

I think I may be hitting a bug in Sublime Text 3. I’m editing a file (with “atomic_save”: true set). Before saving the file I run ls -i in the directory, and record the inode number. I then save the file, and the inode number doesn’t change.

If sublime were writing to a new file, then renaming over the top, I’d expect to see the inode number of the file change. This is what I see happen with “vim” and other editors.

This is a problem for me in conflation with a bug in the VMware host tools – there’s a bug in vmhgfs, but atomic save behaving the way it behaves with VIM does seem to work around the issue. It’s also concerning that atomic save is (apparently) not atomic?

Platform is OS X Mavericks, on a HFS+ partition.

Thanks
Grahame

0 Likes
#2

Any change of a reply to this?

0 Likes
#3

Your question is illogical. There have obviously been no replies to this, so how could one have changed?

0 Likes
#4

I think angrygoat meant “chance”.

0 Likes
#5

I know.
Just a little deadpan Spock humor.
Bored out of my mind. Burned out and sick and tired of winter.
And what the hell, this way we up the post and view count.
You realize jps hasn’t posted once in over a month?
I think the dingos ate him.

0 Likes
#6

Yeah, typo :smile: Oops. Well, in Australia it’s hot enough that it’s hard to sleep so winter isn’t all bad.

First time in this forum, I’m mostly just a happy sublime user, this is the first problem I’ve hit.

Oh well, hopefully jps will come back!

0 Likes