Martin Holt Juliussen martinhj

vim and project specific config

I've been in a few .php/.js-projects lately where it is not straight forward to use gf ("goto file"). Usually when the cursor in vim is above a filename I simply hit gf and it opens that file for reviewing/editing.

But in webdev land where I have been lately it is not untypically to do a reference to a file of sorts:
{% include '\_partials/main-menu' with {id: mainMenu} %}

It states the path _partials/main-menu, but the file that I want to investigate is craft/templates/_partials/main-menu.twig.

To gf my way to the right file I found that I could set path+=$PWD/craft/templates and set suffixesadd+=.twig

for file in src/file/path/images/common-name-*
  do
    git mv $file $(echo $file| sed 's/\(.*\)common-name.*/\1/')other-common-name$(echo $file | sed 's/.*common-name\(.*\)/\1/')
  done

	# EXPORT COMMAND FIRST
	export COMMAND="dd if=/dev/urandom of=secret.tar.bz2 bs=56724259 count=1 conv=notrunc"

	# THEN
	for ((n=1;n<8;n++)); do eval $COMMAND; done;

	// create and fill array of given size
	const arrayWithNumbers = Array(4).fill(null).map((u, i) => i) [0, 1, 2, 3]
	// or
	const newArrayWithNumbers = [...Array(4)].map((u, i) => i)

	// positive lookahead
	// ?=
	const lookaheadRegex = /something(?=\$)/ // match something at end of line, but not the end of line

	// positive lookbehind
	// ?<=
	const lookaheadRegex = /(?<=\^)something/ // match something at the start of line, but not the start of line

	// negative lookahead
	// ?!

	// From https://davidwalsh.name/javascript-tricks
	/**
	Those three dots made the task so much easier!

	Require Function Parameters
	Being able to set default values for function arguments was an awesome addition to JavaScript, but check out this trick for requiring values be passed for a given argument:
	*/

	const isRequired = () => { throw new Error('param is required'); };

	const linkPath = '/workingMode/distracted/aBit'
	const isDarkTheme = true

	const generateSearchQuery = (strings, linkExp, searchArgument = 'gaveUp') => {
	let searchQuery = '?search='
	const [,searchQueryArg ,] = strings
	const themeString = isDarkTheme ? 'dark' : 'light'

	if (searchQueryArg !== '') searchQuery = searchQueryArg
	return `/en-us${linkExp}${searchQuery}${searchArgument}?themeType=${themeString}`

	# from https://stackoverflow.com/questions/5163144/what-are-the-special-dollar-sign-shell-variables
	# Aslo see https://www.gnu.org/software/bash/manual/html_node/Special-Parameters.html

	$1# (, $2, $3 , ...) are the positional parameters.
	"$@" # is an array-like construct of all positional parameters, {$1, $2, $3 ...}.
	"$*" # is the IFS expansion of all positional parameters, $1 $2 $3 ....
	$# # is the number of positional parameters.
	$- # current options set for the shell.
	$$ # pid of the current shell (not subshell).
	$_ # most recent parameter (or the abs path of the command to start the current shell immediately after startup).