I have noticed that if I set Line Endings to "CRLF (Windows)" (when collaborating with windows people), line endings are correctly translated to windows style. I forgot to set Textmate back to Unix standard (LF), opened a text file, and when I next saved it it had CLRF line endings. When I changed Textmate back to LF mode, the line endings stayed as CRLF. Even if I delete then re-do all the linebreaks, they are still CLRF. I need to get this sorted right away, so I have used Fink to install dosunix to convert these "CRLFed" documents.
Is this a bug in TextMate? It would be nice if there was some way to set the line endings by file, rather than having an app wide setting. Also, it would be great if this could be put in a bundle (LF->CRLF and vice-versa).
Thanks, Nick Forge
On 16/05/2007, at 1:41 AM, Ciarán Walsh wrote:
On 15 May 2007, at 16:15, Nick Forge wrote:
I forgot to set Textmate back to Unix standard (LF), opened a text file, and when I next saved it it had CLRF line endings.
Do you have “Use for existing files as well” checked in Preferences?
Yes, I do. As I said, TM changed an LF file to CRLF using the preferences setting, but it failed to change them back. As Allan pointed out in his post, I can use Save As to get around this, so it's no big deal. It does however seem that the Preferences setting is a bit inconsistent - changing files in one direction but not the other.
Thanks, Nick
On 16/05/2007, at 11:34 am, Nick Forge wrote:
As Allan pointed out in his post, I can use Save As to get around this, so it's no big deal. It does however seem that the Preferences setting is a bit inconsistent - changing files in one direction but not the other.
And it would still be nice to have this as a widget in the document window, like BBEdit does, along with the file encoding.
I don't know if I'd clutter the document window itself with widgets for one-time settings (lack of widgets was one of the things that made me fall in love with TM). After all, its not something you're going to be changing over & over for a single document. I think maybe a keystroke that displays a sheet or something for document specific settings would be nice, or even an addition to the right click contextual menu. One thing I'd like to see is the ability to set line endings & encoding on a per-project basis. Some projects I work on require collaboration with windows users & others don't. It'd be nice to say that any new file in whatever project would use these attributes.
On May 15, 2007, at 10:38 PM, Tim Mansour wrote:
And it would still be nice to have this as a widget in the document window, like BBEdit does, along with the file encoding.
On 16/05/2007, at 11:22 pm, Cliff Pruitt wrote:
I don't know if I'd clutter the document window itself with widgets for one-time settings (lack of widgets was one of the things that made me fall in love with TM). After all, its not something you're going to be changing over & over for a single document.
That's true Cliff, but there are two uses for a widget: (1) perform an action, (2) provide feedback. Currently there's no quick visual way to tell what line endings or encoding a file has, and that's one thing I'd like. On the other hand, the "Tab Size" that's currently in the status bar is of no use to me at all.
I agree with you wholeheartedly that TM should remain as clutter-free as possible, but the elements that constitute what clutter *is* there should be my choice.
Well, I can't argue with you there. Tab size is pretty useless to me too. I can think of a few ways to provide that visual feedback & not clutter TM. I could see lumping tab size and line endings into the same widget as tab size & letting the widget remember what you would like it display. I could also see giving the option to add more status items to the line / column indicator at the bottom left of the window. For that matter, one thing I like about the OS X terminal app is the ability (although limited) to customize the window title with some useful info. Maybe giving the user the ability to specify custom info into the window title would work. I don't think I'd use it but I don't use but a fraction of what TM has to offer anyway.
On May 16, 2007, at 5:46 PM, Tim Mansour wrote:
That's true Cliff, but there are two uses for a widget: (1) perform an action, (2) provide feedback. Currently there's no quick visual way to tell what line endings or encoding a file has, and that's one thing I'd like. On the other hand, the "Tab Size" that's currently in the status bar is of no use to me at all.
I agree with you wholeheartedly that TM should remain as clutter- free as possible, but the elements that constitute what clutter *is* there should be my choice.
-
Allan Odgaard -
Ciarán Walsh -
Cliff Pruitt -
Nick Forge -
Tim Mansour