Brian May wrote:. ...
I notice with a recent baz archive it is:backup ^.*(~|\.~[0-9]+~|\.bak|\.sw(o|p)|\.orig|\.rej|\.original|\.modified|\.reject|\.(o|a|so|core|so(\.[[:digit:]]+)*))$|^core$ unrecognized ^$ What is the difference between a .swo and a .swp file?
Both are vim backup/temporary files. But if .swp exists, usually vim creates a new one with .swo. And if that exists it uses .swn, I'm not sure how far that goes, because I've only seen .swn.This happens if you open the same file twice, or if you open the file, and your machine dies/network connection dies.
I guess my above quotes above serve to demonstrate different people have different opinions of the usefulness of the "unrecognized" category.
Unrecognized means give an error (generally). Backup means ignore it entirely. It was Tom's original belief that trees should be clean before you commit. (And that you should generally build outside the source tree anyway.) The bazaar people decided that blocking a commit just because there was a .o file in the tree was poor form, and did away with it. (Same thing for dot files, and a few other types, tla mainline by default complains if you have a dot file in your path). John =:->
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
