25 ms·

How to boost your Vim productivity

• deleted 11y ago
  [deleted]
• rav 11y ago
  In my 6 years of coding and writing LaTeX in Vim, I have found that the greatest boost to my Vim productivity is learning all about the vi and ex foundation of Vim. My Vim knowledge applies 100% to any default Vim installation on a modern distro, and my vimrc contains mostly trivial tweaks. This means using :normal and macros instead of :s for most of my search/replace actions; using H, M, L, {, } to navigate quickly in the lines visible on the screen, and using f/F/t/T/;/,/% to navigate quickly within a line. I would say that 98% of my autocomplete needs are fulfilled by token completion (:help i_CTRL-N) and line completion (:help i_CTRL-X_CTRL-L). I frequently use the command-line window (:help c_CTRL-F) and listing matching names (:help c_CTRL-D). I specifically don't have mappings that involve the leader key, and I don't use the Ctrl-P plugin or a package manager or anything like that -- I honestly don't think that mapping <Leader>w to :w<CR> will make me any more productive in Vim.
  • krat0sprakhar 11y ago
    > This means using :normal and macros instead of :s for most of my search/replace actions Interesting. Can you please elaborate more on this?
    • rav 11y ago
      Suppose a range of lines contains function calls in some programming language: i = foo(a, 42, 1) j = bar(b, c, 100, 2) # this is a comment (well, duh) bazbar(etc, 3) You want to edit the last parameter in each function call -- change it to 'hello'. I have two ways of approaching this: macros (interactive) or :norm (less interactive). 1. Put your cursor on the first byte in the first line, type qq to record a macro of your change, q to finish. Select the rest of the lines in visual line mode and type :'<,'>norm @q to run the macro on each of the remaining lines. 2. Select the lines in visual line mode and type, for instance, :'<,'>norm %F,ws'hello' This is the "non-interactive" version of the above since the macro keystrokes are given directly to :normal. Pro: ability to undo keystrokes unlike when recording a macro. Con: cannot actually see the effect of the keystrokes (but with practice, this is not a problem). (Note that colon in visual mode automatically inserts the :'<,'> so you only have to type :norm ...) I find the declarative nature of regexes/:s to be too restrictive -- I much prefer the operational nature of macros/:normal, since that lets me make the change I want directly, without me having to phrase the change as a regular expression. I could also use CTRL-A in normal mode to increment the last argument in each line: :'<,'>norm %b^A (where ^A is the literal, typed CTRL-V CTRL-A) I feel like a wizard whenever I use :normal in a non-trivial manner.
      • solarexplorer 11y ago
        Isn't :%s/.)/hello)/ simpler? Maybe that's because I know nothing about macros. Thanks for the explanation.
        • rav 11y ago
          Pardon, it might have been a trivial example. I managed to find a real-world example I encountered in February this year. The PAPI library has a utility program papi_avail which prints a table of supported performance counters. The lines may look like this: PAPI_VEC_SP 0x80000069 Yes Single precision vector/SIMD instructions PAPI_VEC_DP 0x8000006a Yes Double precision vector/SIMD instructions PAPI_REF_CYC 0x8000006b No Reference clock cycles For a course project, I wanted to turn this into a C-array like this: {PAPI_VEC_SP, "Single precision vector/SIMD instructions"}, {PAPI_VEC_DP, "Double precision vector/SIMD instructions"}, {PAPI_REF_CYC, "Reference clock cycles"}, Using :norm, this transformation can be achieved in the following way: :'<,'>norm I{^[eldedecw, "^[A"}, (where ^[ is a literal escape, typed CTRL-V ESC.) Anecdotally, it is faster for me to type up such a line than an equivalent regular expression, since I use vi normal mode commands much more than regular expressions.
          • solarexplorer 11y ago
            I would have piped this through awk, but this is probably better done with macros. Thanks for taking the time to elaborate. I will definitely give macros a try.
          • pestaa 11y ago
            I just spent minutes to parse that instruction. Mind blown. Thank you for this enlightenment.
            • rav 11y ago
              You need to know how dw, de, cw, ce relate to each other, when the cursor is on a token character vs. a whitespace character, and so on, in order for this to be truly useful -- but luckily, ordinary practice with those commands in Vim can lead to an efficient internal idea of how it works. "You get used to it, though. Your brain does the translating. I don't even see the code. All I see is blonde, brunette, redhead."
    • grimgrin 11y ago
      Another little "trick" for replacing: " search. cw (or cs, c whatever) to replace/fix. esc. n.n.n.n. vnoremap <silent> s //e<C-r>=&selection=='exclusive'?'+1':''<CR><CR> \:<C-u>call histdel('search',-1)<Bar>let @/=histget('search',-1)<CR>gv omap s :normal vs<CR> A really simple, dumb example: http://showterm.io/040c49ac158cdda15fbca http://showterm.io/040c49ac158cdda15fbca
      • rav 11y ago
        Can you explain what the mappings do? I usually use the asterisk to search for the token under the cursor, edit the sought token using cw and then n.n.n.n. to replace later occurrences. I don't see how the mapping makes this more efficient.
  • jessaustin 11y ago
    ...% to navigate quickly within a line. "%" works fine for moving around, but when I use it to edit it always surprises me, which direction it goes. I almost think vim is psychic, because "%" goes the wrong direction for me at least 80% of the time. There must be a deterministic rule governing this, but can anyone explain to me what it is?
    • rav 11y ago
      Find first brace to the right of the cursor (be either an opening or closing brace) and jump to the matching one. If the cursor is at the beginning of a line of matched parentheses, % will go to the closing parenthesis of the first group, as in my example in a cousin comment.
      • jessaustin 11y ago
        Thanks for this! My mental model of this was really wrong.
  • dasil003 11y ago
    > I specifically don't have mappings that involve the leader key, and I don't use the Ctrl-P plugin or a package manager or anything like that -- I honestly don't think that mapping <Leader>w to :w<CR> will make me any more productive in Vim. I'm not as much of a purist, but that line jumped out at me too. For me, the attraction of vim is primarily in raw out-of-the-box editing power and ubiquity. Relying on custom binds for basic actions really hurts the ubiquity half of the equation. And really is :w<CR> where one wastes time in vim? If I wanted to customize everything I'd probably switch to emacs. Still, it's interesting to see how many different ways vim can be optimized according to individual workflows.
    • erikb 11y ago
      While all of that is correct, it's also the core of vim philosophy that using 2 key strokes instead of 3 is what speeds you up. That said I also haven't used too fancy configuration or mapping or plugins in vim yet because I fear I don't have them when I ssh into another system, which happens quite often. But I have to say that I use a few aliases in git and that speeds me up a lot, as long as I stay on my system.
  • rifung 11y ago
    Wow I have only been using H and L, and only because of you have I come to know M, {, and }. Thank you! But would you mind giving an explanation as to what the other things you listed do (f/F/t/T/;/,)? From just playing with them, it seems like f goes to the next character that you type and F does the same but backwards. t/T does the same but instead of going to the character it goes one before/after. I can't figure out what , and ; are for though..
    • rav 11y ago
      They are documented in :help left-right-motions, which you can also read at http://vimdoc.sourceforge.net/htmldoc/motion.html#left-right-motions http://vimdoc.sourceforge.net/htmldoc/motion.html#left-right.... fx moves the cursor to the next occurrence of x, and semicolon repeats the search. To repeat the search in the opposite direction, use comma. 4tx moves the cursor right before the 4th occurrence of x right of the cursor in the line. F and T move backwards instead of forwards; in that case, semicolon continues moving backwards and comma moves forwards (similar to / ? n N). It takes a while to get used to, but it has made me much more efficient compared to when I just pressed wwwww or eeeee or bbbb to get where I wanted in a line.
      • rifung 11y ago
        Oh my god this is amazing. Thank you!
      • aidos 11y ago
        I also make liberal use of '/' to get around. Sometimes the bit you want is a line or two down so 't' doesn't quite cut it. I use t / f a lot when cutting things, though there's probably a better way (from the article, I just discovered gn to visually select the next item matching the previous search). eg, I might have a name that I want to replace in a couple of spots so I find it easy to do something like: /AIDOS<CR>cfSNEWNAME<ESC>n.n.n. It's generally when it's a bit less calculated. If I knew I was replacing a load of stuff I'd use :%s/AIDOS/NEWNAME/gc
  • Rainymood 11y ago
    when I learned about f and F a whole new world opened up for me. It never ceases to amaze me how amazing vim is. Another quick thing I recently learned (yes, novice vim user here) is stuff like this \includegraphics{test.png} if you stand inside the curly brackets and type ciB (change in Brackets) you get this \includegraphics{} with your cursor active inside the brackets, just awesome ..
    • bgilroy26 11y ago
      TIMTOWTDI: ci{ does the same (I think of "B" as beginning of a Word [including punctuation], so it would confuse me to use the "B" meaning braces)
      • chestervonwinch 11y ago
        nice. I was wondering how one would accomplish the same with parens, i.e. ci(. Why does this work? It doesn't seem to match the usual building of commands. I mean this obviously isn't c command followed by i command followed by paren. Is it just special?
        • bgilroy26 11y ago
          I don't know if I am understanding your question correctly. I read 'ci(' as change what's inside parents. I read 'ci{' as change inside braces. 'ca(' and 'ca{' grab the parents and the braces as well. ========================= These combinations work for (d)elete as well. If your cursor is over the 4th letter of a 6 letter word, 'dw' will delete to the end of the word. 'diw' on the other hand will delete the whole word. (I've never tried 'daw' although I know 'da(' works)
          • chestervonwinch 11y ago
            right. I guess what I meant was 'c' and 'd' are usually followed by movements, so stuff like 'dt)' makes sense to me. 'i' on the other hand is not a movement, so the behavior of 'di)' was surprising to me. It's because 'iw', 'aw', and the like are commands of their own when an operator like 'c' or 'd' precedes [1]. So 'di)' is interpreted as 'd' followed by the 'i)' command (if I'm interpreting it correctly!), not as 'd' followed by 'i' followed by ')', which is nonsense. I hope that was clear - just trying to understand vim better :) [1]: http://vimdoc.sourceforge.net/htmldoc/motion.html#text-objects http://vimdoc.sourceforge.net/htmldoc/motion.html#text-objec...
• joelthelion 11y ago
  Why don't people seem to use the F keys? I have mappings for very frequent functions on F1-F5, and it really helps: map <F1> <Esc>:w<CR>| "Fast save imap <F1> <Esc>:w<CR>| "Fast save map <F2> :make<Up><CR>| "Fast compile map <F3> :bn<CR> map <S-F3> :bp<CR> " Same mapping for gnome-terminal ( see http://stackoverflow.com/q/12813126/164171 ) map ^[O1;2R :bp<CR> map <F4> :bd<CR>| "Close buffer map <F5> :cnext<cr> map <S-F5> :cprev<cr> imap <F5> <Esc>:cnext<cr> imap <S-F5> <Esc>:cprev<cr>
  • andrewstuart2 11y ago
    One of my favorite bits for saving my own butt: commit more. "Function to commit. function! GitCommit () execute 'write' let message = input('Enter commit message: ') execute '!git add ' . bufname('%') . ' && git commit -m ''' . message . ''';' endfunction imap <F7> <Esc>:call GitCommit()<CR> map <F7> <Esc>:call GitCommit()<CR>
    • thekemkid 11y ago
      OMG, I need to add this to my .vimrc. Thanks :D
    • leephillips 11y ago
      Have you tried fugitive (a vim wrapper around git)?
  • shmerl 11y ago
    I map a few of them: " Filesystem browser map <F2> :Explore<CR> " Show whitespace set listchars=eol:↵,tab:>·,trail:~,extends:>,precedes:<,space:␣ map <F4> :set list!<CR>
  • iovar 11y ago
    I'd guess, for the same reason I use Ctrl-[ instead of the Esc key. F keys put you out of the home row (at least in full size keyboards).
• andrewstuart2 11y ago
  I'm all for bending your text editor to your will, but a few of these tips gloss over the core of vim: the shortcut language it offers and the composability of its parts of speech [1]. For example, remapping the paste key to paste + move to end is cool, but `ppppp` to paste 5 times circumvents vim's killer repetition. Want to paste 100 copies? (hopefully you do this rarely). Just type `100p` and you're done. I won't bother typing out the obvious sequence of repeated `p` presses, but you get the drift. Also, remapping v to progressively select larger surrounding text objects will keep you from learning that you can perform any action on the 3rd parent curly braces by following the action with the text object `3a{` or `3a}`. Select it: `v3a{`, delete it: `d3a{`, comment it out `gc3a{` ([2]), whatever. If there's an action in vim you can perform it on a text object which can usually start with some count. I really do mean language, too. When I'm using vim, I feel a lot more like I'm communicating with my computer than trying to figure out how to do what I want to do. The actions are there: delete, change, select. The direct objects are there: braces, this line, line number N, end of this word, the next character C, this paragraph. The prepositions are there: inside, outside, up to (inclusive, exclusive). Heck, the sensible defaults feel a whole lot like the "understood" words that you can leave out of sentences. Instead of "navigate to line 30", you can just use the shortcut for "line 30" (30G) and be done. One of my favorite things about vim is the number of times I've literally been surprised that vim didn't read my mind and go where I was looking. Once you're familiar with the different pieces, it's so good that you might expect it to read your mind. </almost-blog-post> [1] http://ferd.ca/vim-and-composability.html http://ferd.ca/vim-and-composability.html [2] https://github.com/tpope/vim-commentary https://github.com/tpope/vim-commentary
  • rav 11y ago
    > I really do mean language, too. When I'm using vim, I feel a lot more like I'm communicating with my computer than trying to figure out how to do what I want to do. I tell people learning Vim or Emacs that they should treat it like learning a new programming language -- a programming language for text manipulation. (In particular, don't attempt a first project in C++ while writing your first report in LaTeX, both in Vim for the first time -- it will not be a pleasant experience!)
• shmerl 11y ago
  Lately I use neovim, because it allows using 24 bit color themes in the terminal.
  • INTPnerd 11y ago
    So neovim is usable now? Do you run into many problems with it?
    • EduardoBautista 11y ago
      I have been using it for months without any issues. It is actually a bit faster than regular vim.
    • shmerl 11y ago
      So far the only issue was some slowness when it uses xsel over ssh. I don't think it should take that long because of network alone. Otherwise - it's very good.
    • meunier 11y ago
      The only thing I've noticed is that I can't get italics in the terminal.
  • SeoxyS 11y ago
    How's the plugin situation these days? Will an existing (pathogen-powered) configuration work pretty well with neovim these days?
• grondilu 11y ago
  With bash, if 'fg' is too long to type you can just type '%'.
  • arc_of_descent 11y ago
    I use 'fg' a lot. Thanks for the '%' tip. Now to practice and grow some memory muscles!
• orthecreedence 11y ago
  This was great even just for the <Leader>p "+p mapping. I do this all the time ("+p). It's weird because I tend to go through waves of realizing "Oh! I can just remap that!" I feel like I have fairly good vim skills but somehow always forget I can keep making it more efficient than it already is. Thanks for the reminder =].
  • ThrustVectoring 11y ago
    I've got vim set up to use the system clipboard automatically. Want to visit a URL in a readme file? yiW, tab over to chrome (with vimium), hit P to open it in a new tab. Want to add a URL to documentation? yy it from chrome, tab to terminal, p it in.
• Veritaas 11y ago
  The most productive mapping ever: imap jj <ESC>. No more having to reach for the escape key.
  • zhengyi13 11y ago
    ICBW, but I believe Ctrl-[ is already available, and works the same. For me, having remapped Capslock to Ctrl, this is a dead simple way of hitting Esc without going as far off homerow.
    • leephillips 11y ago
      I had jk mapped for a long time and thought it was safe. Then one day I actually had to type it as text, and it took me a moment to figure out what was wrong. I'm retraining myself to use ^[ now.
      • isbadawi 11y ago
        I don't think the speed hit you take when you actually have to type 'jk' should be a dealbreaker. It rarely comes up, and when it does, you can use e.g. '<C-v>j<C-v>k' or 'jjkak'.
  • positr0n 11y ago
    Even better: imap jk <ESC> imap kj <ESC> I just hit both and j at the same time with my pointer and index fingers so it's essentially one keystroke.
    • illamint 11y ago
      `kj` has worked really well for me (except, actually, when trying to write a blog post about a recent trip to Reykjavik, but that's the one time it's bitten me versus the shitton of time it's saved). I also have `zkj` mapped to `<ESC>:w<CR>` to save AND exit insert mode.
    • thomasahle 11y ago
      How does this work? What if you are in insert mode and actually want to type j or k?
• gfodor 11y ago
  This is great. One thing the author should do is remap enter to something better than "jump to end of file." I remapped mine to ":w<CR>" to save the current file, and it's stuck.
• INTPnerd 11y ago
  This is one of the best "how to boost you Vim productivity" articles I have ever seen. It really gets to the heart of the types of customizations that a lot of people don't consider that make a massive difference.
• yramagicman 11y ago
  Does anyone have any advice on bindings to change split size? Ctrl-w + and Ctrl-w - just don't work well, and my current configuration shadows Ctrl-a, which I really would like to avoid.
  • rav 11y ago
    I rarely resize windows, but when I do, I set mouse=a and use the mouse to drag the window borders around. There's also CTRL-W _ (underscore) to maximize the current window and CTRL-W = to make window sizes equal.
    • yramagicman 11y ago
      I'm in the same boat, rarely re-sizing windows, and I'd do the same thing, but I use Tmux and terminal Vim and using the mouse there just doesn't work in my terminal emulator. (I use st[0] on Linux. It probably would work in iTerm on Mac, but I haven't tried.) It also may not work due to Tmux being configured with mouse support. [0] http://st.suckless.org/ http://st.suckless.org/
    • yramagicman 11y ago
      Also, did you know that Ctrl-w | maximizes the a window horizontally? So if you have splits open above and beside you ctlr-w _ ctrl-w | will maximize your current split. immediately maps this to ctrl-w m
      • ta0967 11y ago
        yes i did, having read the manual. :) there's also `:on[ly]` (i have `set hidden` in my .vimrc)
  • ta0967 11y ago
    ^W20+ - increase the current window height by 20 lines ^W20> - increase the current window width by 20 columns :he ctrl-w edit: typo
    • 11y ago
• blueblob 11y ago
  A few of these are good suggestions but I can't live without C-v, whether I am already in visual mode or not. Block selection may not be used that frequently but when it is, it's a lifesaver.
  • yramagicman 11y ago
    I use block selection so often that I've switched the mappings in my vimrc. I have v mapped to visual-block selection and ctrl-v mapped to visual selection. It's very rare that I miss normal visual mode as I use block and line selection more than anything.
• erikb 11y ago
  It is a long long time ago that someone taught me something really new about vim and used plugins that are not just fancy (looking at most status line plugins or nerdtree) but actually seem to improve productivity in a vim-ish sense. Kudos!
  • pyre 11y ago
    python-mode or jshint2.vim? I don't think that they are "just fancy. Bringing linting into the editing window is more helpful (to me personally at least) than having a separate process running with it. (Note: I turn rope off in python-mode because it's horribly inefficient, and sometimes causes Vim to delay reacting to user input)
• clinta 11y ago
  I disliked the part about setting up Vim on servers. Do you really want to be adding all the dependencies for your editor on every server? I'm an advocate of using the netrw plugin to edit over ssh directly and avoiding logging into servers when not necessary. vim scp://host//etc/whatever
  • sheerun 11y ago
    Plugins aren't installed until you call :PlugInstall You can also use .nvimrc instead .vimrc, so only nvim instance on server gets plugins.
• yramagicman 11y ago
  I have hacked my tabline to be a list of my open buffers. It still functions as a tabline, for those of you who use tabs, but it's kinda nice to see all my open buffers in a nice list across the top of my screen. https://github.com/yramagicman/dotfiles/blob/master/.vim/after/plugin/tabline.vim https://github.com/yramagicman/dotfiles/blob/master/.vim/aft...
  • graywh 11y ago
    See also: bufexplorer, MiniBufExplorer, buftabs
• bliti 11y ago
  Very useful, thank you. I'm spending more and more time using Vim through ssh and trying to re-learn as much as I can.
• critium 11y ago
  Learning that makeprg can be anything (even a script) made a huge difference to me. That and errfmt means I dont need to leave vim to compile or lint
• floatboth 11y ago
  The zsh Ctrl+Z binding is brilliant! The Space and Ctrl+Space thing is interesting, but not interesting enough for me to switch (from , and Ctrl+q – with Ctrl being on Caps Lock).
• ortuna 11y ago
  You may also like spacemacs. They've got a pretty nice <SPACE> + a lot of keys binding system. https://github.com/syl20bnr/spacemacs https://github.com/syl20bnr/spacemacs
• deleted 11y ago
  [deleted]
• dyates 11y ago
  This post has some valuable tips (I'm probably going to try out <Space> as a leader), but one or two near the start rub me the wrong way in terms of how I use vim and how it's my impression that it's intended to be used. >It seems like vvv is slower than vp but in practice I don’t need to think beforehand what to select, and what key combination to use. The way I've always used vim and always thought it was intended to be used is that you do think beforehand. You sit at your editor, think about what changes you want to make, and then key in a set of precision commands in vim-editing-language and it happens. >This way v replaces viw, vaw, vi", va", vi(, va(, vi[, va[, vi{, va{, vip, vap, vit, vat, ... you get the idea. I kind of like the precision of having all of those different things, and of course the option of using them for more than just visual select but also change, delete, and so on. Although I suppose this doesn't remove any of those keymappings, I must protest remapping Ctrl+v: I can't even use an editor without block select. I imagine there's a plugin (or even builtin feature) that at least generalises "s, (s , [s, tags and things of that sort though. >Stop that stupid window from popping up: >map q: :q I know it's a weird and irritating thing to have that window pop up when you meant to quit, but it's actually a very neat interface: a whole vim buffer for recomposing commands and your command history for later execution (almost acme-like). Give the poor guy a chance. As a counterpoint to what I've pointed out above, I'd like to recommend Drew Neil's [Practical Vim](http://www.amazon.com/Practical-Vim-Thought-Pragmatic-Programmers/dp/1934356980 http://www.amazon.com/Practical-Vim-Thought-Pragmatic-Progra...) to anyone who hasn't read it already. It's got a lot of great content, and really goes a long way to explain vim's quirks and methods of doing things. One of the useful tips I learnt from that was the ex command "normal", which allows you to execute a string of normal mode commands over a range of lines. So, for example, you can append a semicolon to each line in a visual selection by entering :'<,'>%normal A; A small thing, but one that I've used a lot since learning about it.
  • kweinber 11y ago
    +100 for Practical Vim... Hands down the best vim guide. After 10 years of kinda-knowing-vim, that book changed how I use vim entirely.
• roel_v 11y ago
  Step 1 for those who really want to boost productivity (but let's be honest, most of us don't!): forget about all those plugins that are time sinks to configure and integrate with each other, about obscure tweaks that take half a day to get right, and about elaborate .vimrc's that take you so far away from 'standard' that you're crippled without them. Stick to a fairly basic standard install and a .vimrc of 50 lines, tops. I've been using vim for 15+ years now, since late 1990's. I use viemu in Visual Studio and I've written code in 10+ languages in vim. I've written non-trivial vimscripts and integration tools with other parts of my workflows over the years. I love how comfortable it feels, and I feel crippled when I have to use a 'normal' editor; like walking with a little pebble in your shoe - not a big a deal enough to prevent you from doing anything you could otherwise, but still damn uncomfortable. With that said, I'm not convinced that I've actually saved time with it. I shudder if I think of the many man-days I spend 10 years ago on getting this and that plugin working, tweaking settings and keybindings for things I use twice a month tops and automating things that I could have done manually 10 times faster. It's not like regular editors are that much slower to use. It felt like throwing off a yoke when I dumped all those plugins so that I could focus on writing software, instead of tweaking the editor so that I could write programs with a few keystrokes. So yeah, that was gramps' advice I guess...
  • Legion 11y ago
    > and about elaborate .vimrc's that take you so far away from 'standard' that you're crippled without them. Stick to a fairly basic standard install and a .vimrc of 50 lines, tops. I think this is terrible advice. While it is true that one should avoid getting lost down the plugin rabbit hole, for many of us, the whole point of Vim is that it is a configurable, composable editor. As for being "cripped" without my vimrc, well, moving tiny text files around is pretty much a solved problem at this point. And as a developer, I'd prefer to optimize my 99.9% of the time environment, and not worry about the .1% of the time I'm away from it. I do, however, recommend that your vimrc is something you should build up over time, understanding what you are putting into it, rather than grabbing some big off-the-shelf framework and using it without understanding what is going on.
  • bch 11y ago
    +1 for the sentiment (which I share). I've done major swaps between Emacs and (n)vi over the years (currently all vi all the time now, but if you caught me last year, I was ~6 years into my Emacs phase...) -- anyway: the fussing and portability is what kept me from developing custom elisp scripts that I couldn't be guaranteed to have sitting down at every computer, and what now keeps me in nvi, and my nvi usage pretty "vanilla". It's not clear to me if its only the fear of getting caught w/o a custom environment is what's keeping me from developing that environment, but regardless, my env is vanilla. Edit: typos
• mastensg 11y ago
  Here is a way to do the Ctrl-Z trick in Bash: https://gist.github.com/mastensg/6d9030e25699c2eed5c4 https://gist.github.com/mastensg/6d9030e25699c2eed5c4
  • kokonotu 11y ago
    Thanks! I am looking for this
• deleted 11y ago
  [deleted]