This doesn't affect it inside of one, try
echo -n (echo -n 1 | string collect -N).
Why does fish have a file descriptor for its own file descriptor directory?
that makes sense
thank you
It seems
kill (jobs -p) does the job
What about to introduce any environment variable to control what completions are allowed to do and what not? For instance when this variable ($fish_disable_smart_complete or another name) is not set nothing changes (for backward compatibility) and otherwise:
--conditioncomplete option is not allowed because potentially it can run for a long time- command substitutions are not allowed in
--argumentsfor the same reason
What do you think about it?
This would also be a global option for all completions, which would break completions that are fast enough just because some others aren't.
hello all... I'm finding it surprisingly difficult to run a detached process and save the PID... I'm trying to do something like
eval $cmd &; echo $last_pid but this really, really does not seem to want to work...
that wasn't my issue, actually I figured it out: the command I was trying to run was all in one string, I needed to string split it an additional time.
Unfortumately this didn't solve what seems to be a much deeper problem of Xorg absolutely not wanting to do what I'm trying to do here lol
I noticed the new fish breaks compat with mc, is it just me or has someone else seen that?
@andrewsh:matrix.org It's an mc bug - it tries to extract the first line of the prompt and is overly simplistic in doing so. https://midnight-commander.org/ticket/4258
The only sure way to get a bug fixed now is to do it yourself.
I have for now downgraded fish back to the version where it works
anyway, added the details to the Debian bug report, hopefully the maintainer can have a look and figure something out
@faho: thanks!
Why do these both output the same thing? According to my understanding of character escapes in single quotes, the \$ should result in no regex backreferencing happening
$ string replace -r '(\w+)\s+(\w+)' '$2 $1 $$' 'left right'
right left $
$ string replace -r '(\w+)\s+(\w+)' '\$2 \$1 $$' 'left right'
right left $
@PatrickF1 #5474 - unfortunately
string replace has a superfluous round of unescaping in the replacement part so you'll have to double up the slashes one more time. There's no great way of fixing it so we've introduced a feature flag until we figure out how to detect it and warn about it.
btw https://fishshell.com/docs/current/language.html#future-feature-flags says "round of escaping", but that should read "round of unescaping right"?
"un"escaping is a pretty technical term, it's when you turn
$ into "expand this" and \$ into $. If it does too much unescaping that means you need more escaping. I do not believe this subtlety helps any in the explanation, so we've left it as "escaping".
HN
had avoided it for a while due to non-posix
hard to step out of decades of relying on posix shells...
If it's going to take more than a few lines/functions, it's getting done in python or a DSL instead of bash