Comments on: Praise for the Humble gedit http://www.linux-mag.com/id/5982/ Open Source, Open Standards Sat, 22 Nov 2008 00:05:42 +0000 http://wordpress.org/?v=2.0.11 by: pstahle http://www.linux-mag.com/id/5982/#comment-1207 Sat, 21 Jun 2008 03:36:39 +0000 http://www.linux-mag.com/id/5982/#comment-1207 Depending on what I am doing I use vim (full, non vi compatible) or I will use jEdit. On a rare occasion I will pull out nedit and use that. I am kind of weird in that if I am used to editing certain types of files with a certain editor that is what I will feel most comfortable doing. For instance I have spent many years doing console editing of perl code from vim and feel uncomfortable editing/writing perl any other way. One of my pet peeves is all the distros that default to vim minimal, and have a lot of the great features of vim turned off.... that is just plain irritating.... Depending on what I am doing I use vim (full, non vi compatible) or I will use jEdit. On a rare occasion I will pull out nedit and use that. I am kind of weird in that if I am used to editing certain types of files with a certain editor that is what I will feel most comfortable doing. For instance I have spent many years doing console editing of perl code from vim and feel uncomfortable editing/writing perl any other way. One of my pet peeves is all the distros that default to vim minimal, and have a lot of the great features of vim turned off…. that is just plain irritating….

]]> by: Bryan Richard http://www.linux-mag.com/id/5982/#comment-1113 Tue, 27 May 2008 16:17:41 +0000 http://www.linux-mag.com/id/5982/#comment-1113 Anyone having trouble with Vim's learning curve might want to try installing Cream -- it takes some of the sting out of the Vim command structure but doesn't lose any of its text processing power. We just posted an article about it: <a href="http://www.linux-mag.com/id/6045" title="Sweeten Your Vim with Cream" rel="nofollow">Sweeten Your Vim with Cream</a>. Anyone having trouble with Vim’s learning curve might want to try installing Cream — it takes some of the sting out of the Vim command structure but doesn’t lose any of its text processing power. We just posted an article about it: Sweeten Your Vim with Cream.

]]> by: Soren Harder http://www.linux-mag.com/id/5982/#comment-1111 Tue, 27 May 2008 13:10:24 +0000 http://www.linux-mag.com/id/5982/#comment-1111 Hi, I have had to use Vi a couple of times and each time I am completely lost. I use Emacs a lot for programming and sometimes even for writing mails and copying them into my mail-program (it tends to die when you send the mail). I do not understand that anyone find the learning curve steep; isn't this the Platonic ideal of an editor? ;-) You just have to start at a young age ;-) Hi,

I have had to use Vi a couple of times and each time I am completely lost.

I use Emacs a lot for programming and sometimes even for writing mails and copying them into my mail-program (it tends to die when you send the mail). I do not understand that anyone find the learning curve steep; isn’t this the Platonic ideal of an editor? ;-) You just have to start at a young age ;-)

]]> by: dewfy http://www.linux-mag.com/id/5982/#comment-1110 Mon, 26 May 2008 07:43:30 +0000 http://www.linux-mag.com/id/5982/#comment-1110 The only reason I hate emacs - is a scrolling policy of large text. When your eye expects shifting line up, you get centring of this line on screen. It strange but I never meet workaround. The only reason I hate emacs - is a scrolling policy of large text. When your eye expects shifting line up, you get centring of this line on screen. It strange but I never meet workaround.

]]> by: Corne Beerse http://www.linux-mag.com/id/5982/#comment-1100 Fri, 23 May 2008 10:11:05 +0000 http://www.linux-mag.com/id/5982/#comment-1100 When I started with unix about 20 years ago, vi already was a steep learning curve but it was there on every unix machine. The alternative at that time was emacs, which had a more relax learning curve but a steep installation curve as it was (and stil is) not available on every installation... Then `vi` has some more advantages: If you know vi, specially the : commands, then you know `ed` (which effectively is what you use with the : commands) and you know all ed's deriviates as `ex` and `sed`. I see the regexp as available in ed is still unbeaten. It is the major reason why I keep comming back to the commandline to use vi. btw: I've just seen a msWindows Powershell and W2008 presentation. I wonder if edlin is available, notepad still is there... When I started with unix about 20 years ago, vi already was a steep learning curve but it was there on every unix machine. The alternative at that time was emacs, which had a more relax learning curve but a steep installation curve as it was (and stil is) not available on every installation…

Then `vi` has some more advantages: If you know vi, specially the : commands, then you know `ed` (which effectively is what you use with the : commands) and you know all ed’s deriviates as `ex` and `sed`.

I see the regexp as available in ed is still unbeaten. It is the major reason why I keep comming back to the commandline to use vi.

btw: I’ve just seen a msWindows Powershell and W2008 presentation. I wonder if edlin is available, notepad still is there…

]]> by: Bryan Richard http://www.linux-mag.com/id/5982/#comment-1086 Fri, 16 May 2008 15:28:14 +0000 http://www.linux-mag.com/id/5982/#comment-1086 The old joke about <a href="http://bash.org/?795779?" rel="nofollow">everyone's first vi session</a> rings pretty true. But after awhile you start to appreciate all of these ^'s (emacs) and :'s (vi). The old joke about everyone’s first vi session rings pretty true. But after awhile you start to appreciate all of these ^’s (emacs) and :’s (vi).

]]> by: Bryan Richard http://www.linux-mag.com/id/5982/#comment-1085 Fri, 16 May 2008 15:19:54 +0000 http://www.linux-mag.com/id/5982/#comment-1085 Yeah, that's what I mean. I used to be strictly KDE so I never had an opportunity use gedit until this week. I don't recall what the default editor was either in pre-2000 KDE. I'm pretty sure I just set the path to vi though. Yeah, that’s what I mean. I used to be strictly KDE so I never had an opportunity use gedit until this week. I don’t recall what the default editor was either in pre-2000 KDE. I’m pretty sure I just set the path to vi though.

]]> by: ageilers http://www.linux-mag.com/id/5982/#comment-1084 Fri, 16 May 2008 15:09:51 +0000 http://www.linux-mag.com/id/5982/#comment-1084 "Having been a KDE guy back in the day, gedit falls under the former category." Well, actually, gedit would go with GNOME. KDE currently would be Kate or Kwrite . I can't remember what editor came with KDE back when. “Having been a KDE guy back in the day, gedit falls under the former category.”

Well, actually, gedit would go with GNOME. KDE currently would be Kate or Kwrite . I can’t remember what editor came with KDE back when.

]]> by: David Bayer http://www.linux-mag.com/id/5982/#comment-1082 Fri, 16 May 2008 13:12:36 +0000 http://www.linux-mag.com/id/5982/#comment-1082 I'm one of those non-denominational text editors. Vim has a bit of a learning curve, but with a cheat-sheet posted on my monitor I use it for all cli text editing. In the gui I've used gedit for a while and like it pretty well. Played with kate some, but don't use it very much (for no particular reason). On Macs I use TextWrangler and on Windows I use PSPad. I'm all about the free stuff... I’m one of those non-denominational text editors.

Vim has a bit of a learning curve, but with a cheat-sheet posted on my monitor I use it for all cli text editing. In the gui I’ve used gedit for a while and like it pretty well. Played with kate some, but don’t use it very much (for no particular reason). On Macs I use TextWrangler and on Windows I use PSPad. I’m all about the free stuff…

]]> by: david Ford http://www.linux-mag.com/id/5982/#comment-1081 Fri, 16 May 2008 12:25:16 +0000 http://www.linux-mag.com/id/5982/#comment-1081 I agree with chavoux - Vi and EMACS are just too much hard work to use to edit a text file - I use 'joe'. david I agree with chavoux - Vi and EMACS are just too much hard work to use to edit a text file - I use ‘joe’.
david

]]>