VirtualTam's bookmarks

  1. A whole buncha' links with contradictory information on how to properly set up a mail server ;-)

    Disclaimer - My primary goal is to add proper Spamassassin (SA) filtering to an existing Postfix / Dovecot / roundcube installation, i.e.:

    • use SA as a milter (mail filter) to attribute a spam score to incoming mail
    • keep SA up-to-date
    • train SA with spam/ham from the users' virtual mailboxes
    • train SA according to user decisions (actual user or trained mail client with automatic/trained spam detection)

    Here we go!

    Most useful links; I stumbled upon them as soon as I knew what to look for:

    Official:

    Debian:

    CentOS:

    RHEL:

  2. And more generally, "emacs as a <language> IDE":

    • code completion
    • snippet / templates
    • project view
    • syntax checking
    • test harness utilities

    See also:

  3. item = Jenkins.instance.getItemByFullName(&quot;your-job-name-here&quot;)
    
    // THIS WILL REMOVE ALL BUILD HISTORY
    item.builds.each() { build -&gt;
      build.delete()
    }
    item.updateNextBuildNumber(1)
    
  4. TL;DR - Right Click on window title bar > More Actions > Special Applications Settings > Size and Position > Obey geometry restrictions > Choose Force and leave check mark to No.

    http://www.emacswiki.org/emacs/KdeMaximized https://bbs.archlinux.org/viewtopic.php?id=92115

  5. (global-set-key (kbd "C-c <left>") 'windmove-left) (global-set-key (kbd "C-c <right>") 'windmove-right) (global-set-key (kbd "C-c <up>") 'windmove-up) (global-set-key (kbd "C-c <down>") 'windmove-down)

  6. Tension / gauge calculator to design custom string sets

    Related threads:

  7. Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)

    I'm currently looking for more dev-friendly solutions, the key points being:

    • writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
    • parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
    • complete feature set!
      • we don't want to just run tests...
      • coverage reports (find dead/weak/untested code sections)
      • output formatting (JUnit-XML seems to be quite a common format out there)

    There seem to be 3 solutions in Python:

    • stock unittest + project-dependent customizations / test helpers
    • nosetests
    • py.test

    And 2 ways of gettings things done:

    • keeping things stock: no external dependency, project-specific implementation...
    • using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)

    Some links:

  8. electric-indent has been activated by default in emacs 24

    to disable it for Python: (add-hook 'python-mode-hook (lambda () (set (make-local-variable 'electric-indent-functions) (list (lambda (arg) 'no-indent)))))