Hi, On Thu, Feb 10, 2022 at 6:57 AM Mark Woods <[email protected]> wrote:
> FWIW, this also bothered me but I've mostly worked around it using an > existing plugin, https://github.com/yssl/QFEnter, which allows quickfix > items to be opened in the previous window, even nofile windows, and > supports custom exclusions (e.g. nerdtree). It remaps <cr> and redefines > :cnext and friends and it mostly just works out of the box. > > :cnext etc. seems a little buggy when the qf window is focused, but > otherwise works fine (this is good enough for me, it's when the quickfix > window is hidden or not-focused that I use :cnext, but YMMV). > > I also added a custom mapping to improve handling of excluded files, > rather than simply error when trying to open in an excluded window, try the > next window, see yssl/QFEnter#26 <https://github.com/yssl/QFEnter/pull/26> > > > When you select an entry in the quickfix window, the file will be opened in a usable buffer. Any buffer with the 'buftype' set is considered as not usable. This is because many plugins mark a buffer as special (by setting 'buftype') and then display some information in the buffer. For example, the taglist/tagbar plugins display the symbol information in a buffer. The same applies for 'terminal', 'prompt' and 'location list' buffers. If these buffers are used for opening a file from the quickfix list, then it will affect the plugin and user workflow. Regards, Yegappan -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7%3D05h58%3De%2BtWi6PicgtWqVggKvSnCKAwOAM8qB4WcJA4A%40mail.gmail.com.
