Author Topic: So I had to kill gvim  (Read 3744 times)

Mike

  • Jackass In Charge
  • Posts: 11257
  • Karma: +168/-32
  • Ex Asshole - a better and more caring person.
So I had to kill gvim
« on: August 09, 2006, 10:49:16 PM »
Over the last few months we've noticed that several files were mysterously adding newlines to the end of php files after the ?>
Now this is bad because that new line is now HTML and it can cause all sorts of troubles on some servers.

We finally tracked it back to me.  It turns out that everytime I saved it would put a newline at the end of the file if there was one there.  Now comes the really fucked up part, inside the program itself I couldn't see it.  It would show/act like there was no newline.

So I had to kill it.  Lets hope edit plus 2 is better.

Perspective

  • badfish
  • Jackass In Charge
  • Posts: 4635
  • Karma: +64/-22
    • http://jeff.bagu.org
Re: So I had to kill gvim
« Reply #1 on: August 09, 2006, 10:53:58 PM »
emacs will warn you if your source doesn't have a newline at the end. Many compilers/interpreters of various languages don't like not having a newline at the end.

Stephen

  • Jackass IV
  • Posts: 426
  • Karma: +23/-3
Re: So I had to kill gvim
« Reply #2 on: August 09, 2006, 11:02:50 PM »
I first read this as "So I had to kill jkim."



Oh, well.


<3 ... ?

PS: I'm glad that I can be such a great contributer to this community.

ober

  • Ashton Shagger
  • Ass Wipe
  • Posts: 14310
  • Karma: +73/-790
  • mini-ober is taking over
    • Windy Hill Web Solutions
Re: So I had to kill gvim
« Reply #3 on: August 09, 2006, 11:37:13 PM »
LOL @ overthrown... I read the same thing. 

Also, this appears to be more of a software thing.... MOVED.

hans

  • Guitar Addict
  • Jackass In Charge
  • Posts: 3523
  • Karma: +46/-18
Re: So I had to kill gvim
« Reply #4 on: August 10, 2006, 12:01:01 AM »
EditPlus is one of my favorite editors. I've trimmed down to just using jEdit (since my lappy is super powerful now) but I've used EditPlus for the last few years as my text editor of choice. Very fast and flexible.
This signature intentionally left blank.

Mike

  • Jackass In Charge
  • Posts: 11257
  • Karma: +168/-32
  • Ex Asshole - a better and more caring person.
Re: So I had to kill gvim
« Reply #5 on: August 10, 2006, 12:12:43 AM »
emacs will warn you if your source doesn't have a newline at the end. Many compilers/interpreters of various languages don't like not having a newline at the end.
Yes but it should still show the damn newline in the file.

ahluka

  • Jackass IV
  • Posts: 794
  • Karma: +10/-201
Re: So I had to kill gvim
« Reply #6 on: August 10, 2006, 10:48:42 AM »
I edit almost everything with the VS 2003 IDE.
Well, almost. Anything that VS doesn't have syntax hilighting for (perl python ruby etc) I use ConTEXT. Nice and lightweight with easily customisable syntax hilighters.

Mike

  • Jackass In Charge
  • Posts: 11257
  • Karma: +168/-32
  • Ex Asshole - a better and more caring person.
Re: So I had to kill gvim
« Reply #7 on: August 10, 2006, 11:21:24 AM »
Well goodie for you.

jkim

  • Jackass In Charge
  • Posts: 3290
  • Karma: +106/-12
Re: So I had to kill gvim
« Reply #8 on: August 12, 2006, 08:17:29 PM »
I first read this as "So I had to kill jkim."



Oh, well.


<3 ... ?

PS: I'm glad that I can be such a great contributer to this community.
I totally didn't read that until today.  Thanks, feeling the love.

(I'm glad I can contribute as much as overthrown)