[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Advice on co with mac for file type/creator

From: Ryan Schmidt <subversion-2006d_at_ryandesign.com>
Date: 2006-12-08 22:40:09 CET

On Dec 8, 2006, at 15:19, David Pratt wrote:

> Ryan Schmidt wrote:
>> On Dec 5, 2006, at 11:33, David Pratt wrote:
>>> Hi. When I co from a svn repository on my mac, the file type and
>>> creator are most often empty. I realize I can batch process
>>> folders to set types based on extensions but I am wondering if
>>> someone has a better solution for this - or can advise on how
>>> they cope with this. Many thanks.
>> Not really. Subversion does not store type / creator information,
>> or resource forks. It stores the data fork only.
>> On Mac OS X, I have not had to worry about type / creator
>> information in many years; are you sure you have to? For example,
>> if you have a bunch of, say, .txt files, and by default these open
>> into, I don't know, TextEdit maybe, and you would rather use
>> BBEdit, then just click one of the .txt files in the Finder, Get
>> Info on it, in the Open With section select BBEdit, then click the
>> Change All button, and from then on, all .txt files will open into
>> BBEdit. No need to muck with type / creator codes ever again.
>> Does that help you?
> Hi Ryan. Thank you for your reply. I do not generally worry about
> creator types in mac either since file extensions are good enough for
> opening applications. The trouble I had was more to do with BBEdit.
> It did not want to do multi folder search/search replace on files
> where
> the type is empty. I managed to solve this problem today by adding
> file extension mappings to my BBEdit Language preferences.
> Everything works the way I want. Just need to add any additional
> mappings a time goes on.
> A second issue I ran into recently is using a dotted folder name -
> using a namespace together with the word menu like 'mynamespace.menu'.
> Since I am developing in python, I create folders in subversion to
> keep namespace packages sorted out. This feature is common with
> repositories like svn.zope.org and other python repositories also.
> If I do a check out, it thinks the folder is a mac app file and not
> a folder. The .menu is what mac interprets as part of an app. This
> type of folder naming convention is not an issue on unix or windows
> (of course) and only appears on a check out. Not sure anything can
> be done about this one though. Many thanks.

True, on Mac OS X, directories whose names end in ".menu" are
considered to be MenuExtra bundles. The only suggestion I can make is
that if you intend to use these directories on Mac OS X, do not put
".menu" at the end of their names. I realize that the Zope developers
may be reluctant to change this. Unfortunately, if they do not remove
".menu" from the names of their directories, developing Zope on Mac
OS X will be exceptionally bizarre -- that is, if you intend to use
the Finder and standard save/open panels to navigate. If instead you
restrict yourself to the Terminal, bundles do not pose a problem.
Also, Finder replacements such as Path Finder offer the ability to
easily navigate into bundles, thus also alleviate the problem.

To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 8 22:40:53 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.