Losing my SASS sporadically

[Jérôme Gravel-Niquet]

Hey everyone,

First of all, HAML / SASS are great, I just can't go back to plain old
HTML / CSS, this has been such a productivity enhancement!

Onto the problem: For some weird and unknown reason, whenever I don't
refresh my site for a certain amount of time, I end up losing my
changes to my sass file. I'm running Passenger 2.2.3 in development
mode... I can make a lot of changes and then lose them all for no
apparent reason.

Basically I have to rapidly do a command+z in Textmate to get back to
the last state of my sass file. Does it have anything to do with a
cache?

It's frustrating, whenever I forget to do an undo on the sass file to
recuperate my styles, I can lose quite a lot of things. The SASS file
seems to be stuck at the state of when I originally copied it from
another project, which is very weird. Says my file has been modified 2
days ago when I've been actively working on it every day. Could be a
permission issue, but then again, I can save and see my changes on the
site.

I'm at a loss here... I wouldn't post if I had a single clue what to
look for...

Thanks!

[Chris Eppstein]

I can't imagine this is due to haml or sass. We only ever read your
sass files, never write to them.

Are you sure this isn't some artifact of how you're using source
control? This is the kind of thing I would expect if you checked out,
changed branches, etc.

Chris

Hunt & pecked on my iPhone... Sorry if it's brief!

On Jun 29, 2009, at 9:03 AM, Jérôme Gravel-Niquet

[Jérôme Gravel-Niquet]

I figured it would probably not be HAML/SASS, I guess posting here was
a desperate move hehe.

I use Github, but I haven't committed/branched/pushed/pulled or
anything in the last days the problem has been occurring.

So this must be due to either the Spree gem, Passenger... or something
else specific to my system I guess.

Thanks!

On 29 juin, 12:37, Chris Eppstein <ch...@eppsteins.net> wrote:
> I can't imagine this is due to haml or sass. We only ever read your  
> sass files, never write to them.
>
> Are you sure this isn't some artifact of how you're using source  
> control?  This is the kind of thing I would expect if you checked out,  
> changed branches,  etc.
>
> Chris
>
> Hunt & pecked on my iPhone... Sorry if it's brief!
>
> On Jun 29, 2009, at 9:03 AM, Jérôme Gravel-Niquet  
>

[Jérôme Gravel-Niquet]

My bad... completely unrelated to haml or sass!

Thanks though ;)

On 29 juin, 12:37, Chris Eppstein <ch...@eppsteins.net> wrote:

> I can't imagine this is due to haml or sass. We only ever read your  
> sass files, never write to them.
>
> Are you sure this isn't some artifact of how you're using source  
> control?  This is the kind of thing I would expect if you checked out,  
> changed branches,  etc.
>
> Chris
>
> Hunt & pecked on my iPhone... Sorry if it's brief!
>
> On Jun 29, 2009, at 9:03 AM, Jérôme Gravel-Niquet  
>