3

This seems to have randomly started a few days ago. It used to be fine to run fish shell from Ubuntu bash for Windows. But suddenly when I hit Tab for autocomplete, it barfs with:

The file "x86" is not executable by this user in command substitution called on standard input

Also, when I just type x86 it doesn't actually run a command, but it tells me:

The file "x86" is not executable by this user

However, which x86 outputs nothing.

Any clue what in the world could be going on here?

Improve this question
2
  • whats your pwd? are you on or evaluating a path to c:\program files (x86)\ ? bash is likely to parse that as multiple file names. windows should never have allowed whitespace in filenames...
    – Frank Thomas
    Commented Nov 22, 2017 at 19:36
  • Ah, it looks like ` /mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common` (among a few others) is on my PATH. Is there a way to either eliminate those, as they're not even remotely relevant for the subsystem.... I mean, I could manually set the PATH of course
    – Wayne Werner
    Commented Nov 22, 2017 at 21:50

2 Answers 2

Reset to default
2

This was a bug present in fish and fixed in version 2.3.0 - if it is still present in later versions, a report would be greatly appreciated.

You can install a newer version from the Ubuntu PPA repositories if the version installed by apt-get is too old.

Improve this answer
1
  • You r question solves the problem, mine just rambles :)
    – Vedant
    Commented Nov 25, 2017 at 3:16
0

The issue here is in completer_t::complete_cmd, which invokes expand_string. This is a very general function that expands things like wildcards, process expansion, variable expansion, etc.

It's surely wrong to do these expansions in the components of $PATH.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .