similar to: How to set environment variable XAPIAN_CJK_NGRAM?

The last Debian version I installed on a Desktop was 5.0.0 (released 14-02-09). The provided link indicates the relevant change was initiated in 5.3. > Debian uses /etc/profile.d too (and has done for nearly 8 years): > https://bugs.debian.org/545756

Olly, Thanks a lot! I installed Xapian 1.2.25 on Ubuntu 14.04. How to set environment variable XAPIAN_CJK_NGRAM? I'm a newbie to Xapian. Best wishes, Peter At 2018-02-12 20:00:02, xapian-discuss-request at lists.xapian.org wrote: >Send Xapian-discuss mailing list submissions to > xapian-discuss at lists.xapian.org > >To subscribe or unsubscribe via the World Wide Web,

On Tue, Feb 13, 2018 at 09:32:26AM +0800, Peter Zhao wrote: > I installed Xapian 1.2.25 on Ubuntu 14.04. How to set environment > variable XAPIAN_CJK_NGRAM? I'm a newbie to Xapian. This is really a generic Unix question rather than a Xapian one, and the answer rather depend how eprints gets run. When you're running a program from the shell, you can use env in front of the command

Olly, That's very kind of you to help me. When I used "env XAPIAN_CJK_NGRAM=1 indexer-command" indexer Eprints again, it can search Chinese by character level. But it is not so good for words or phrase level. ICU would be better than CJK. Hope ICU can use soon! Best wishes, Peter At 2018-02-13 11:44:46, "Olly Betts" <olly at survex.com> wrote: >On

On Tue, Feb 13, 2018, at 02:32, Peter Zhao wrote: > At 2018-02-12 20:00:02, xapian-discuss-request at lists.xapian.org wrote: > >There's also a patch to add support for using libicu to find word > >boundaries: > > > >https://github.com/xapian/xapian/pull/114 > > > >That'll get merged soon hopefully (mostly we need to sort out how to > >manage

>> The last Debian version I installed on a Desktop was 5.0.0 (released 14-02-09). Haven't used a Debian version since 2011. > That's actually version 5.3 of the base-files package, rather than > version 5.3 of Debian (there isn't a version 5.3 of Debian). Yes, that's correct. Debian 7 being released after that distro's developers conceded to the integration of

I added the enviroment variable RSYNC_RSH=ssh and every things seems to work fine, but there is no way to tell if rsync is actually using ssh or not?

Dear R developers, after upgrading from R 2.1.1 to 2.2.0 I can't start csh (scripts) anymore. While the following commands work fine > system("tcsh -c pwd") /hom1/users/gloeckler > system("bash -c pwd") /hom1/users/gloeckler > system("ksh -c pwd") /hom1/users/gloeckler csh (in contrast to the shells used above) doesn't give any result:

I've read and followed the README.LLVM file that comes with LLVM-GCC 4.0 Front End source, but got the following error when compiling: configure: error: You must specify valid path to your LLVM tree with --enable-llvm=DIR make: *** [configure-gcc] Error 1 I've done the following in csh before hand: $ setenv LLVMOBJDIR /home/napi/proj/c2jvm/llvm/llvm-gcc/obj Where did I go wrong?

Hello, in /etc/cron.d/test I've this: 50 15 * * * root ( date ; echo "---" ; env ; echo "---" ; set ) >>/tmp/test.txt and I thought I would be shown environment variables which are defined in e.g. /etc/profiles.d/proxy.sh or /etc/profiles.d/proxy.csh but this isn't like this ... where do I have to define e.g. export

xapian-core-1.2.24 Unclear yet about any possible use of patches, either for MSYS/MINGW and/or MSYS2/MINGW, for xapian-core versions(?), but here are sections of the 'configure' and 'make check' logs I output from a MSYS/MINGW (g++ 5.3.0) compile on XP SP3 (32 bit) Home Edition (xapian-core-1.2.24). configure log checking for setenv... no checking for _putenv_s... yes

We have several "csh" batch scripts using "#!/bin/csh -v". It work fine, before Centos 5.5. After cenos 5.5, it will NOT execute and only list history. Anyone know why? Thanks.

Dear Olly Betts, same 32 bit compiler version hardware OS OS version as here (where remotetcp_chert passed and skipped 3) xapian-core-1.2.21.tar.xz http://nurmi-labs.blogspot.com/2015/10/xapian.html ./apitest backend remoteprog_brass: All 225 tests passed, 3 skipped. ./apitest backend remotetcp_brass: All 225 tests passed, 3 skipped. ./apitest backend remoteprog_chert: All 225 tests passed,

On Tue, 2007-10-02 at 14:38 -0700, Tanya M. Lattner wrote: > > I've read and followed the README.LLVM file that comes with LLVM-GCC 4.0 > > Front End source, but got the following error when compiling: > > > > configure: error: You must specify valid path to your LLVM tree with > > --enable-llvm=DIR > > make: *** [configure-gcc] Error 1 > > > >

The sshd server normally builds the environment variables from scratch for a shell process it creates. Except when compile for Cygwin, it simply adds settings to its own set of environment variable settings. A comment in the code says this special case is made because in Cygwin, some of sshd's environment is important for child processes too. I don't run Cygwin (I run Linux), but on my

Greetings, Peter Ross! > problem solved but part of the mystery remains: > It has to do with the root shell!! Oh? I'm no expert, but I could probably explain it. If you're using statically linked shell (busybox comes to mind), you are locked to whatever libs have been linked in at the compile time. Also re: your previous wonder about library name, it may differ between

Having modified software packages' creation scripts some of which use patches, I'm familiar with their use and authorship. It was the specific patch Olly mentioned which I did not know yet if it was needed or indicated. Obviously autoconf is indicated for a bootstrap when xapian is obtained from Github, but, the package maintainer for the MSYS2/MINGW xapian-core1.4.1 had not listed

On 10/2/07, Mohd-Hanafiah Abdullah <napi at axiomsol.com> wrote: > I've read and followed the README.LLVM file that comes with LLVM-GCC 4.0 > Front End source, but got the following error when compiling: > > configure: error: You must specify valid path to your LLVM tree with > --enable-llvm=DIR > make: *** [configure-gcc] Error 1 > > I've done the following

> I've read and followed the README.LLVM file that comes with LLVM-GCC 4.0 > Front End source, but got the following error when compiling: > > configure: error: You must specify valid path to your LLVM tree with > --enable-llvm=DIR > make: *** [configure-gcc] Error 1 > > I've done the following in csh before hand: > $ setenv LLVMOBJDIR

SSH, like RSH before it, invokes a command using the user's shell as specified in the passwd file. In a mixed shell environment with some logins csh-like and some sh-like that is sometimes very difficult to handle. (No, I am not fond of csh.) If I could force a single shell everywhere of course that would be preferable but sometimes I have no control over it. I have often wanted an option