Situation: I'm using grunt + grunt-contrib-watch + grunt-contrib-compass. I use Compass to automatically generate my sprite. My .sass files are getting compiled every time I save, which is exactly what I want. But that means that my sprite is also getting regenerated every time I save, which was great at the beginnning but takes forever now that I've got about 30 images (+ #2x versions) that go into that sprite.
Question: Is there a way to stop Compass from regenerating the sprite every time I save? Maybe it could just regenerate it if there actually were some changes regarding the sprite.
Thanks for your help!
Compass should cache it by default, unless you use set force: true. Try running compass from the Terminal and see if the same happens.
The grunt-contrib-compass is just a thin wrapper around Compass.
Related
I recently started making music using GarageBand's MIDI software. I've made it up to a certain point, where losing all my progress would be disastrous.
Here's the issue I have:
When I go to File > Save/Save As or just cmd+S or cmd+shift+S, or Share > Export Song to Disk, instead of functioning and saving the file (I checked in Finder; last time I exited the app without saving due to this issue, the untitled garageband file disappeared) properly onto the app, it would either do nothing or give me the rainbow wheel of death for 10-20 seconds and then proceed to not function.
I've searched online for answers to this, and there were several (2) users I found that had the same problem. Their post either had no answer or the answer was unintuitive (such as always using a different, more complicated method to save, like messing around with the garageband files themselves everytime to save).
I'm looking for an answer to this issue that would result in slightly more convenient, one-time edits to the app / any software beneath that would fix this issue, if there are any. However, if the community has any alternate way to save the file right now, I would greatly appreciate it.
======
Also:
Since I'd assume most of the solutions would involve closing the app and then making edits, then reinstalling it, please tell me if I could just copy the notes (not the tracks) onto a text document and paste it into the new file after. I would prefer to save my music.
Try this . . .
First QUIT Garageband (yes you will lose unsaved work).
Find the Garageband folder where all the .BAND files are saved. Usually it is in Users -> Username -> Music -> Garageband.
Move older .band files into another folder (EG: "Garageband OLD")
Then start a new project (or open a project still in the Garageband folder).
Save and Save-As should now work.
It seems there is some sort of file limit for the Garageband folder. In my case the file limit is either 170 .band files or about 125GB.
I am currently using Garageband 10.3.5 on High Sierra.
I've written a program that generates an image via tkinter.Canvas and saves it. Now I'm updating this project to use FastAPI to let users hit my end-point and download this image.
I'm not trying to display the image on the server, just generate it in memory, save it to storage, then return that image.
Initial proof-of-concept tests work, but I cannot get this to work in Docker because no $DISPLAY is set. Unlike other questions I've seen, I'm not trying to display the image directly, just generate the image, save it, and return a file-path.
This is not a dupe of Tkinter setup on headless server. That question boils down to "how do I not run tkinter while on a server?" I still need tkinter, I just have no intention of displaying it.
I have also seen something about X11, but it seems like I'd need to know the server's environment in order to install X11, and I do not.
Is tkinter really not able to generate an image without $DISPLAY (even if I don't intend to display it)? If so, is there an alternative to tkinter I can use that can generate an image without needing a $DISPLAY? Am I totally misunderstanding a major part of how this works? It seems like I should be able to generate an image and save the bytes without needing all the things required for actual graphical rendering...
Using Pillow.Image and Pillow.ImageDraw instead of tkinter works for my scenario. (Credit goes to #acw1668)
My project only draws lines, circles, and polygons - all things that ImageDraw can do. The process of switching from one to the other was exceptionally straightforward, and Docker returns the ImageDraw/Image file with no issues!
I am currently working on Linux with tmux + vim.
What is the proper way to view log files, that each time recreated?
I am using Check as unit test framework for C, and after make check, log file recreated. Vim doesn't shows this changes, or maybe :set autoreload doesnt't work for me.
You can use the Vim-Timer plugin available in GitHub. This allows the user to set a time interval and the file is reloaded after that time interval. (Time interval is less than a second by default, but you can change it)
It is available at https://github.com/dahu/Vim-Timer
After installing the plugin, put the code in autoread_updater.vim into ~/.vimrc.
It works perfectly for autoread though there are minor bugs.
I made a small project in Meteor / Iron. There's almost no styling in it yet but a lot of JavaScript already coded. I would like to update the system to handle SCSS instead of LESS since it seems more adapted for this specific project.
I can't find anywhere how to do such thing, do you have any idea ? Do I have to do everything manually ?
According to the docs:
$ iron create myApp --css=scss
You could then dump everything but your .scss files into the new project.
Or you can manually swap out packages as mentioned above:
meteor remove less
meteor add fourseven:scss
As far as converting your LESS into SASS, this may help, but I dont think its going to be as automatic as you want.
I have nodejs v0.6.3 and coffeescript 1.1.3. on Archlinux.
I know they changed the way watch works in the latest release of coffeescript and that watch requires at least node v0.6.2.
In my case it only works once. After that when I save a file again, coffee does not take notice.
What could be the problem here?
There are a number of problems with fs.watch, which I've been actively discussing on both the Node and CoffeeScript issue trackers. One problem—likely the one you're encountering—is that some programs save changes not by writing directly to the existing file, but rather by writing to a temporary file and then mv-ing that file on top of the existing one. From fs.watch's perspective, this means that the watched file has been deleted, and changes to the new file will be ignored.
On the current CoffeeScript master, we try to work around this by re-watching the file each time a rename event is emitted. So please install that and let me know whether it solves your problem. If it doesn't, you should revert to using the older fs.watchFile API, either by downgrading to CoffeeScript 1.1.2 or by using a third-party tool like my own Jitter.