You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah it does nothing and we are aware of it. We are actually currently reworking how the whole layout configuration works #922 and its probably hitting master at the beginning of next week. We are trying to only break backwards compatibility once so it takes some time. We are providing a changelog to help adjusting and result_width is named there:
width is now handling it. See for example: :help layout_strategies.horizontal() or any other strategy you want. Also you should read :help telescope.defaults.layout_config
Description
Expected Behavior
The behavior I expect is to reduce the width of the results box, the default width leaves empty space.
Actual Behavior
I think
results_width
is what I need but when I change its value I don't see any change. Is there something I am doing wrong?Details
Reproduce
results_width
Environment
NVIM v0.5.0-dev+1421-ga72dfec85
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-11 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compiled by runner@fv-az68-463
Features: +acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/share/nvim"
Run :checkhealth for more info
Configuration
The text was updated successfully, but these errors were encountered: