> paredit - Yes, he wrote a kind of paredit for ST2. But it's really missing > several important functions. Plus it doesn't work as well as paredit.el does. > I tried to remedy these with no luck.
There were two plugins. The 1st link on Google is to and older one that points to the new one I sent you. Did you try the new one? > shortcuts - Sure, that's true about emacs too. But having a well-thought-out > system is different than just randomly changing shortcuts. Shortcuts are > surprisingly tied together in subtle ways. Then put some thought into your shortcut assignments. :-p > And for the record lispindent is awful, I remember someone recently > explaining why in a gist comment, either tim baldridge or tomjack (or someone > else who goes in IRC a lot). In my experience it's a vast improvement over the default. > splits - I mean split-panes, like both vim and emacs have. ST2 does okay in > this area, but could use improvements to get as good as emacs. I think I > heard ST3 is working on that. Did you try out the Origami plugin? It's excellent: https://github.com/SublimeText/Origami > No idea how to edit it, so I considered it a lost cause. Just regular expressions. If you know regex, then all you have to do is stare at the file for a while and it should become obvious what it's doing. You can also play around a bit with it. > nrepl - The post above says that ST's repl support is super-crashy. That > doesn't give me a whole lot of confidence. OK, well, were they talking about the fork I was referring to? Are you sure? Did you try it yourself? I haven't experienced a single crash so far. I see you didn't comment on the jump-to-* recommendations... why not? Cheers, Greg -- Please do not email me anything that you are not comfortable also sharing with the NSA. On Jul 27, 2013, at 2:56 PM, Steven Degutis <sbdegu...@gmail.com> wrote: > Greg, thanks for your reply. Please see my responses: > > paredit - Yes, he wrote a kind of paredit for ST2. But it's really missing > several important functions. Plus it doesn't work as well as paredit.el does. > I tried to remedy these with no luck. > > shortcuts - Sure, that's true about emacs too. But having a well-thought-out > system is different than just randomly changing shortcuts. Shortcuts are > surprisingly tied together in subtle ways. > > tabs - I meant tab-bar, and in this area ST2 is pretty much okay. It's a > little awkward that the same shortcuts switch between splits and tabs though. > And for the record lispindent is awful, I remember someone recently > explaining why in a gist comment, either tim baldridge or tomjack (or someone > else who goes in IRC a lot). > > splits - I mean split-panes, like both vim and emacs have. ST2 does okay in > this area, but could use improvements to get as good as emacs. I think I > heard ST3 is working on that. > > magit - I'll check it out, thanks. > > themeable - true. But related to this is the terrible Clojure syntax file for > ST2, where almost everything is highlighted the same. For example only the > colon in a keyword is highlighted special, the rest of the keyword is > un-highlighed. And it's not just a theme issue, it's the same for every > theme, so it must be a syntax definition problem. I tried to fix it up, found > it was really just a TM bundle, and was terrified by its size. No idea how to > edit it, so I considered it a lost cause. > > nrepl - The post above says that ST's repl support is super-crashy. That > doesn't give me a whole lot of confidence. > > -Steven > > > On Sat, Jul 27, 2013 at 1:44 PM, Greg <g...@kinostudios.com> wrote: > Steven: > > ST2 has the following features that you wanted: > > * paredit or better > - https://github.com/odyssomay/paredit > * keyboard shortcuts that dont kill my wrists/pinkies/fingers > - you can make whatever shortcuts you want > * jump-to-symbol-definition > - see my post on ST2 in the "is intellij idea a good idea" thread dated > July 25th. > * jump-to-file > - the built-in "goto anything" works for that, and there are > file-specific plugins too > * tabs (a la macvim) > - not sure what you mean, but there a plugin called "Lispindent" that > works great > * splits (a la emacs) > - not sure what you mean, but there's a "Split Into Lines" command > * magit or better (might be willing to ignore this omission though) > - Use these 3 plugins together: GitGutter, Side Bar Git, and SublimeGit > * not-super-bloated UI > - ST fits this definition perfectly > * themeable (dont care if it has a good theme, i can make one if need be, i > just need it to be themeable) > - ST is themeable (see my post in the other thread on July 25th) > * something like nrepl.el > - ST has SublimeREPL, which has a fork that works with nREPL. Link in > the other thread. > > So.... looks like you're pretty much covered by ST already. :-) > > Cheers, > Greg > > -- > Please do not email me anything that you are not comfortable also sharing > with the NSA. > > On Jul 27, 2013, at 11:57 AM, Steven Degutis <sbdegu...@gmail.com> wrote: > >> I would be willing to pay /really/ good money for an editor that has a few >> features: >> >> * paredit or better >> * proper syntax highlighting of clojure (emacs rocks at this, ST2 sucks at >> it) >> * ST2-quality fuzzy matching at every completionable prompt (emacs's >> ido-mode is alright but ST2's is way better) >> * keyboard shortcuts that dont kill my wrists/pinkies/fingers >> * jump-to-symbol-definition >> * jump-to-file >> * tabs (a la macvim) >> * splits (a la emacs) >> * magit or better (might be willing to ignore this omission though) >> * not-super-bloated UI >> * themeable (dont care if it has a good theme, i can make one if need be, i >> just need it to be themeable) >> * something like nrepl.el >> >> (where ST2 means Sublime Text 2) >> >> That's *all* I care about, nothing else matters to me. But no editor can get >> *all* these things right. >> >> -Steven >> >> >> On Sat, Jul 27, 2013 at 6:54 AM, Colin Fleming <colin.mailingl...@gmail.com> >> wrote: >> Hi all, >> >> I was planning to wait a little longer before going public, but since it's >> pretty relevant to the other IntelliJ thread going on at the moment I >> thought I'd jump in. For the last couple of months of happy unemployment >> I've been working on a fork of La Clojure which is now about 70% migrated to >> Clojure and significantly improved. It's a lot of work to develop a tool >> like this, and one of the options I'm considering is starting a company to >> develop it as a commercial product - JetBrains have never maintained >> development of La Clojure very actively. I've been doing a little market >> research but there's really not much data around about whether there are >> enough people working with Clojure to sustain a product like that, and also >> the community is currently very focused on open source. >> >> One problem is that the IDE space is already fairly fractured - there's >> Emacs and CCW, Clooj, Sublime Text and the promise of Light Table at some >> point, and of course the current public version of La Clojure. But there's >> still not a great option for something that's powerful but easy to use - CCW >> is probably the closest thing to this right now. However I think it's >> telling that a large fraction of people in the State of Clojure 2012 survey >> still identified development tools as a major pain point. >> >> I think that the IntelliJ platform is a fantastic base to build something >> like this on. Clojure as a language makes it pretty challenging to develop a >> lot of the great functionality that JetBrains are famous for, but I think >> there's scope to do a lot of great things. Certainly for mixed Clojure/Java >> projects it would be difficult to beat, but even for Clojure only projects I >> can imagine a lot of fantastic functionality built on their infrastructure. >> My plan would be to release a standalone IDE and a plugin for people using >> IntelliJ Ultimate for web dev, Ruby/Python or whatever. Since it's mostly >> Clojure now (and I'm migrating what's left as I get to it) there's a real >> possibility of a Clojure plugin/extension API. I envision charging >> PyCharm/RubyMine type prices, say $200 for company licenses or $100 for >> individual developers. >> >> So, I'd love to hear what people think. I'd appreciate it if we could stay >> away from the politics of open source vs proprietary - several people have >> told me privately that they'd rather use OSS and that's fine, proprietary >> isn't for everyone. What I'd like to know is if the idea is appealing to >> many people here? >> >> In case it's a concern for anyone, I've discussed this with JetBrains. >> >> Thanks for any feedback, >> >> Cheers, >> Colin >> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with your >> first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> -- >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clojure@googlegroups.com >> Note that posts from new members are moderated - please be patient with your >> first post. >> To unsubscribe from this group, send email to >> clojure+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> > > > > -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > >
signature.asc
Description: Message signed with OpenPGP using GPGMail