6 ms·
A multi-purpose EDITOR variable
- dmckeon 14y agoTo edit several files of one type in one call: #!/bin/bash case $1 in *_EDITMSG | *MERGE_MSG | *_TAGMSG) /usr/local/bin/vim "$@" ;; *.md | *.txt) /usr/local/bin/mmdc "$@" ;; *) /usr/local/bin/subl -w "$@" ;; esac
- deleted 14y ago[deleted]
- jasonm23 14y agoUse Emacs, then you don't need several not very good editors. /flamebait
- lokedhs 14y agoI was just about to post the same thing (mentioning emacsclient though). Does that make me a troll? :-)
- deleted 14y ago[deleted]
- jasonm23 14y agoapparently, not.
- jlgreco 14y agoFrankly I don't see the point with Vim either, or any other editor that is capable of some concept of modes. Why doesn't the author find sublime suitable for git commit messages?
- alecdbrooks 14y agoI would guess it has something to do with Vim having a console version and Sublime not. Commit messages are so short he probably just wants it to pop up in his shell, rather than in another window.
- dlitz 14y agoWith Emacs, you get a single not very good editor to rule them all! :P
- jasonm23 14y agosays the Vim guy.
- asveikau 14y agoDon't a lot of programs first check for program-specific EDITOR values? So if you want to change the one for git, set GIT_EDITOR? Seems a lot cleaner than trying to recognize the filename.
- mccolin 14y agoDo people not often use "git commit -m" for commit messages? Curious as to the common level of need to launch the full editor.
- obilgic 14y agoWriting descriptive commit messages with multiple lines.
- ams6110 14y ago$ commit -m 'This is > my long > multi-line message' Granted, if you really want to write a novel that gets inconvenient, but I try to keep commit message short and reference a story or bug id# for more details when necessary.
- ibotty 14y agoi know it was not your point, but pls use a blank line between title and body.
- pilgrim689 14y agodepends. for small commits, a one-liner suffices. For large commits, merge commits, etc., or for repos that require you to sign-off on the commit or whatnot, a one-liner followed by a blank line and then a nice paragraph or bullet-point list is necessary. "launching a full editor" is hardly a problem with emacsclient or vi[m]
- jordibunster 14y agoThe smaller the commit, the more likely that it needs a proper explanation of why it was made. When you find a commit from two years ago that changes a constant from -1 to -2, and the commit message says "constant change", or "bugfix in floobers" you're left with no context.
- deleted 14y ago[deleted]
- dubcanada 14y agoYour website font on Windows is just plain terrible looking. Regardless of that... I love this!
- dangrossman 14y agoDon't blame Windows for Chrome's terrible text rendering there. Firefox and IE don't mangle fonts the same way.
- drivebyacct2 14y agoDoes Chrome use a different rendering in Linux? It looks fine here and I don't really have issues with fonts. (Except Calibri, people need to stop using it. It looks bad as is, and it looks awful in Linux without a bunch of manual hacks)
- Evbn 14y agoNot sure about windows, but Chrome definitely renders differently between Mac and Linux-- which is why Google Drive Presentations are not cross-platform -- spacing between objects gets messed up when you switch.
- kaens 14y agoThis is not a multi-purpose EDITOR variable. This is using a dispatch script as $EDITOR.
- mooism2 14y agoGreat! Now, how do I get EDITOR (and PAGER, for that matter) on a remote system to refer to an editor on the system I'm sshing in from?
- kree10 14y agoTake a look at bcvi if your preferred local editor is vim: http://sshmenu.sourceforge.net/articles/bcvi/ http://sshmenu.sourceforge.net/articles/bcvi/