CAFxX

📂 Persistent "pipes" in Linux

In a project I'm working on I ran into the requirement of having some sort of persistent FIFO buffer or pipe in Linux, i.e. something file-like that could accept writes from a process and persist it to disk until a second process reads (and acknowledges) it. The persistence should be both across process restarts as well as OS restarts.

AFAICT unfortunately in the Linux world such a primitive does not exist (named pipes/FIFOs do not persist

igalic

" Filename:      /etc/vim/vimrc
" Purpose:       configuration file for vim
" Authors:       grml-team (grml.org), (c) Michael Prokop <[email protected]>
" Bug-Reports:   see http://grml.org/bugs/
" License:       This file is licensed under the GPL v2.
""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

" All system-wide defaults are set in $VIMRUNTIME/debian.vim (usually just
" /usr/share/vim/vimcurrent/debian.vim) and sourced by the call to :runtime you
" can find below.  If you wish to change any of those settings, you should do it

mholt

package interfaces

import (
	"bufio"
	"crypto/elliptic"
	"crypto/tls"
	"database/sql/driver"
	"debug/dwarf"
	"encoding/xml"
	"fmt"

daryltucker

# I have my own logging setup and had a hard time disabling console output in Flask. 

    app.logger.disabled = True
    log = logging.getLogger('werkzeug')
    log.disabled = True
    
# New, 2022 Method:

    logging.getLogger('werkzeug').disabled = True

Roguelazer

try:
    import readline
except ImportError:
    pass
else:
    import itertools
    import rlcompleter
    import re
    import os
    import atexit

knu

require 'active_record'

module ActiveRecord::ConnectionAdapters
  class ColumnDefinition
    module CharsetSupport
      attr_accessor :charset, :collation
    end

    prepend CharsetSupport
  end

martijnvermaat

SSH agent forwarding and screen

When connecting to a remote server via SSH it is often convenient to use SSH agent forwarding so that you don't need a separate keypair on that server for connecting to further servers.

This is enabled by adding the

ForwardAgent yes

option to any of your Host entries in ~/.ssh/config (or alternatively with the -A option). Don't set this option in a wildcard Host * section since any user on the remote server that can bypass file permissions can now als use keys loaded in your SSH agent. So only use this with hosts you trust.

dypsilon

Frontend Development

Attention: the list was moved to

https://github.com/dypsilon/frontend-dev-bookmarks

This page is not maintained anymore, please update your bookmarks.

---

datagrok

Ideas for improvements to git log --graph

I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.

Make the graph for --topo-order less wiggly

Imagine a long-running development branch periodically merges from master. The git log --graph --all --topo-order is not as simple as it could be, as of git version 1.7.10.4.

It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.

matthewp

(function() {
  "use strict";

  Object.defineProperty(HTMLLinkElement.prototype, 'template', {
    get: function() {
      if(!/template/i.test(this.rel)) {
        return "";
      }

      var req = new XMLHttpRequest();