search for: nspace

Why does inserting an empty quote ("") into a rsync command cause the current directory to be backed up? Not sure if this is a UNIX-syntax question or rsync-syntax question. Code: #!/bin/sh echo "\nspace between quotes has no effect; only music is backed up:" rsync -ilrtn " " /home/wolf/music /backups/backup1 echo "\nempty quotes backs up current directory and music:" rsync -ilrtn "" /home/wolf/music /backups/backup1 Thank you.

...> > of the name is drop by swig. There is also some error with define > > macro in .i files, but with minor change all work perfectly. I had a look and I think that at least the macro changes are only needed because the golang branch hasn't been updated for ages. SWIG has a "%nspace" feature to support wrapping namespaces, but it isn't implemented for Go yet. However, Xapian's C++ API doesn't make much use of namespaces beyond the top-level Xapian namespace, and I'd expect in Go that the Go package name would fulfil the same purpose as the C++ namespace n...

...meanpart <- exp(tr.totpart.pruned$frame$yval)-1 tr.totpart.pruned$frame <- cbind(tr.totpart.pruned$frame, meanpart) and thought this was good because summary(tr.totpart.pruned$frame) lists meanpart as one of the columns. BUT when I tried plot(tr.totpart.pruned, compress = T, uniform = T, nspace = .5, margin = .1) text(tr.totpart.pruned, splits = T, all = T, pretty = 0, digits = 4, use.n = T, fancy = T, label = meanpart) I got an error Error in text.rpart(tr.totpart.pruned, splits = T, all = T, pretty = 0, : Label must be a column label of the frame component of the tree...

...p by swig. There is also some error with define > > > macro in .i files, but with minor change all work perfectly. > > I had a look and I think that at least the macro changes are only needed > because the golang branch hasn't been updated for ages. > > SWIG has a "%nspace" feature to support wrapping namespaces, but it > isn't implemented for Go yet. However, Xapian's C++ API doesn't make > much use of namespaces beyond the top-level Xapian namespace, and I'd > expect in Go that the Go package name would fulfil the same purpose > as...

This is probably more useful to the general list. Thanks for the update, Dave — was this based on the previous golang bindings? J > Begin forwarded message: > > From: Dave Courtois <dave.courtois60 at gmail.com <mailto:dave.courtois60 at gmail.com>> > Subject: GoXapian > Date: 27 October 2018 at 15:27:09 BST > > Hi there just a little word to tell you that