Add option `g:vrc_enable_header_buffer` to filter curl header into a separate buffer

[diepm]

Thanks for this great idea. Please consider my comments below.

• I suggest displaying the headers in a split buffer, probably on top of the output buffer. It's so that everything is visibly clear, and we don't have to worry about the mapping to switch back and forth. This "mini" display would be similar to the quickfix window when we set vrc_show_command to 1. The only difference is that we might want this header buffer to be a regular buffer.
• Do you think it makes sense to have the buffer-scoped header buffer name like with the output buffer where a user can set an output buffer name for each "rest" buffer.
• Please update the help file as well (you might want to do that after all code review is done).
• Indentation is 2 spaces.

[hiberabyss]

Hi @diepm,

For your first point, we do not care about header content in many cases, showing it in a separate window may be a waste of the space to display response content.

From my experience, the reason I enable curl header is to get the response filetype and have a see of the http status code if there is any error.

How do you think about this?

I will update source code according your comments.

Thanks!

[diepm]

We can add two options,

• vrc_hide_headers: will hide the headers if they present.
• vrc_split_headers: will display the headers part in a split buffer.

Of course these two options only take effect if the response includes headers (i.e., with -i option). The "hide" option has a higher priority than the "split" one since if the user wants to hide the header section, we don't have to display it.

What do you think?

[hiberabyss]

I think it's a little complicated to add two options for this feature. Maybe we could add one first, and then add another one if there is the demand.