On Sat, Nov 15, 2014 at 6:52 PM, grubernd <li...@mehrzweckraum.com> wrote: > hi.. > > i know, i have read > http://i3wm.org/i3status/manpage.html#_what_about_memory_usage_or_cpu_frequency > > i wonder how the author came to the conclusion of above sections. obviously > s/he has never worked with large image data in image-editing software where > making a minor change to your workflow or how your image layers are > structured can make the difference between just working on or sending your > machine into swap for 10 minutes or an hour with a single click. being able > to monitor your memory-usage by software is more than helpful, it makes the > difference between work or not being able to. I’d argue that you should disable swap entirely, so that the graphics application in question can detect an out of memory situation and react appropriately (by telling you about it, probably). If the app doesn’t work that way, maybe you can convince upstream to implement that behavior.
> > the +/- buffers/cache info from free is pretty much what others use and it > is the real deal. > > would be great if this would make it into i3status one day. See http://i3wm.org/i3status/manpage.html#_external_scripts_programs_with_i3status for how to add this to i3status with a simple wrapper script. The section you referred to is just about what is shipped in i3status itself. -- Best regards, Michael
