Live data from Hacker News

Setting up Sublime Text 2

drewbarontini.com

21–30 of 53 posts

Re: Setting up Sublime Text 2

#21

One of the things I like most about Sublime is that it just works right out of the box. Sure almost everyone uses a plugin or two, but to me it's the editor that doesn't need blog posts about how to configure it, it doesn't require you to keep a git repository of your thousand-line configuration, it doesn't require an understanding of esoteric key commands to get started. To me, Sublime is an editor for people who do…

I agree. I also love the way it stores settings as an explicit list of changes from defaults (rather than a list of all settings and their values, default and otherwise), so you always know what's up.

My settings file only has a light theme and trim_trailing_spaces_on_save, and I'm very content with that.

This isn't to dismiss its flexible and configurable nature, which is awesome. I just don't need to do more for now.

Re: Setting up Sublime Text 2

#22
post #17

How do you put downloaded themes into Sublime Text 2?

Is there a particular theme you're interested in?

Two options:

1. Download package control [1] (first config listed in OP) and then search for themes.

2. Visit the individual theme repos (mostly on GH) and follow instructions.

[1] http://wbond.net/sublime_packages/package_control

Re: Setting up Sublime Text 2

#24
post #13

Earlier quoted context omitted.

It's half-way there. It could go a lot further. I'm really surprised there isn't a single (featureful) editor that follows the OSX/GNOME aesthetic of "convention over configuration; no preferences/options/modes if possible". Key-bindings are the same everywhere you go. Every command is available on every instance of the editor on everyone's machine, everywhere in the world. You never have to re-learn anything; you ca…

I'd suggest you should download every plugin for ST and see how bloated it becomes, you'd end up with something as slow and ungainly as Eclipse. To me, one of the largest benefits of ST is having a very powerful editor which is fast, simple, and very usable, and wouldn't want to see the core become much heavier than it already is (although I'm loving the code navigation functionality coming in ST3).

Oh, I'm certain that having all the plugins running code in the background at once would be a horrible experience (in much the same way that "installing every browser extension" would be a horrible experience.) I'm thinking mostly of plugins (packages, really) that just add code you can call through the command system--they don't do anything or consume any resources unless you prompt them to, so why shouldn't they be shipped with the runtime?

But on the other case--what sort of Sublime plugins do you use that constantly run in the background doing something? I don't use any myself that do anything like that; what are some good examples?

Re: Setting up Sublime Text 2

#25
I know Sublime Text has a lot of momentum, especially on this site, but the one main ting which keeps me from adopting Sublime text is that I can't run it from a terminal. Simple as that.

If I'm going to invest time, effort and know-how into something as fundamental as a text-editor, I want to know that I can run it everywhere I need it.

I'm going to guesstimate that I spend at least 20% of my text-editing via terminals, via SSH, via remote sessions somehow. And there I can't use Sublime Text at all.

In those remote sessions I'm probably editing the same things I do locally, so why should I need to change my entire environment to suit that 20% of the same workload? It just doesn't make sense.

Other objections to Sublime text would be that it's not open source. With more and more (new) arm-based platforms popping up left and right, that becomes increasingly important. I want to know that I can take my tools with me to the places I go. Not being open-source severely limits those possibilities.

Re: Setting up Sublime Text 2

#26

I know Sublime Text has a lot of momentum, especially on this site, but the one main ting which keeps me from adopting Sublime text is that I can't run it from a terminal. Simple as that. If I'm going to invest time, effort and know-how into something as fundamental as a text-editor, I want to know that I can run it everywhere I need it. I'm going to guesstimate that I spend at least 20% of my text-editing via termin…

You can use the built in 'subl' command to launch Sublime Text 2 from the terminal.

http://www.sublimetext.com/docs/2/osx_command_line.html

Editing remote files is as simple as an SFTP mount.

Re: Setting up Sublime Text 2

#27
post #26

I know Sublime Text has a lot of momentum, especially on this site, but the one main ting which keeps me from adopting Sublime text is that I can't run it from a terminal. Simple as that. If I'm going to invest time, effort and know-how into something as fundamental as a text-editor, I want to know that I can run it everywhere I need it. I'm going to guesstimate that I spend at least 20% of my text-editing via termin…

You can use the built in 'subl' command to launch Sublime Text 2 from the terminal. http://www.sublimetext.com/docs/2/osx_command_line.html Editing remote files is as simple as an SFTP mount.

That is for OSX, which I refuse to use on an principle of ethical software conduct. Apple is hostile to open software and computers as open platforms. They want to take away the open nature of computers which allowed them to exist in the first place and they use BS patent-lawsuits to hinder competitors willing to provide just that.

They are evil and I refuse to support them with a penny or any significant effort or attention.

Apart from that, talking about SFTP mounts is completely missing the point.

Sometime I'm in a terminal, on a router, NAS, cloud-server or whatever, and need to edit some files in the current folder.

What I do then is "$ emacs file", not change context, go to another local terminal and fuse-mount some completely remote FS with whatever keys and credentials I need to provide, in /mnt/remote/, and then fire up a local editor for /mnt/remote/the/actual/directory/i/was/working/in/file.

That's extremely inefficient.

When I say I need something to work in a terminal to be a proper solution, I mean any terminal.

Re: Setting up Sublime Text 2

#28
post #26

I know Sublime Text has a lot of momentum, especially on this site, but the one main ting which keeps me from adopting Sublime text is that I can't run it from a terminal. Simple as that. If I'm going to invest time, effort and know-how into something as fundamental as a text-editor, I want to know that I can run it everywhere I need it. I'm going to guesstimate that I spend at least 20% of my text-editing via termin…

You can use the built in 'subl' command to launch Sublime Text 2 from the terminal. http://www.sublimetext.com/docs/2/osx_command_line.html Editing remote files is as simple as an SFTP mount.

way to miss the point. op needs it to run _in a terminal_.

Re: Setting up Sublime Text 2

#29
post #13

Earlier quoted context omitted.

It's half-way there. It could go a lot further. I'm really surprised there isn't a single (featureful) editor that follows the OSX/GNOME aesthetic of "convention over configuration; no preferences/options/modes if possible". Key-bindings are the same everywhere you go. Every command is available on every instance of the editor on everyone's machine, everywhere in the world. You never have to re-learn anything; you ca…

This is pretty much Textmate to a T. Uses OS X conventions, heavily configured for doing real work out of the box instead of installing 10 packages, has a built-in system for language definitions and plugins. Auto-updates which will include language and theme updates as well.

"Every command is available on every instance of the editor on everyone's machine, everywhere in the world."

OS X is neither on everyone's machine nor everywhere in the world. By a large stretch!

Re: Setting up Sublime Text 2

#30
post #26

Earlier quoted context omitted.

You can use the built in 'subl' command to launch Sublime Text 2 from the terminal. http://www.sublimetext.com/docs/2/osx_command_line.html Editing remote files is as simple as an SFTP mount.

That is for OSX, which I refuse to use on an principle of ethical software conduct. Apple is hostile to open software and computers as open platforms. They want to take away the open nature of computers which allowed them to exist in the first place and they use BS patent-lawsuits to hinder competitors willing to provide just that. They are evil and I refuse to support them with a penny or any significant effort or a…

I fell for the peer pressure and tried to use a macbook some time ago and I feelt like I was in the movie "the island", but I wouldn't say that apple are any more evil than other companies in the IT industry.

So here I am running linux once more.

I have a lot of time invested in emacs but I have switched to sublime since early versions of v2-beta. My main reason was at that time the ruby and RoR modes for emacs wasn't really up to speed.

I like sublime text and I don't regret jumping on that train. Easy to get started, lots of features and plugins, highly configurable. I use sublime as my main "desktop" editor now.

When editing over ssh emacs is my preferred editor, after 15 years of using emacs as my primary editor I think I have enough emacs keystrokes deeply imprinted in my brain to last me a lifetime ... :)

Post reply on HN