let 'previewpopup' like 'completepopup'#18873
Conversation
|
this needs a bit of updates to the documentation, I guess we need to also link from 'previewpopup' (this should also document what values can actually be set) to 'pumborder'?. Also, can you please update the tests for all possible option values that this allows then? |
17d111e to
af93d70
Compare
|
Sorry, I finally found some time to look this pr.
I've use some time understanding how to use and create test cases, i will be update it later. |
f5e3f88 to
fae0561
Compare
|
Thanks |
|
After this patch, my windows build (clang 21.1.8) fails with a linker error because This PR inserts a call to In other parts of the code A simple fix (that works for me) is to add did_set_previewpopup(optset_T *args UNUSED)
{
if (parse_previewpopup(NULL) == FAIL)
return e_invalid_argument;
#if defined(FEAT_QUICKFIX)
popup_close_info();
#endif
return NULL;
}Cheers |
|
thanks, i include it |
Problem: Compile error in did_set_previewpopup() when quickfix
feature is not included (John Marriott, after v9.2.0051)
Solution: Add ifdef FEAT_QUICKFIX (John Marriott)
related: #18873
Signed-off-by: John Marriott <[email protected]>
Signed-off-by: Christian Brabandt <[email protected]>

I’ve seen many separate checks in the code specifically for the preview popup window, blocking certain parameters. I’m not familiar with Vim’s codebase, and I don’t really understand why this is done. My understanding is that a preview popup window is just a normal popup window (please correct me if I’m wrong), I also don’t really get why those checks are needed. This PR is meant to address the issue in #18826 and allow
previewpopupto have richer configuration, so I removed some of the checks that tested whether a popup was a preview. I’m not sure what side effects this might cause.