Comments for Wrong Side of Memphis

Comment on Vim as IDE. Are you getting the wrong parts? by Jaime Buelta

Jaime Buelta — Wed, 19 Jun 2013 07:15:21 +0000

Hi Rob: If you're referring to this (that I put as example of what NOT not do), I don't know what plugins are being used there. My Vim configuration is pretty minimalistic, I use Command-T to move to files, Syntastic to check syntax and errors, and minibuffexp to keep track of opened buffers (I use it less these days, anyway, I may remove it). That's it from plugin point of view. I have a couple of settings on .vimrc, like remapping cursors (as I navigate through hjkl) to move lines and characters, highlighting characters over 80 in a line, setting stuff like tabs and so, and removing trailing spaces on save. (I've also removed your duplicated comment)

Comment on Vim as IDE. Are you getting the wrong parts? by Rob

Rob — Tue, 18 Jun 2013 20:03:13 +0000

Hello, I liked your vim configuration. I’m new to VIM. Would it be possible for you to post your vimrc or a least post the sections that make these plugins work with in Vim. Thank you in advance.

Comment on Vim as IDE. Are you getting the wrong parts? by Jaime Buelta

Jaime Buelta — Tue, 18 Jun 2013 09:48:47 +0000

I know fugitive. and it’s an awesome tool. But I still prefer the CLI for git. I use the command line for lots of stuff, so it fits quite well my workflow…

Comment on Vim as IDE. Are you getting the wrong parts? by ibizaman

ibizaman — Tue, 18 Jun 2013 08:55:11 +0000

“I use other tools for things like source control”
Let me introduce you to fugitive “https://github.com/tpope/vim-fugitive”

Comment on Vim speed is not really the point by Vim as IDE. Are you getting the wrong parts? | Wrong Side of Memphis

Vim as IDE. Are you getting the wrong parts? | Wrong Side of Memphis — Tue, 18 Jun 2013 07:30:21 +0000

[…] with a quick command. It is not just about using hjkl to move around and having an insert mode. It’s about being precise. It is difficult at first, because you can’t simply discover what are the available options, […]

Comment on I once was a non-tech entrepreneur by These are the times of miracle and wonder | Wrong Side of Memphis

These are the times of miracle and wonder | Wrong Side of Memphis — Mon, 17 Jun 2013 08:01:33 +0000

[…] that, I spend a few years without working as developer, but when I came back, it looked like I missed stuff. Like how incredibly easier to use have Linux […]

Comment on ffind: a sane replacement for command line file search by insane

insane — Mon, 10 Jun 2013 10:58:51 +0000

Just use an alias

Comment on ffind: a sane replacement for command line file search by Elias

Elias — Sun, 09 Jun 2013 19:26:19 +0000

You might want to avoid hard-coding VT102 colour sequences. Those will make a mess out of any terminal types that use different sequences.

The proper way to do it is to use terminfo. I don’t know Python, but googling a bit revealed this which seems to do what you need: http://code.activestate.com/recipes/475116-using-terminfo-for-portable-color-output-cursor-co/

Comment on ffind: a sane replacement for command line file search by James P (@thegidster)

James P (@thegidster) — Sun, 09 Jun 2013 19:11:51 +0000

Nice, I too use find a lot with my search term surrounded by wildcards

Comment on ffind: a sane replacement for command line file search by Joe Siponen

Joe Siponen — Sun, 09 Jun 2013 15:45:50 +0000

But since you seem to like ‘ack’ as tool I would also like to recommend the “-g” option which seems to exactly what this ffind tool is capable of:

-g REGEX Same as -f, but only print files matching REGEX

So, looking for a file named ffind.py:

ack -g “ffind\.py”

And, you could also restrict ack to look *only* for python-files that includes ffind.py in its name (as the above could, for instance, also return a java-file named “ffind.py.java”):

ack -g “ffind\.py” –py