Changing Line Endings

[Warren Michelsen]

BBEdit 8.6

OK, I miss the nice little pop-up we had to easily change line endings for any open file between Unix, Mac and Windoze. That option seems to have disappeared and is now only accessible through the far more cumbersome Save As... -> Options, etc.

Why did the BareBones folks remove that?

Is there a simple script or such available to get that back? I suppose I could do a find/replace but the pop-up control on the window was handy to indicate which type line endings were already present.

Sometimes I miss the older versions...

Fixed bug in which changes to the Text Encoding or Line Endings
popup menus in the status bar didn't become immediately visible;
the change really was made, though. [64848]

So there still IS a line endings pop-up selector? Where is it?

Didn't this used to be in the Show Line Numbers, Soft Wrap Text, etc. menu?

[Matthew Fischer]

Post by Warren Michelsen
BBEdit 8.6
OK, I miss the nice little pop-up we had to easily change line
endings for any open file between Unix, Mac and Windoze. That
option seems to have disappeared and is now only accessible through
the far more cumbersome Save As... -> Options, etc.

Preferences -> Text Status Display -> Show Status Bar -> Line Break Type

will give you the pop-up back at the bottom of your window.

[Doug McNutt]

Post by Warren Michelsen
OK, I miss the nice little pop-up we had to easily change line endings for any open file between Unix, Mac and Windoze.

It ain't BBEdit but here is some AppleScript and simple C that works..

<ftp://macnauchtan.com/Software/LineEnds/FixEndsFolder.sit> 52kB
--
--> Life begins at ovulation. Ladies should endeavor to get every young life fertilized. <--

[Scot Hacker]

Post by Warren Michelsen
Why did the BareBones folks remove that?

It wasn't removed - just moved to the bottom of the document window.
Look in the lower left for three picklists:

Language Selector | Encoding | Line Endings

./s

--
Scot Hacker, Webmaster
Graduate School of Journalism
UC Berkeley
http://journalism.berkeley.edu

[Warren Michelsen]

Post by Scot Hacker

Post by Warren Michelsen
Why did the BareBones folks remove that?

It wasn't removed - just moved to the bottom of the document window.
Language Selector | Encoding | Line Endings

Ah, thanks!

[Joe Chellman]

Post by Warren Michelsen
So there still IS a line endings pop-up selector? Where is it?

There's a new status bar at the bottom of the window, and you'll find
it there. If you don't see it, open the preferences and look in Text
Status Display, and enable the stuff there.

Joe
--
Joe Chellman
http://www.chellman.org/
http://www.chellman.org/pgp_key.txt

[E David Miller]

At the bottom of the text window, the 'status bar' there includes the
type of file and context highlighting, the text encoding, and the
line ending. Each of these can be clicked on to present a select-list
with all available options for each.

Post by Warren Michelsen
BBEdit 8.6
OK, I miss the nice little pop-up we had to easily change line
endings for any open file between Unix, Mac and Windoze. That
option seems to have disappeared and is now only accessible through
the far more cumbersome Save As... -> Options, etc.
Why did the BareBones folks remove that?
Is there a simple script or such available to get that back? I
suppose I could do a find/replace but the pop-up control on the
window was handy to indicate which type line endings were already
present.
Sometimes I miss the older versions...

Fixed bug in which changes to the Text Encoding or Line Endings
popup menus in the status bar didn't become immediately visible;
the change really was made, though. [64848]

So there still IS a line endings pop-up selector? Where is it?
Didn't this used to be in the Show Line Numbers, Soft Wrap Text, etc. menu?
--
------------------------------------------------------------------
Have a feature request? Not sure the software's working correctly?
List FAQ: <http://www.barebones.com/support/lists/bbedit_talk.shtml>
List archives: <http://www.listsearch.com/BBEditTalk.lasso>

[Rich Siegel]

Post by Warren Michelsen
OK, I miss the nice little pop-up we had to easily change line endings
for any open file between Unix, Mac and Windoze. That option seems to
have disappeared and is now only accessible through the far more
cumbersome Save As... -> Options, etc.

Generally, the "Where Did Everything Go?" help describes the
changes in the UI that were made in 8.5/8.6, for customers of
older versions.

R.
--
Rich Siegel Bare Bones Software, Inc.
<***@barebones.com> <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they
sedate me.

[Bruce Van Allen]

Post by Warren Michelsen
So there still IS a line endings pop-up selector? Where is it?
Didn't this used to be in the Show Line Numbers, Soft Wrap Text, etc. menu?

Check the Status Bar -- at the very bottom of the window.

Also, see Preferences -> Text Status Display -> __ Show status bar.

HTH,

- Bruce

__bruce__van_allen__santa_cruz__ca__

[Jayson Garrett]

The subject pretty much says it all. :)

Is there any way in BBEdit 8.6 to make "Show Tab Stops" the default? As
it is now, I have to turn that back on every time I restart the program.

Another question would be: is there any way to save my preferred window
size so that all new windows are created at that size?

Thanks!

[Jim Correia]

Post by Jayson Garrett
Is there any way in BBEdit 8.6 to make "Show Tab Stops" the
default? As it is now, I have to turn that back on every time I
restart the program.

Set the value in Preferences -> Text Status Display.

Post by Jayson Garrett
Another question would be: is there any way to save my preferred
window size so that all new windows are created at that size?

Size/position your window, then choose "Save Default Window" from the
Window menu.

[Rod Buchanan]

Post by Jayson Garrett
Another question would be: is there any way to save my preferred window
size so that all new windows are created at that size?

I believe

Window -> Save Default Window

is what you are looking for.
--
Rod Buchanan
Kelly Supply / KDSI / ISCO
888 382-5670 x220

"US Weekly is to Lindsay Lohan and Nichole Richie roughly what Golf Digest
is to Tiger Woods and Ernie Els."
-- Robert Siegel, "All Things Considered"

[Jayson Garrett]

Thanks folks, that's just what I needed!

Should've noticed those things myself.

Post by Jim Correia
Set the value in Preferences -> Text Status Display.

Post by Jayson Garrett
Another question would be: is there any way to save my preferred
window size so that all new windows are created at that size?

Size/position your window, then choose "Save Default Window" from the
Window menu.

Post by Jayson Garrett
Another question would be: is there any way to save my preferred window
size so that all new windows are created at that size?

I believe
Window -> Save Default Window
is what you are looking for.

[Google Kreme]

Post by Jayson Garrett
The subject pretty much says it all. :)

Please, when you are making a NEW message with a NEW subject about a
NEW topic, don't REPLY to a previous post.
--
Rid yourself of doubt --
or should you?
-George Carlin

[Eric Bergman]

A colleague just alerted me to the fact that text files I sent him
recently have a carriage return (\r or CR) line ending instead of the
newline (\n or LF) they used to have. These are files created in a
Fortran program under OS X 4.8. It may be that this change occurred
when I started working on a MacBook Pro a few months ago. The reason
I'm writing this list about it is the very odd behavior of BBEdit
(8.6 and 8.6.1) with regard to line endings.

BBEdit is set to use unix line endings (\n or LF) by default and
BBEdit shows that unix line endings are being used when I open them.
But if I do a greg search for \n the search fails. If I grep for \r
it finds each line ending. So there seems to be a discrepancy between
what BBEdit says the line endings are and what's actually there.
Then, if I change the line endings to Mac style (\r) and then back to
Unix style, the file stays with Mac style line endings. In other
words, I can't seem to change the line endings using BBEdit.

Since my colleague on a Unix workstation sees the \r line endings
also, I think they really are there, But I cannot understand where
they're coming from, nor why I cannot change them with BBEdit. I must
be missing something rather gross here.

Eric

[Doug McNutt]

BBEdit is set to use unix line endings (\n or LF) by default and BBEdit shows that unix line endings are being used when I open them. But if I do a greg search for \n the search fails.

Try the grep search from Terminal or a BBEdit worksheet.

BBEdit always uses \r for line endings internally. In an AppleScript or search and replace you have to use \r to make things work. Actually I think BBEdit now uses 16 bits per character internally but it's still a 0D and not a 0A or one of those other unicode line ends.

The endings are changed back to the selected values on a save so files on disk should be what you expect.

Is there any possibility that FORTRAN code is creating files with mixed line ends? It would be surprising in a FORTRAN source file but quite possible as the result of a FORTRAN execution especially if the program is reading data from an external instrument.

BBEdit doesn't support mixed line ends. It decides which one comes something like first and treats any others as garbage. BBEdit's Hexdumps are your friend.

<ftp://ftp.macnauchtan.com/Software/LineEnds/FixEndsFolder.sit>
might also be helpful.
--
--> Life begins at ovulation. Ladies should endeavor to get every young life fertilized. <--

[Eric Bergman]

Post by Doug McNutt
Try the grep search from Terminal or a BBEdit worksheet.
BBEdit always uses \r for line endings internally. In an
AppleScript or search and replace you have to use \r to make things
work. Actually I think BBEdit now uses 16 bits per character
internally but it's still a 0D and not a 0A or one of those other
unicode line ends.
The endings are changed back to the selected values on a save so
files on disk should be what you expect.

Thanks for the clarification on that Doug. I suppose there is
explanation of that somewhere in the BBEdit documentation, but I
think it would be helpful to add some info on this subject to the
"Help > Grep Reference" section. It seems natural to assume that
you'd be able to change the line endings and then search for them.

Post by Doug McNutt
Is there any possibility that FORTRAN code is creating files with
mixed line ends? It would be surprising in a FORTRAN source file
but quite possible as the result of a FORTRAN execution especially
if the program is reading data from an external instrument.

I really doubt that my Fortran code would create mixed line endings,
but it's possible that something unexpected is happening because my
compiler (Absoft) is really for a PPC Mac and is running on the Intel
machine courtesy of a patch that has not been thoroughly tested. The
next release is due soon and will be Intel-native.

Eric

[Rob Russell]

These are files created in a Fortran program under
OS X 4.8.

Fortran is available for OS X 10.4?

r

[Maarten Sneep]

Post by Rob Russell

These are files created in a Fortran program under
OS X 4.8.

Fortran is available for OS X 10.4?

yes: http://hpc.sourceforge.net/

[Neil Faiman]

Post by Maarten Sneep

Post by Rob Russell
...
Fortran is available for OS X 10.4?

yes: http://hpc.sourceforge.net/

Also (for Intel): <http://www.intel.com/cd/software/products/asmo-na/
eng/compilers/fmac/267426.htm>

Regards,

Neil Faiman

[Eric Bergman]

Post by Rob Russell
Fortran is available for OS X 10.4?

Hi Rob,

I'm using a commercial compiler from Absoft, but Intel's ifort
compiler is available for Intel Macs, and there are several open
source fortran compilers available. I think they are for PPC Macs.
The Intel-native version of the Absoft compiler is due out this
spring, but the PPC version can be run on Intel Macs with a simple
patch, but executables run under Rosetta. Apple hosts a mailing list
for people interested in using Fortran (fortran-***@lists.apple.com).

Eric