简体   繁体   English

git忽略Mac OS X上带空格的目录

[英]git ignore for directories with spaces on Mac OS X

I'm trying to add some patterns to my .gitignore file to ignore *.mode1v3 and *.pbxuser files generated by Xcode. 我正在尝试将一些模式添加到我的.gitignore文件中,以忽略Xcode生成的* .mode1v3和* .pbxuser文件。 However, my app name has a space in it, so the files I want to ignore are in the Foo Bar.xcodeproj/ directory. 但是,我的应用程序名称中有一个空格,因此我要忽略的文件位于Foo Bar.xcodeproj/目录中。 Adding variants of these patterns don't seem to work: 添加这些模式的变体似乎不起作用:

*.mode1v3
Foo Bar.xcodeproj/
Foo Bar.xcodeproj/*.mode1v3
Foo Bar.xcodeproj/username.mode1v3

What should the .gitignore patterns be? .gitignore模式应该是什么?

AFAIK spaces aren't treated specially; AFAIK空间不经过特殊处理; neither Pro Git nor gitignore(5) nor fnmatch(3) mentions them. Pro Git和gitignore(5)以及fnmatch(3)提及它们。 Anyway the first pattern *.mode1v3 is totally sufficient; 无论如何,第一个模式*.mode1v3是完全足够的; patterns without slashes are applied to all subdirectories. 没有斜杠的模式应用于所有子目录。 If you want additional ignore patters for a specific subdirectory, just place a dedicated .gitignore in that directory. 如果您想要特定子目录的其他忽略模式,只需在该目录中放置一个专用的.gitignore

Have you tried escaping any spaces in the folder or file names with backslashes? 您是否尝试使用反斜杠转义文件夹或文件名中的任何空格?

*.mode1v3
Foo\ Bar.xcodeproj/
Foo\ Bar.xcodeproj/*.mode1v3
Foo\ Bar.xcodeproj/username.mode1v3

Also, are these files already being tracked by git? 此外,这些文件是否已被git跟踪? From man gitignore : 来自man gitignore

A gitignore file specifies intentionally untracked files that git should ignore.
Note that all the gitignore files really concern only files that are not already
tracked by git; in order to ignore uncommitted changes in already tracked files,
please refer to the git update-index --assume-unchanged documentation.

Additionally, here are some of the patterns discussed in man gitignore : 此外,以下是man gitignore讨论的一些模式:

o   If the pattern ends with a slash, it is removed for the purpose of the
    following description, but it would only find a match with a directory. In
    other words, foo/ will match a directory foo and paths underneath it, but will
    not match a regular file or a symbolic link foo (this is consistent with the
    way how pathspec works in general in git).

o   If the pattern does not contain a slash /, git treats it as a shell glob
    pattern and checks for a match against the pathname relative to the location of
    the .gitignore file (relative to the toplevel of the work tree if not from a
    .gitignore file).

o   Otherwise, git treats the pattern as a shell glob suitable for consumption by
    fnmatch(3) with the FNM_PATHNAME flag: wildcards in the pattern will not match
    a / in the pathname. For example, "Documentation/*.html" matches
    "Documentation/git.html" but not "Documentation/ppc/ppc.html" or
    "tools/perf/Documentation/perf.html".

o   A leading slash matches the beginning of the pathname. For example, "/*.c"
    matches "cat-file.c" but not "mozilla-sha1/sha1.c".

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM