Closed dgudim closed 10 months ago
Only inline sabbrevs, which are defined with -i
, are affected by that option. Please define it in this way:
ble-sabbrev -i "~proj=$HOME/Documents/shared/_projects/"
But it will also complete somestring~proj
right?
Yeah, it does. Ok, thanks for quick response anyway. I though this would work for all sabbrevs. Is it possible to add a similar option for not inline ones?
But it will also complete
somestring~proj
right?
Right.
Is it possible to add a similar option for not inline ones?
It's possible if it is really needed by users, but what is your use case of not inserting a space after e.g. word sabbrevs? The word sabbrevs (which are the default sabbrevs when the type is unspecified) are intended to generate a single command-line word separated by a space. So a global option that disables suffixing space for all the sabbrevs doesn't seem useful. Specifically for the example of ~proj
you provided, I suspect what you want would be actually defining it without the final slash,
ble-sabbrev -i "~proj=$HOME/Documents/shared/_projects"
and press /
after typing ~proj
to continue to write filenames or subdirectory names. Here, notice that magic-slash
is bound to the key /
by default.
Oh, I somehow missed the /
part, many thanks :)
ble version: Bash version:
If I understand correctly,
inline-sabbrev-no-insert
should disable insertion of space after completing sabberv, but it still inserts it for metyping ~proj and pressing space still inserts a space after .../shared/_projects/