Fedora gedit for bash has become useless

[EdH]

[rant]
The more Fedora advances, the more useless it is becoming - recall my other issues...

Now I find that gedit is producing a "Windows" formatted text, that won't run as a bash script.

Do any of the learned linux guys have a quick fix? I'm about to trash Fedora. Maybe it's past time...
[/rant]

Thanks for any help...

[Mark Rose]

Check the line ending setting. You want "Unix" line termination, not "Windows" or "Mac".

I don't use gedit personally, as I really dislike Gnome, but googling tells me there should be a "Line Ending" setting when you save the file.

[jasonp]

Your system should also have 'unix2dos' and 'dos2unix' utilities that allow you to retroactively fix the line endings on files you have.

Windows notepad similarly cannot properly display files with unix line endings; I work around as necessary. Incompatibilities between text editors are low on the list of cross-platform problems that I have to deal with.

[EdH]

Thank you for the replies. I had looked with no success for the line ending setting. It must be hiding with the un/redo entries I'm suppose to have.

Anyway, the problem is fixed. I unwittingly caused it due to another recent shortfall of Fedora: files no longer allows for the creation of a new document via a right-click. Therefore, I copied/pasted an existing .sh file and edited it. Apparently the c/p transformed the original's line endings for some unknown reason.

By starting afresh with a new gedit document, and creating/saving a .sh file with the proper first line, the line endings are correct for the rest of the editing.

I was unaware of the two conversion routines. Thanks! I may make use of those.

[Xyzzy]

[Xyzzy]

For fun you can use od to view the actual contents of a file.

$ cat dos.txt | od -c
0000000   a   b   c   1   2   3  \r  \n   1   2   3   a   b   c  \r  \n
0000020
$ cat unix.txt | od -c
0000000   a   b   c   1   2   3  \n   1   2   3   a   b   c  \n
0000016

More info:

http://stackoverflow.com/questions/2...in-bash-script

[Xyzzy]

Originally Posted by jasonp

Windows notepad similarly cannot properly display files with unix line endings; I work around as necessary.

Open the file in "Wordpad" first, then just save it and then open it in "Notepad".

[ccorn]

Originally Posted by jasonp

Windows notepad similarly cannot properly display files with unix line endings; I work around as necessary. Incompatibilities between text editors are low on the list of cross-platform problems that I have to deal with.

Funnily enough, the "edit" command in the DOS box ("run command...") can deal with unix line endings; just opening and saving the text file should convert the line endings to CR LF. At least that was in XP times, and I do not use Windows much. Of course, notepad++ can handle such things too.

Originally Posted by EdH

Now I find that gedit is producing a "Windows" formatted text, that won't run as a bash script.

Do any of the learned linux guys have a quick fix?

With standard coreutils, from dos to unix (delete CR):

tr -d '\r' <winfile.txt >unixfile.txt

or in-place with sed (and with a backup file):

sed -i.bak 's:\r::g' textfile.txt

[LaurV]

in windoze, use Programmers' Notepad !
(one of the best, small, and free!)
(no, eclipse is not "small")

You can select what line endings you want, and write your own scripts, own menu commands, etc, if you like.

It also has a nice python extension and lots of syntax schema...

[Mark Rose]

Notepad.

I remember using Notepad.

Once I had to create a web based tutorial on using FrontPage.

FrontPage was so awful I wrote the tutorial in Notepad.

[rogue]

Originally Posted by Xyzzy

Open the file in "Wordpad" first, then just save it and then open it in "Notepad".

Try NotePad++. It blows away NotePad on all fronts.