aboutsummaryrefslogtreecommitdiff
path: root/sh/profile.d/visual.sh
Commit message (Collapse)AuthorAgeFilesLines
* Switch to using GNU Emacs on development machinesTom Ryder2019-01-011-2/+8
| | | | | | | | | | | | | | > Andromeda, by Perseus sav'd and wed, > Hanker'd each day to see the Gorgon's head: > Till o'er a fount he held it, bade her lean, > And mirror'd in the wave was safely seen > That death she liv'd by. > Let not thine eyes know > Any forbidden thing itself, although > It once should save as well as kill: but be > Its shadow upon life enough for thee. > > --Dante Gabriel Rossetti
* Quote EDITOR/VISUAL assignments for clarityTom Ryder2018-01-151-1/+1
| | | | | | | | | | | | | | | | | This appeases ShellCheck 0.4.7, which is fretting that I meant a command expansion. I didn't, but it seems a bit nicer to quote these anyway. In sh/profile.d/editor.sh line 4: EDITOR=ed ^-- SC2209: Use var=$(command) to assign output (or quote to assign string). In sh/profile.d/editor.sh line 22: EDITOR=ex ^-- SC2209: Use var=$(command) to assign output (or quote to assign string). In sh/profile.d/visual.sh line 2: VISUAL=vi ^-- SC2209: Use var=$(command) to assign output (or quote to assign string).
* Just use whichever vi(1) we need as VISUALTom Ryder2017-05-141-6/+2
| | | | | | | This avoids an unwanted situation on e.g. Debian minimal where the default Vi implementation is a stripped-down Vim that doesn't use vim(1) as a name, so stuff like sudoedit(8) breaks looking for it and falls back on EDITOR.
* Use env vars not shell funcs for vim checkTom Ryder2017-03-091-2/+6
| | | | | | Set EDITOR and VISUAL appropriately based on what's on the system. We can't assume ed(1) unfortunately, but ex(1) should be there.
* Arrange EDITOR/VISUAL in a more typical wayTom Ryder2016-08-181-0/+3