Re: [basex-talk] Forcing reading _only_ from standard input

On 23 Aug 2018, at 1:06 am, Christian Grün wrote: > Feel free to check out the latest stable snapshot [1]. > > [1] http://files.basex.org/releases/latest/ Works well for me; thank you.

Re: [basex-talk] Forcing reading _only_ from standard input

Hi Richard, Newlines (i.e., whitespace-only, non-empty strings) were treated identically to the "." file reference. As you can also supply absolute and relative file and directory paths as arguments for the -i flag, the factbook.xml file, which is located in a descendant directory of your current

Re: [basex-talk] Forcing reading _only_ from standard input

On 22 Aug 2018, at 3:44 am, Christian Grün wrote: > I didn’t manage to reproduce this behavior. Do you work with the > latest version of BaseX? 9.0.2. > If yes, could you possibly download a fresh > version (e.g. the zip distribution) and tell us step by step how I can > simulate the behavior?

Re: [basex-talk] Forcing reading _only_ from standard input

Hi Richard, Thanks for reporting this. I didn’t manage to reproduce this behavior. Do you work with the latest version of BaseX? If yes, could you possibly download a fresh version (e.g. the zip distribution) and tell us step by step how I can simulate the behavior? Thanks in advance, all the

[basex-talk] Forcing reading _only_ from standard input

Hi. I have a script in which I process data from standard input like this: VOCAB_WITH_NEW_VOCAB_NOTE="$(echo "$VOCAB" | "${BASEX}" -i - -q $" copy \$c := . modify ... etc. etc. The script has been working fine. However, due to a defect in an earlier line in the script, during one test run,