Re: How are we supposed to paste text in XCode?
Re: How are we supposed to paste text in XCode?
- Subject: Re: How are we supposed to paste text in XCode?
- From: Jim Wintermyre <email@hidden>
- Date: Thu, 8 Jun 2006 20:08:59 -0700
I've been having issues with XCode where it won't preserve the line
endings in my files. It's not always reproducible however. I
searched the archives and found this message:
On 15 Feb 2006, at 15:42, Jerry wrote:
On 13 Feb 2006, at 23:42, Steve Mills wrote:
On Feb 13, 2006, at 17:03, David Ewing wrote:
I'm not sure what might be causing nothing to be checked for a
file's line endings. Can you give a little more detail of the
steps to reproduce this? It would probably be better to file a new
bug about this. The bug you seem to be mentioning covers a couple
of other issues, none of which seem to be this one.
I don't know how to make it happen on demand. I always notice it
after a bunch of editing. I'll spend some time tonight and see if I
can find some steps to dupe. At one point I was going to write a
script that constantly checked the line endings of the front
> window, but couldn't figure out how to do that in Xcode. (The
dictionary is really confusing, IMO.)
FWIW, I have the same problem, but don't know how to trigger it.
Files keep losing their line ending state and ending up with Unix
endings even though they were Windows endings to start with. This
drives our source code control system completely bananas.
This sounds like exactly what I'm seeing. I just checked, and if I
select a file in my project and look at it in the inspector, it says
"No Explicit File Encoding" and "No Explicit Line Ending"... and it
looks like this is the case for every file in my tree! I've been
previously using this tree with CodeWarrior, and am converting over
to XCode. The files always open fine in CodeWarrior, and never give
me a message saying that there are inconsistent line endings (they
are always set to Mac, until editing a file in XCode causes it to get
converted to Unix). As mentioned above, this is a major hassle with
the source control system when the file to be checked in has the
wrong line endings. It's not noted when you check the file in (only
when adding a new file), and if you check in a file this way, it
comes back all screwed up as you might expect. I thought whatever
was causing this might have been fixed in XCode 2.3, but it's still
the same.
Any idea what might be causing this? Do I need to somehow go through
and tell XCode to mark every file as having certain line endings? I
do have the Text Editing prefst set to Mac (CR) for both new and
existing files.
Thanks,
Jim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden