From: Olga G. <ol...@gm...> - 2009-09-18 16:14:47
|
I used Vim, so that's probably what happened! I just found another way of figuring out what characters exactly are in the file: hexdump -C check.file There were two 0A characters at the end - hence two newlines. 2009/9/18 Witold Baryluk <ba...@sm...> > Dnia 2009-09-18, pią o godzinie 11:04 -0400, Olga Gelbart pisze: > > Hi Marcel! > > That worked! my system boots fine now. I guess when I tried to make > > sure there is a newline character at the end of the line, I actually > > added an extra line! > > I think Vim is one of few editors which implicitly adds newline at the > end last line (if it is not empty). It does this even if you just open > and write file back. I found this is very irritating, also because i > mostly put my own enter there, so this end having two of new line > characters. > > mcedit doesn't have this problem :) Or cat > file :) > > > BTW. fastest way is to just cat file to terminal, if it have no eneter, > your prompt will end on the same line as last line: > > > sredniczarny:~> cat bz > ala > ma kotasredniczarny:~> > > If it is written correctly it should be: > > sredniczarny:~> cat bz > ala > ma kota > sredniczarny:~> > > But not this: > > sredniczarny:~> cat bz > ala > ma kota > > sredniczarny:~> > > > -- > Witold Baryluk > |