Skip to content

Commit b2561ff

Browse files
committed
Add writeup .txt for the tutorial assignment
A guide for adding Sublime Text access from the CLI is included in the writeup.
1 parent 4d0a4f6 commit b2561ff

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

HLimm_git_writeup.txt

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
Henry Limm
2+
3+
Git Version Control (Clinic Tutorial)
4+
5+
6+
7+
- user (GitHub): KLimit
8+
- tutorial repository: KLimit/git_test
9+
10+
- total time: ~4 hr
11+
12+
No errors to report; however, I did take the time to set up my CLI so that I
13+
was able to open files using Sublime Text 3 rather than VS Code (on Windows).
14+
Below is how I accomplished this:
15+
16+
- under C:\Users\<username>, create a .bash_profile file
17+
-- this is best done from a text editor -> Save as vs. in File Explorer
18+
19+
- paste the following into the .bash_profile:
20+
-- alias subl="/c/Program\ Files/Sublime\ Text\ 3/subl.exe -w"
21+
--- note the forward slashes are to escape the space; apostrophe (')
22+
within the string should also work (see below)
23+
--- also note the -w to make Git Bash wait for the file to close
24+
before resuming the CLI
25+
26+
- that should be all that's necessary
27+
28+
- confirm that .gitconfig contains the following code (this should happen
29+
during installation if you choose to use Sublime 3)
30+
-- [core]
31+
editor = "'c:/program files/sublime text 3/subl.exe' -w "
32+
33+
I'm not sure how popular Sublime is among students now, but I'm sure that
34+
someone might find it helpful to add this in an appendix or as a side note. It
35+
seems that other text editors like Atom are a bit more simply integrated just as
36+
VS Code is.

0 commit comments

Comments
 (0)