Are you using a virtual machine for your dev env? If so make sure the clock on your VM is set to the right time. I had a situation once where I was editing files locally which were then mounted on my dev VM and changes weren't showing in Rails.
On Thu, Jun 25, 2009 at 3:04 PM, Dave Spurr <david.sp...@gmail.com> wrote:
> Are you using a virtual machine for your dev env? If so make sure the
> clock on your VM is set to the right time. I had a situation once where
> I was editing files locally which were then mounted on my dev VM and
> changes weren't showing in Rails.
> -D
> On 25/6/09 12:48, Francis Fish wrote:
> > Hi guys,
> > This is driving me nuts and restarting passenger makes no difference.
> > If I rename the layout and change the name in the controller then it
> > picks it up.
> > CSS seems to suffer from the same problem.
> > I'm convinced that my 2.2.2 project *just works*. Is there something
> > in 2.3 I've missed?
> On Thu, Jun 25, 2009 at 3:04 PM, Dave Spurr <david.sp...@gmail.com> wrote:
>> Are you using a virtual machine for your dev env? If so make sure the
>> clock on your VM is set to the right time. I had a situation once where
>> I was editing files locally which were then mounted on my dev VM and
>> changes weren't showing in Rails.
>> -D
>> On 25/6/09 12:48, Francis Fish wrote:
>> > Hi guys,
>> > This is driving me nuts and restarting passenger makes no difference.
>> > If I rename the layout and change the name in the controller then it
>> > picks it up.
>> > CSS seems to suffer from the same problem.
>> > I'm convinced that my 2.2.2 project *just works*. Is there something
>> > in 2.3 I've missed?
Finally worked this out. I use emacs and it keeps old versions of the files
with handy ~1~, ~2~ extensions. For some reason these were being loaded
instead of the main file. I have a little shell alias that purges these
backup files and things start working if I run it.
Now I suppose I need to go dredging in the part that recognises file names
for HAML. Maybe not.
I had to go back to 2.3.2 because the hybrid wouldn't work with passenger.
At least I know what the problem is now. The give away was looking at error
messages and realising it was referring to the file with the ~ on the end.
> Finally worked this out. I use emacs and it keeps old versions of > the files with handy ~1~, ~2~ extensions. For some reason these were > being loaded instead of the main file. I have a little shell alias > that purges these backup files and things start working if I run it.
I've always wondered why text editors do this. If I want to keep the history of a file I'll use a source control, if not then don't litter my filesystem with "cruft".
Guess its a throwback to times before a simple `git init` created a repo for you right? :)
On Mon, Jun 29, 2009 at 3:21 PM, Caius Durling <ca...@caius.name> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1
> On 29 Jun 2009, at 15:17, Francis Fish wrote:
> > Finally worked this out. I use emacs and it keeps old versions of > > the files with handy ~1~, ~2~ extensions. For some reason these were > > being loaded instead of the main file. I have a little shell alias > > that purges these backup files and things start working if I run it.
> I've always wondered why text editors do this. If I want to keep the > history of a file I'll use a source control, if not then don't litter > my filesystem with "cruft".
> Guess its a throwback to times before a simple `git init` created a > repo for you right? :)
*sometimes*, very occasionally, it helps. Maybe once a year. Useful when editing config files too. But you're right about the other 99.9999%. I read somewhere there's an ubuntu util that creates a git repo for your /etc area and updates using a daemon whenever a file is changed, but not had a chance to check it - that would make it worth turning the option off.
I still have it turned on because it's a habit from my 20 years' coding. Probably *does* need a rethink.
> *sometimes*, very occasionally, it helps. Maybe once a year. Useful > when editing config files too. But you're right about the other > 99.9999%. I read somewhere there's an ubuntu util that creates a git > repo for your /etc area and updates using a daemon whenever a file > is changed, but not had a > chance to check it - that would make it worth turning the option off.
Ooh, I've done that manually. Didn't think to look if someone'd done a daemon for it already.
|
