Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
bash: warning: command substitution: ignored null byte in input
See original GitHub issueAfter installing argcomplete I get the following warning from bash frequently. Everything still works but this is very annoying. It happens the instant I hit tab to auto-complete and it happens about 10% of the time. Any idea what’s causing this?
bash: warning: command substitution: ignored null byte in input
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
Get rid of "warning: command substitution: ignored null byte in ...
Read ignoring all NULs. This gets you equivalent behavior to the newer (4.4) release of bash. model=$(tr -d '\0' </proc/device-tree/model).
Read more >How do I ignore "command substitution: ignored null byte in ...
@Vikki, Because Bash doesn't support NUL bytes in values. It internally uses C-style strings, where the NUL byte marks the end of the...
Read more >How do I fix warning: command substitution: ignored null byte ...
This warning appears to be a new feature in Bash-4.4 - see for example Command substitution with null bytes generates warning.
Read more >warning: command substitution: ignored null byte in input #77
Good morning, I installed asus-fan-control on my Asus K53SC, my os is arch-linux, and when I execute sudo asus-fan-control I get these ...
Read more >command substitution: ignored null byte in input : r/bash - Reddit
hello, when a certain file does not contain what i grep for, I always get this warning message.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Released in v1.11.0, please test.
Indeed, the problem is fixed in my case after the most recent release! Thanks! Important note is that I not only needed to update the package, but afterwards also the initialization i.e.
activate-global-python-argcomplete --dest=- > file.