On 12/29/2017 10:55 AM, Bo Berglund wrote:
On Fri, 29 Dec 2017 19:05:06 +0100, Bo Berglund
<bo.bergl...@gmail.com> wrote:

On Fri, 29 Dec 2017 09:24:10 -0800, David Chapman <dcchap...@acm.org>
wrote:
But if I add the content of my cvsignore file to the config file as a
whitespace separated list on one line that line becomes VERY log (over
600 chars).
Can I put the info in separate lines?

It turns out that enabling this option by removing the # character
makes SmartSvn barf when I want to check out a project!
So it is necessary also to remove all whitespace *before* the
global-ignores text. After this whitespace is permissible.

This is how my file looks now for ignores (the ignore globs are all on
one line, the newsreader has added the line breaks):

[miscellany]
### Set global-ignores to a set of whitespace-delimited globs
### which Subversion will ignore in its 'status' output, and
### while importing or adding files and directories.
### '*' matches leading dots, e.g. '*.rej' matches '.foo.rej'.
  global-ignores = *.o *.lo *.la *.al .libs *.so *.so.[0-9]* *.a  *.pyc
*.pyo *.a  *.aps  *.bak  *.BAK  *.bpt  *.bro  *.bsc     *.cdb  *.cfg
*.cgl  *.class  *.compiled  *.clw  *.db  *.dbg  *.dcu  *.DCU  *.ddp
*.dsk  *.dti   *.err  *.exp  *.gid  *.gz        *.identcache  *.ilk  *.jar
*.lnk  *.local  *.log  *.lps  *.lrt     *.mod  *.MOD  *.ncb  *.NCB  *.ocx
*.OPT  *.opt  *.pch  *.pjt      *.plg  *.PLG  *.pdb  *.PDB  *.ppu  *.o
*.obj  *.OBJ  *.or      *.rsj  *.rst  *.sbr  *.scc  *.SID  *.sln  *.tar
*.tds  *.tlh    *.tli  *.trg  *.vbw  *.zip  __history  bak  *.~*  .#*

I guess it is not valid to split the list on several lines in they
config file?



I tried to use a backslash character as a line continuation for "global-ignores" and it did not work.  Apparently you are stuck with a very long line here.  I don't know if anyone else has complained about it or if an enhancement request would be seen favorably by the Subversion developers.

You could shorten the line a bit by reducing the number of spaces between words, and on Windows the names should be case-insensitive so that you can remove entries that differ only in case.

--
    David Chapman      dcchap...@acm.org
    Chapman Consulting -- San Jose, CA
    EDA Software Developer, Expert Witness
    www.chapman-consulting-sj.com

Reply via email to