On Jan 16, 2013, at 7:29 AM, Colin Yates <colin.ya...@gmail.com> wrote:
> Hi all, > > After 15 off years of using IDEs I am making the jump into Emacs. I have > read http://dev.clojure.org/display/doc/Getting+Started+with+Emacs and > https://github.com/technomancy/emacs-starter-kit and I am just at the point > where I have stopped yelling at paredit and starting to appreciate its point. > > My current major stumbling block though is navigating my project. Whilst (I > expect) the density and sane namespacing capabilities of Clojure to > significantly reduce the number of files, that isn't true of everything. In > particular, ExtJS encourages you to follow the "one file per class". You > don't have to but eventually you will have more than a handful of files > regardless. > > So my questions: > - is there a decent project explorer. I really miss the "tree on the left, > editor on the right" layout > - is there a decent JS and clojure autocompletion aware plugin > - other than paredit, nrepl and clojure-mode (and the excellent coffee-mode > for coffeescript), what other plugins should I install Hi Colin: No real answers, but I wanted to chime in to say that I'm in the same spot. I had been putting off using Emacs until I felt I was "ready", but then came to realize that the choice to use Emacs is like the choice to have kids. If you wait until you're "ready", you'll never do it. This is week 2 and it's definitely getting better, altho truth be told it wasn't nearly as bad last week as I expected it would be. Been working on the desktop with a cheat sheet constantly open on my laptop next to me. I also miss the project explorer. I'm used to working with multiple files at once, having them open in tabs, and being able to easily switch back and forth between any of them. I've definitely found that to be a bit jarring in Emacs, but trust that at some point I'll get used to the "Emacs way" versus trying to find a plugin to provide a project explorer. I have to remind myself that all of the files that I'm working with are there, they're just not immediately visible. M-x B will let me go thru the list of files open in buffers, even if those buffers aren't visible. It's different, but that's where the trust comes in :) The biggest issue I find with the lack of a project explorer is when I don't know what directory a particular file is in. Emacs provides great autocompletion when you're navigating to a particular file in the minibuffer, but that presumes you know exactly where the file is. I suppose there's always the option of opening a dired buffer (M-x dired) or even a shell (M-x shell). That's still not as "easy" or visual as a directory tree, but I think the big issue is that Emacs is really all about keeping your hands on the (proper) keys. A shell at least lets you continue to type your way around your directory structure to locate a file. A directory tree/project explorer would likely require grabbing the mouse and clicking down into various directories. It's what we're used to, yes… but it's not really, um… idiomatic Emacs :D -- Charlie Griefer http://charlie.griefer.com "Give light, and the darkness will disappear of itself." -- Desiderius Erasmus -- 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
