Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

设置python trace back 的errorformat无效,并且python默认的自定义compiler失效

Open
#104 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
28/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
vim
Domain
tooling

Research direction

Reproduce the Python traceback through asyncrun using the compiler configuration in the .tasks file. Trace how the task's compiler and errorformat are selected, then verify that the configured Python patterns parse into the quickfix list and that a file-specific compiler is honored.

Written by the indexing model from the issue text.

Description

如标题:
在使用asyncrun执行的时候,可以通过指定文件的编译器的方法设置特定的编译器,用来给quickfix list 提供正确的errorformat。可以执行并且能够正确的解析。asynctasks 指定文件的compiler 无效,在.tasks 文件中设置的
errorformat=
%\sFile\ "%f"\,\ line\ %l\,\ %m,
%
\sFile\ "%f"\,\ line\ %l,
也不起作用。请求帮助!

Dominant language
Vim Script
Stars
936
Forks
32
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from skywind3000/asynctasks.vim

All issues in skywind3000/asynctasks.vim

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.