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.

Sign up for GitHub

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

Jump to bottom

TypstWatch should show errors #42

Closed
kaushikcfd opened this issue Jul 26, 2023 · 3 comments
Closed

TypstWatch should show errors #42

kaushikcfd opened this issue Jul 26, 2023 · 3 comments
Labels
enhancement New feature or request

Comments

@kaushikcfd
Copy link

If there is a compilation error (say invoking an unknown symbol) the observed behavior is that the pdf does not get updated. Maybe, like vimtex, it makes sense to show the error in the statusline?

Happy to contribute towards it, if it's not already implemented and we can agree that this is a good direction.
@kaarmu
Copy link
Owner

kaarmu commented Jul 27, 2023

Thank you for the input! I think this is a good feature to have, although when using :make or vim-dispatch I think the errors show up in the quicklist. I never became too familiar with Vimtex so I don't know how exactly the setup was there. What is your (current/ideal) workflow? Would love any help possible!

@kaarmu kaarmu added the enhancement New feature or request label Jul 27, 2023
@PhyX-Meow
Copy link

PhyX-Meow commented Oct 14, 2023 •
edited
Loading

I think the error should show some where when using TypstWatch. At least in statusline, better at the precise place it occurs.
Currently I completely can not know if it encountered into some error until I find the pdf is not updated.

kaarmu added a commit that referenced this issue Oct 16, 2023
@kaarmu
Progress on #42
09fcd72 
This feature is now working on normal vim. When there is an error
typst.vim will populate the QuickFix list and open it. When the
errors have been fixed, the QuickFix list will be closed.

Some problems remain for neovim. I think it is only minor fixes due
to API differences.
This was referenced Oct 18, 2023
Closed
Closed
@kaarmu
Copy link
Owner

kaarmu commented Apr 14, 2024

Following up here now, I have this experience in both vim and neovim. If there is something you miss then we can open a new issue for that specifically.

@kaarmu kaarmu closed this as completed Apr 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kaushikcfd @PhyX-Meow @kaarmu