You are right that the thread should be Console based IDEs. I don't think the name can be changed now though (at least I have not found a way). The type of tool used can depend on the task I am performing. I prefer a GUI for editing due to being able to have many files open and just click between them (in principle possible with the console as well). I particularly like the gui when I am debugging. the ability to just hover my mouse over a variable and just see what it is set to I find quite natural. I have used gdb and know it is possible to output the value of variables from the console too but in that case I found setting break points challenging because from the console I could be looking at source files or in gdb but not both. It might have been more challenging than it would otherwise be because the code was objective-c and getting the method names right for break points I found a bit of a challenge. Also a GUI IDE can combine multiple bits of data together from different sources in the same display such as allowing me to browse a database schema my code has to interact with. Performing queries from the console in PostgreSQL I frequently find the number of columns will be too big for the width of the console and so the rows will wrap and then it gets really hard to follow which value is in which column.
On Jan 19, 1:11 pm, "Ricky Clarkson" <[email protected]> wrote: > It sounds like we're around the same age, but I vastly prefer command-line > tools, as I can automate them, they're quite often faster and they work on > machines I only have non-graphical access to. > > Beyond that I should have pointed out a flaw in your original question. > > Generally, command-line tools are those that take command-line arguments and > more or less run without user interaction. > > That means a command-line IDE is pretty much impossible; you mean a console > application. What I said in the first paragraph of this mail refers to > command line tools, and I believe no matter the generation we should all be > comfortable with those. Console applications, the difference between > graphical and textual isn't as important as the featureset and usability > differences. > > > > > > > > -----Original Message----- > From: Carl Jokl <[email protected]> > Sender: [email protected] > Date: Thu, 19 Jan 2012 05:23:31 > To: The Java Posse<[email protected]> > Reply-To: [email protected] > Subject: [The Java Posse] Re: Command Line based IDEs > > It makes sense that a command line IDE can in theory support many or > most of the same functionality as a GUI IDE. The command line is after > all > just a different view on what can be just the same model. I just don't > have enough experience of trying to do development with *nix command > line editors > to know what is and isn't supported just that lots of people rave > about how great Emacs is. > > I think it can be a generational thing based on when people came in > contact with Unix environments. I like most others didn't get proper > exposure to it until University. This was post 2000 so GUIs even for > Linux/Unix were the norm. I am still old enough to have worked from > the command line and so have done a bit for both worlds. I just get a > bit fed up sometimes with prevailing attitudes that real men must do > everything from the command line to show how clever this is. It seems > a lot less to do with efficiency and more to do with bravado and ego. > Still if I had the same level of experience as others doing things > from the command line then I am sure I might find it powerful. I am > not sure it would be enough to make me want to give up my IDE though. > > On Jan 19, 12:32 pm, Josh Berry <[email protected]> wrote: > > On Thu, Jan 19, 2012 at 4:35 AM, Carl Jokl <[email protected]> wrote: > > > It did make me curious though as to what kind of development power is > > > available from command line editors like Emacs. I know that key > > > features I like in IDE's is the ability to hyperlink through to a > > > method declaration / class declaration or where a variable is > > > declared. Also finding the usages of a method is really valuable to me > > > as well as being able to apply various forms of refactoring. In theory > > > a command like editor could support some or all of that. However I > > > don't know what features are actually currently available. > > > Pretty much all of the navigation stuff that you named has been there > > for ages in c like languages with ctags. Even in vim I can ctrl-] on > > a word and it will pop me a list of all of the places that symbol is > > used. I don't use emacs, but I understand that it can actually be a > > bit more advanced than just ctags. Just take a look at the scala > > support in emacs to see that it is not lacking ability. > > > Add in fugitive.vim and you have a really good front end to a git > > repo. :Ggrep "sdfsf" will let you quickly cycle through all git grep > > results ridiculously quickly, for instance. (With emacs, you can just > > have an embedded terminal and then you are back to anything you can do > > in the command line can be done in the editor.) > > > Refactoring is something that is often not as well supported, to my > > knowledge. > > > And this is ignoring the quip a lot of *nix folks have about it being > > their ide. :) > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/javaposse?hl=en. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
