faho · GitHub

faho

@faho faho mentioned this pull request

May 5, 2018

Closed

@ridiculousfish

This introduces a new type features_t that exposes feature flags. The intent
is to allow a deprecation/incremental adoption path. This is not a general
purpose configuration mechanism, but instead allows for compatibility during
the transition as features are added/removed.
Each feature has a user-presentable short name and a short description. Their
values are tracked in a struct features_t.
We start with one feature stderr_nocaret, but it's not hooked up yet.
This teaches the status command to work with features.
'status features' will show a table listing all known features and whether
they are currently on or off.
`status test-feature` will test an individual feature, setting the exit status to
0 if the feature is on, 1 if off, 2 if unknown.
This introduces a new command line option --features which can be used for
enabling or disabling features for a particular fish session.
Examples:
  fish --features stderr-nocaret
  fish --features 3.0,no-stderr-nocaret
  fish --features all
Note that the feature set cannot be changed in an existing session.
This partially reverts  5b489ca , with
carets acting as redirections unless the stderr-nocaret flag is set.
This flag is off by default but may be enabled on the command line:
fish --features stderr-nocaret
This enables users to opt in (or out) of specific features by setting
the fish_features environment variable.
For example `set -U fish_features stderr-nocaret` to opt into removing the
caret redirection.
This adds a feature flag for controlling whether question marks are globs.
It is not yet hooked up.
This partially reverts  6e56637  and fish-shell#4520
by bringing back the ? wildcard, guarded by the qmark-noglob feature flag.
This is a convenience over fish_features().test()
Replace these with 2>

ridiculousfish added a commit to ridiculousfish/fish-shell that referenced this pull request

May 6, 2018

@ridiculousfish

@ridiculousfish

@faho faho mentioned this pull request

May 8, 2018

Closed

@ridiculousfish

@github-actions github-actions Bot locked as resolved and limited conversation to collaborators

Apr 16, 2020

Read the original on github.com ↗