Live data from Hacker News

Poll: Which is your primary text editor?

news.ycombinator.com

141–150 of 163 posts

Re: Poll: Which is your primary text editor?

#141
post #62

No pico/nano love? Just kidding, I've only used it in dire emergencies too.

Nano is my preference for a linux editor. It is simple, it stays out of my way, there's nothing to memorize, there's no Java, and the syntax highlighting is decent.

When I worked at Google, I did all my coding in a custom version of nano which I'd hacked up to show an 80-column marker.

Re: Poll: Which is your primary text editor?

#142
post #89

Earlier quoted context omitted.

The geographical interpretation is strange. Why would you think Sublime would be relatively more prevalent than vi/emacs in SV? (Also don't forget it's coffee time in Europe)

> The geographical interpretation is strange. Logically, you'd be right that it wouldn't make much sense. However geographical trends like that do happen. eg SLES tends to have more traction in Europe than in the US (where RHEL is king of the enterprise space). Opera is more widely used in Europe and some eastern blocks than it is in the States. Apple hardware has a lower foothold in Europe than in America. And so on…

Sure they happen. But what is the basis for assuming so so matter-of-factly in this case? If you ask me I'd expect SV to have higher vim/emacs penetration since it's been tech central since before the invention of the terminal.

Re: Poll: Which is your primary text editor?

#143
Geany. We need something better than Syntax Highlighting. Something along the lines of the original Literate Programming. At least different fonts and styles for different syntax elements. Each package or multi-file module should have it's own background texture.

If you've got time and money to spare, and want to improve the editor you produce (not just use) then learn from the $300 SlickEdit editor. It does a lot of things right. And there's a go package for it.

Re: Poll: Which is your primary text editor?

#144
post #91

Earlier quoted context omitted.

I wouldn't have said so. Even ignoring the fact that it's a GUI app, it's also mouse driven. And the "CLI" aspect of Acme is really just a novel way of implementing shortcuts and macros, but since those functions are non-interactive, it's not really behaving like a command line. At risk of nitpcking, I think the "other CLI" option should have read "other console based" (that is, unless they were expecting people to a…

I don't understand what you mean with the CLI aspect of acme. Could you elaborate? But re:"other cli" I agree: even ed counts as console-based, not CLI (which would be sed, cat, maybe awk and echo... not fun, but of course real programmers use butterflies)

With Acme, any piece of text can be executed as a command with a (IIRC) middle mouse button click.

So in one pane on Acme, you can have the following written down:

    ls ~/dev
    uptime
and middle clicking uptime or highlighting and then middle clicking ls ~/dev would literally run those commands and return the output in a new Acme pane (you can even go a step further and have commands inside comments in your source code - as it's all just text to Acme).

What's more, the File / Save menus are just a text pane that you can edit, delete and add text to. So Acme follows some of the paradigms of working with the command line in terms of the application being controlled by text rather than hotkeys and widgets. But essentially it's still a mouse-driven application.

Also, I up-voted you just for the subtly of the XKCD reference (usually people just drop the URL with much thought of adding their own wit to the conversation). Nicely done :)

Re: Poll: Which is your primary text editor?

#145
post #89

Earlier quoted context omitted.

> The geographical interpretation is strange. Logically, you'd be right that it wouldn't make much sense. However geographical trends like that do happen. eg SLES tends to have more traction in Europe than in the US (where RHEL is king of the enterprise space). Opera is more widely used in Europe and some eastern blocks than it is in the States. Apple hardware has a lower foothold in Europe than in America. And so on…

Sure they happen. But what is the basis for assuming so so matter-of-factly in this case ? If you ask me I'd expect SV to have higher vim/emacs penetration since it's been tech central since before the invention of the terminal.

> Sure they happen. But what is the basis for assuming so so matter-of-factly in this case?

I can't help you there as I wasn't the one that made that comment.

> If you ask me I'd expect SV to have higher vim/emacs penetration since it's been tech central since before the invention of the terminal.

You could make similar arguments against SV: vim was written by a European (Bram Moolenaar) and GNU emacs was widely popularised by a European OS (Linux). Sadly local statistical trends are rarely that simple to explain (and if we're honest, the results of these polls are anything but trustworthy to begin with)

Re: Poll: Which is your primary text editor?

#146

Whenever I stumble into a "best editor" discussion, I am reminded of the words of Kieran Healy that adorn the top of my init.el (from http://kieran.healy.usesthis.com/ ): ``But even if TextMate 2 drops from the sky fully-formed and marveled at by all, Emacs will still be there, waiting. It will be there when the icecaps melt and the cities drown, when humanity destroys itself in fire and zombies, when the roaches fin…

And just like the platypus, vi/vim will still be there as the counter-example to intelligent design.

Re: Poll: Which is your primary text editor?

#147

Earlier quoted context omitted.

Sure they happen. But what is the basis for assuming so so matter-of-factly in this case ? If you ask me I'd expect SV to have higher vim/emacs penetration since it's been tech central since before the invention of the terminal.

> Sure they happen. But what is the basis for assuming so so matter-of-factly in this case? I can't help you there as I wasn't the one that made that comment. > If you ask me I'd expect SV to have higher vim/emacs penetration since it's been tech central since before the invention of the terminal. You could make similar arguments against SV: vim was written by a European (Bram Moolenaar) and GNU emacs was widely popu…

> I can't help you there as I wasn't the one that made that comment.

But you're totally derailing my thread as that is the entire point of my comment. The OP presented it like some sort of foregone conclusion that SV would obviously skew to Sublime. Why!? I am not trying to make a claim that A) geographical variances don't exist or B) SV over-represents vim / emacs (that was merely a wild guess, not meant to state a position, just meant to demonstrate that intuitively the OP's argument makes no sense).

I hope that's clear now.

Re: Poll: Which is your primary text editor?

#148

Earlier quoted context omitted.

> Sure they happen. But what is the basis for assuming so so matter-of-factly in this case? I can't help you there as I wasn't the one that made that comment. > If you ask me I'd expect SV to have higher vim/emacs penetration since it's been tech central since before the invention of the terminal. You could make similar arguments against SV: vim was written by a European (Bram Moolenaar) and GNU emacs was widely popu…

> I can't help you there as I wasn't the one that made that comment. But you're totally derailing my thread as that is the entire point of my comment. The OP presented it like some sort of foregone conclusion that SV would obviously skew to Sublime. Why!? I am not trying to make a claim that A) geographical variances don't exist or B) SV over-represents vim / emacs (that was merely a wild guess, not meant to state a…

To be honest, I think you're being a tad argumentative. All the former poster said was the was "I'm sure that there's a bit of selection bias going on." Which is actually a very fair comment as polling at set times when only a specific region is active will generate some selection bias. He didn't state that it's a forgone conclusion that vi/emacs is unpopular in SV. If anything, he was just stating the obvious about how not everyone is on the same timezone and thus around to vote.

And accusing me of "totally derailing [your] thread" when it's neither your thread and nor am I going off topic, is rather childish. I appreciate you wanted pyre to expand on his comments, but let's not descend into hair-pulling just because someone else happens to side with a comment that you presumably misinterpreted (and I'm making that presumption because you latter agreed with his comment when I reworded it).

Re: Poll: Which is your primary text editor?

#149
post #65

Earlier quoted context omitted.

Well, vi is the editor I use 2nd most (after Emacs), but I use nvi nearly as often as I use vim, and I avoid the vim extensions (except the useful :help). I imagine changing vi to vim would be a bit like changing Emacs to GNU Emacs.

Are you really using Vi or the vi command "aliased" to Vim on most distributions?

vi defaults to vim on some of my machines, to nvi on others. I like to have access to both.

vim pros: syntax highlighting is often nice (though when I really care about highlighting, I usually use Emacs), vim's :help is very nice, vim is usually installed

nvi pros: the small TCB I prefer when I'm root (`find /usr/share/vim -name \*.vim | wc -l` just gave me 1103 results, including hundreds of scripts that might be run without me explicitly asking for them), no splash screen, avoids the autoindenting that is often irritating, bound to vi on FreeBSD

I can't say nvi vs. vim efficiency has been an issue for me, but it has been for some people ... http://www.galexander.org/vim_sucks.html

Re: Poll: Which is your primary text editor?

#150

Earlier quoted context omitted.

I don't understand what you mean with the CLI aspect of acme. Could you elaborate? But re:"other cli" I agree: even ed counts as console-based, not CLI (which would be sed, cat, maybe awk and echo... not fun, but of course real programmers use butterflies)

With Acme, any piece of text can be executed as a command with a (IIRC) middle mouse button click. So in one pane on Acme, you can have the following written down: ls ~/dev uptime and middle clicking uptime or highlighting and then middle clicking ls ~/dev would literally run those commands and return the output in a new Acme pane (you can even go a step further and have commands inside comments in your source code -…

Oh, I didn't think of middle clicking as "CLI" related in any way... I'm a relative newbie with respect to Acme, but I have recorded some videos in my blog (tagged Acme) about cool stuff you can do with it, and that I find beautiful in its own way. I love emacs (and in fact also vim, I use evil in emacs) but I find some of the ideas behind acme just too cool to overlook. You can drive acme completely, making it a gui to your text-based code (via the virtual file system /acme/events which pipes everything that goes on in the acme window!)

In Acme, middle click executes text under the cursor (and middle selection executes selection,) whereas right-click looks for text/opens file depending on what you point it to. You can also add extra arguments to commands (via the 1-2 chord, where you select something with the left button, select something else with the middle button and click the left button afterwards, so you can have ~/dev in your file pane, ls in another pane and execute ls ~/dev in one go without typing anything else.

Now I understand your comment. Just a side remark, ~ usually doesn't work correctly in Plan9 from User Space and you have to input all the path... I'm sure it can be worked around, but I haven't got time to figure it out.

Re: XKCD reference, I just love that comic. I even went as far as using it as the image in the "landing page" (or index, depending on how you think about it) in my personal page at the department I did my PhD... I'm still the only emacs user among ~30 hardcore unix users that have a preference for vi and vim (yes, both, I didn't forget the "m".) I can understand that they like vim (or I could if they knew more vim than they do, but they mostly don't and miss all the cool stuff vim has to offer, which is lots) but I just can't get why they don't even try emacs to see what other intelligent beings see in it. I have done it with vim, acme and I even try to use sam and ed occasionally to get used to different paradigms in editing. Probably I'm just nuts :)

Post reply on HN