about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2018-11-30 16:39:27 -0800
committerKartik Agaram <vc@akkartik.com>2018-11-30 16:39:27 -0800
commit14da19a27204f77ea65ad66fe3fba6a60225f035 (patch)
tree127206649dcea12792387d270ad1bd431579fb28
parent8bf0c436ecdbbbbf07a2221702d35b323cc27f9c (diff)
downloadmu-14da19a27204f77ea65ad66fe3fba6a60225f035.tar.gz
4806
Drop a wildcard in my edit shortcuts that's getting confused between apps/crenshaw2-1.subx
and apps/crenshaw2-1b.subx. We're pretty much always using the full filename
(excluding .subx extension) anyway.
-rw-r--r--vimrc.vim4
1 files changed, 2 insertions, 2 deletions
diff --git a/vimrc.vim b/vimrc.vim
index 8bb5bbfe..1c85b643 100644
--- a/vimrc.vim
+++ b/vimrc.vim
@@ -72,9 +72,9 @@ endfunction
 
 function! SubxPath(arg)
   if a:arg =~ "^ex"
-    return "examples/" . a:arg . "*.subx"
+    return "examples/" . a:arg . ".subx"
   else
-    return "apps/" . a:arg . "*.subx"
+    return "apps/" . a:arg . ".subx"
   endif
 endfunction
 
DD; font-weight: bold } /* Literal.Number.Float */ .highlight .mh { color: #0000DD; font-weight: bold } /* Literal.Number.Hex */ .highlight .mi { color: #0000DD; font-weight: bold } /* Literal.Number.Integer */ .highlight .mo { color: #0000DD; font-weight: bold } /* Literal.Number.Oct */ .highlight .sa { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Affix */ .highlight .sb { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Backtick */ .highlight .sc { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Char */ .highlight .dl { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Delimiter */ .highlight .sd { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Doc */ .highlight .s2 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Double */ .highlight .se { color: #0044dd; background-color: #fff0f0 } /* Literal.String.Escape */ .highlight .sh { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Heredoc */ .highlight .si { color: #3333bb; background-color: #fff0f0 } /* Literal.String.Interpol */ .highlight .sx { color: #22bb22; background-color: #f0fff0 } /* Literal.String.Other */ .highlight .sr { color: #008800; background-color: #fff0ff } /* Literal.String.Regex */ .highlight .s1 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Single */ .highlight .ss { color: #aa6600; background-color: #fff0f0 } /* Literal.String.Symbol */ .highlight .bp { color: #003388 } /* Name.Builtin.Pseudo */ .highlight .fm { color: #0066bb; font-weight: bold } /* Name.Function.Magic */ .highlight .vc { color: #336699 } /* Name.Variable.Class */ .highlight .vg { color: #dd7700 } /* Name.Variable.Global */ .highlight .vi { color: #3333bb } /* Name.Variable.Instance */ .highlight .vm { color: #336699 } /* Name.Variable.Magic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
	<head>
		<title>Communication Guidelines</title>
		<link rel="stylesheet" href="/plain.css" />
		<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon" />
		<meta charset="utf-8" />
	</head>
	<body class="indent">
		<h1>Communication Guidelines</h1>
		<p><a href="/contact.html">A few ways to contact me</a></p>
		<p>
		These are some general recommendations that I believe make communicating with me, at least, easier and/or more effective, including communication conventions that make me happier.  Please note that what I prefer may not be what others prefer and shall not be treated as a general guideline for communications.
		</p>
		<ol>
			<li>Write a descriptive subject for emails.  Do not send emails with an empty subject or no subject header.  The subject should be give the receiver a brief idea of what the email is about.</li>
			<li>Send complete information.  When telling me something or requesting something, please provide complete background information, knowledge required, and other relevant context.  This prevents back-and-forth communication along the lines of ``and now I need to know ... but you didn't tell me that so can you please give that to me''.  Providing context defragments conversations which increases efficiency.</li>
			<li>When using instant messaging such as IRC, do not split one sentence into multiple messages.  Fragmentation reduces readability.</li>
			<li>Do not use excessive emojis.</li>
			<li>Be direct.  As the sender, do not use polite expressions like ``you did quite well in that presentation'' when in reality, the sender believes that the presentation is not ``quite well''.  Direct critique and suggestions are very welcome here.  Politeness is acceptable if it does not interfere with honest conveying of information.</li>
			<li><a href="./ask.html">Don't ask to ask.</a></li>
			<li>Use plain text email.  Both hard-wrapped and non-hard-wrapped emails are acceptable.  If you do hard-wrap, please wrap at 72 characters for English.  Chinese, if hard-wrapped, should be at 36 characters.  Non hard-wrapped emails should <a href="https://www.ietf.org/rfc/rfc3676.txt">specify format=flowed as per RFC3676</a>.</li>
			<li>Interweave the original message with the response when replying to an email and remove irrelevant parts (i.e. greetings, closings, signatures, etc.) of the quoted original email.</li>
		</ol>
		<p>
		Please note that <a href="./wechat.html">WeChat is not a preferred way of contacting me</a>.  <a href="/contact.html">Use these instead</a>.
		</p>
		<div id="footer">
			<hr />
			<p><a href="/">Andrew Yu's Website</a></p>
		</div>
	</body>
</html>