Closed mphojele closed 4 years ago
Have you tried adjusting impatient-mode-delay? That might be close to what you want. There's currently no "public" function to manually trigger an update, but imp--after-timeout is basically that.
I'll look into it, thank you On Sun, 22 Dec 2019, 20:45 Christopher Wellons, notifications@github.com wrote:
Have you tried adjusting impatient-mode-delay? That might be close to what you want. There's currently no "public" function to manually trigger an update, but imp--after-timeout is basically that.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/skeeto/impatient-mode/issues/23?email_source=notifications&email_token=AKSYGBETDNV47ADSFYQI7S3QZ6YWBA5CNFSM4J6JM25KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHPXHLY#issuecomment-568292271, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKSYGBH5OQSWVZCGKKGQADTQZ6YWBANCNFSM4J6JM25A .
Is it possible to set the amount of impatience?
I know simply calling
httpd-start
followed by its command to server the directory means i get a server that serves the actual files and i see changes as i save, which is at impatience level 0.However, enabling
impatient-mode
shoots the impatience level to a 100 because it servers the buffers and i see changes as i edit. What more can I wish for?How about having the impatience level at 50? It serves the buffers, however, I do not see changes as I edit, instead I have to do manual browser refreshes. I'm left with only the joy that I don't have to save the files.
Sorry for being so poetic, but I say this because I'm seeing astronomical numbers with regards to my RAM. maybe it's Firefox, and I don't know how to tweak it to not bunk so much resources. It was around over 1GB and I only had one window and tab open.