Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to display __roast_headers__ and __roast_pretty__ window in same time #9

Open
JulioJu opened this issue May 2, 2019 · 3 comments

Comments

@JulioJu
Copy link

JulioJu commented May 2, 2019

Hi !

Maybe it could be cool to have an option to display in same time the two windows __roast_headers__ (maybe in small, to see at least response header) and __roast_pretty__ ? Don't know if its difficult to implement…

It's just an idea, but maybe not very interesting… Don't know.

Thanks in advance for your answer and I understand if you close the current issue ;-)

@JulioJu JulioJu changed the title Display __roast_headers__ and __roast_pretty__ window in same time Option to display __roast_headers__ and __roast_pretty__ window in same time May 2, 2019
@sharat87
Copy link
Owner

sharat87 commented May 3, 2019

This will be a bit challenging to implement. I think if I get the custom renderers to work, then we can create a custom renderer that shows the headers and the response body at the same time. May be something like that would work better in your case. Not sure, but definitely nice to have.

@JulioJu
Copy link
Author

JulioJu commented May 9, 2019

@sharat87 or maybe simply add an option to automatically split the right pan between two windows,
__roast_headers__ and __roast_pretty__. Vertical size of __roast_headers__ could be calculated thanks the number of lines of its === Response Headers === section and resize automatically thanks trigger the command :resize XX.

@JulioJu
Copy link
Author

JulioJu commented May 27, 2019

It's better to keep __roast_pretty__ in an independent buffer because actually Vim doesn't manage well several filetypes in a same buffer. See for instance neovim/neovim#7866 . When tree sitter will be implemented on NeoVim, IMHO implement a custom renderer could be a solution, but not actually. Currently I believe it's better to keep the buffer __roast_headers__ independent. I don't like https://github.com/diepm/vim-rest-console because of this, all is meld in one buffer and the render is not very good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants