vadviktor

.host:/vmshared    /mnt/vmshared     fuse.vmhgfs-fuse allow_other,uid=1000,gid=1000,auto_unmount,defaults 0 0

xuhdev

# see https://www.topbug.net/blog/2013/04/14/install-and-use-gnu-command-line-tools-in-mac-os-x/

# core
brew install coreutils

# key commands
brew install binutils
brew install diffutils
brew install ed --default-names
brew install findutils --with-default-names

tonysneed

- Open Automator 
- File -> New -> Service 
- Change "Service Receives" to "files or folders" in "Finder" 
- Add a "Run Shell Script" action 
- Change "Pass input" to "as arguments" 
- Paste the following in the shell script box: open -n -b "com.microsoft.VSCode" --args "$*" 
- Save it as something like "Open in Visual Studio Code"

bbengfort

import networkx as nx
import graph_tool as gt



def get_prop_type(value, key=None):
    """
    Performs typing and value conversion for the graph_tool PropertyMap class.
    If a key is provided, it also ensures the key is in a format that can be

acamino

Shortcut — Action

• CTRL + A — Move to the beginning of the line
• CTRL + E — Move to the end of the line
• CTRL + [left arrow] — Move one word backward (on some systems this is ALT + B)
• CTRL + [right arrow] — Move one word forward (on some systems this is ALT + F)
• CTRL + U — (bash) Clear the characters on the line before the current cursor position
• CTRL + U —(zsh) If you're using the zsh, this will clear the entire line
• CTRL + K — Clear the characters on the line after the current cursor position
• ESC + [backspace] — Delete the word in front of the cursor

wojteklu

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

---

General rules

1. Follow standard conventions.
2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
3. Boy scout rule. Leave the campground cleaner than you found it.
4. Always find root cause. Always look for the root cause of a problem.

Design rules

manasthakur

Managing plugins in Vim: The basics

Let's say the plugin is at a GitHub URL https://github.com/manasthakur/foo. First get the plugin by either cloning it (git clone https://github.com/manasthakur.foo.git) or simply downloading it as a zip (from its GitHub page).

Adding a plugin in Vim is equivalent to adding the plugin's code properly into its runtimepath (includes the $HOME/.vim directory by default). For example, if the layout of a plugin foo is as follows:

foo/autoload/foo.vim
foo/plugin/foo.vim

csswizardry

Vim without NERD tree or CtrlP

I used to use NERD tree for quite a while, then switched to CtrlP for something a little more lightweight. My setup now includes zero file browser or tree view, and instead uses native Vim fuzzy search and auto-directory switching.

Fuzzy Search

There is a super sweet feature in Vim whereby you can fuzzy find your files using **/*, e.g.:

:vs **/*<partial file name><Tab>

jpickwell

This is based on the following: https://github.com/troyxmccall/dotfiles/blob/ae78ab87c861efe27aee7ede47cd0e61dac8fe22/.functions#L419-L442

I changed it to be a script, and fixed some issues related to handling of versions.

bradmontgomery

Copyright 2020 Brad Montgomery

Permission is hereby granted, free of charge, to any person obtaining a copy of this software 
and associated documentation files (the "Software"), to deal in the Software without restriction, 
including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, 
and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, 
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial 
portions of the Software.