edf2csv 0.8.0 → 0.8.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.js CHANGED
@@ -280,16 +280,29 @@ export async function main(argv) {
280
280
  And the sentence itself claimed a fact the run is in no position to state: nothing was
281
281
  found because nothing was looked at.
282
282
  */
283
+ /*
284
+ `error: ` and the seven-space continuation, like every other refusal.
285
+
286
+ These two are the last pair printing flush left with no prefix — the shape 0.5.79 took
287
+ off the `--stdout` refusals and 0.7.5 took off the rest, on the reasoning both of those
288
+ set out: stderr is what a script greps, and a failure that does not match `^error:` is
289
+ invisible to the grep that finds every other one. These are the two a batch script
290
+ meets first, since a glob that expands to nothing and a folder that cannot be read are
291
+ both things the shell hands over rather than things anybody types.
292
+
293
+ The sentence splits at its own colon so the greppable head stays one line, which is the
294
+ rule `formatDiagnostics` holds every warning to.
295
+ */
283
296
  if (unreadable.length > 0) {
284
- process.stderr.write(`${wrap(`Nothing could be converted: ${unreadable.length === 1 ? 'that path' : 'those paths'} ` +
285
- `could not be read, so whether ${unreadable.length === 1 ? 'it holds' : 'they hold'} ` +
286
- `recordings is unknown.`)}\n`);
297
+ process.stderr.write('error: Nothing could be converted.\n' +
298
+ detail(`${unreadable.length === 1 ? 'That path' : 'Those paths'} could not be read, so ` +
299
+ `whether ${unreadable.length === 1 ? 'it holds' : 'they hold'} recordings is unknown.`));
287
300
  return EXIT_ERROR;
288
301
  }
289
302
  process.stderr.write(
290
303
  // Escaped, like every other path this prints. These come from the command line, which
291
304
  // makes them no safer: a shell glob expands to whatever the directory holds.
292
- `No EDF or BDF recordings found in ${listed(positionals.map((p) => `"${printable(p)}"`))}.\n`);
305
+ `error: No EDF or BDF recordings found in ${listed(positionals.map((p) => `"${printable(p)}"`))}.\n`);
293
306
  return EXIT_USAGE;
294
307
  }
295
308
  const inputs = expanded.map((entry) => entry.path);