since your were talking about kde4... what do you think about KDevelop?
Catfish wrote:
I can only comment that I very much dislike the default syntax highlighting that Kwrite, Kate and KDevelop use.
Otherwise I don't have any real experience using KDevelop, and I'm looking forward to learning it. A while back I used to use Kate for multiple files and its terminal to run make. I suppose KDevelop could be a better choice?
hanst99 wrote:
On Linux, I usually use Vim for editing, git for version control and rake as a much better make alternative. Though I haven't ever actually tried KDE. (I'm one of those strange people that likes Unity).
Catfish wrote:
@ hanst99: I don't understand the appeal of Vim, could you enumerate the reasons why you prefer it to a modern graphic editor with menus and file tabs?
hanst99 wrote:
@Catfish - in any file editor I would end up using hotkeys anyways. And Vim hotkeys (and commands) are IMHO far easier to use. I am using 9 workspaces, so if I am actually editing 2 or more files parallely I am just running multiple instances of Vim. If I just need to do a quick lookup (e.g. in a header while editing a source file), I just open a split window. But it's a personal thing really - you try it, and then you like it or you don't. I don't think there's such a thing as a text editor that everyone will accept equally.
could you enumerate the reasons why you prefer it to a modern graphic editor with menus and file tabs?
There are tabs in vim.
One thing that I like is the possibility to open the file in multiple tabs/windows.It provides useful when doing a merge. So a tab have the diff, and the other have just the file (with syntax highlight)
Also the regex are quite good.
Or just the little commands: change-word, change-inner_block (parenthesis, quotes, brackets)
The mouse is slow, trying ratpoison now.
ed is the standard editor
When I used to own a server, I could use vim through SSH to edit my projects remotely so I didn't have to manage a local git repository.
Also, vim can use the mouse if there's a mouse available and it's enabled.
Also, my take on the mouse is similar to this: When you play an RTS game, you're discouraged to use the mouse because it lowers a productivity. You'll never see a professional Starcraft II player use the mouse as much as a beginner.
Didn't realize a new thread for this topic was made. So I'll just c/p my original post:
Albatross, I've never understood the appeal of vim either. I prefer using Geany and then going to command line to compile. Need to learn makefiles and cmake now that I think about it.
What? Why? ;_;
Wait, is there any other compiler under Linux besides GNU? I've just used GNU and never looked at other compilers.
There's clang, though it's not as well-supported as it could be. I've had really positive experiences with it.
The main reason I still use g++ is because it's still better supported by most IDEs than clang in terms of error message parsing. That and there's no qmake profile for clang. But at least if I wanted to, I could configure Qt Creator to use clang.
Oh I hadn't heard of clang before. I have Qt Creator, KDEvelop 4, Anjuta, Code blocks, and God knows what else on here. Use mostly Geany and command line though as I said.
Nano must be the strangest choice of them all. That's literally less than coding in notepad, it has no mouse support. And yet, I do know people, in real life, that use nano.
Nano must be the strangest choice of them all. That's literally less than coding in notepad, it has no mouse support. And yet, I do know people, in real life, that use nano.
I chose it as a command line editor. I'd hardly call it less than coding in notepad considering you can get syntax highlighting with it. As for it not having mouse support, I seldom use a mouse when at the command line anyways.
nano is what I use for quick editing, gedit is my text editor of choice. It manages to have (almost) all the features I want while still being simple enough to not irritate me. I usually only use an IDE for C#, in which case I use MonoDevelop. Otherwise I use hand-written Makefiles (it takes me about 5 seconds to write them because I write them mostly from memory) and the command-line.