Display richer error message

Ouverte
  • Quelque chose ne va pas ?
#403 1 commentaire 1 réaction 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
43/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
rust, vim
Domaine
developer-experience, tooling

Piste de recherche

Start by locating rust.vim's makeprg and errorformat configuration, then check how its diagnostics are parsed. The report suggests using Cargo's human message format for richer multiline details, but leaves open whether to change the command format or parser. Done means location list entries show the useful diagnostic context from the example; test against the provided Cargo errors.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Tested with vim 8.2 and nvim 0.5.0-dev on fedora 30, with the current master of rust.vim (9e6836f44528312171b21a78d9228c88615f63ae) and the current master branch of syntastic (b3e2d8470fddc7f2b598f09023ebc5045a3fb1fd)

Steps to reproduce:

Type some rust code and wait for the error to be displayed in the location list (or open it manually with :lopen)

Currently the location list windows looks like this:

lib/dice_system.rs|34 col 5 error| struct is not supported in `trait`s or `impl`s                                                                                                                                                             
lib/dice_system.rs|41 col 5 error| associated type in `impl` without body
lib/dice_system.rs|41 col 23 error| bounds on `type`s in `impl`s have no effect
lib/dice_system.rs|53 col 5 error| associated function in `impl` without body
lib/dice_system.rs|54 col 5 error| associated function in `impl` without body

This is the same output that if you do manually (in command mode):

set makeprg=cargo\ check\ --message-format=short
make
copen

If I do change it to

set makeprg=cargo\ check\ --message-format=human

I get much nicer details

||     Checking pyrite v0.1.0 (/home/rmoussu/perso/brolisteam/pyrite)
lib/dice_system.rs|34 col 5 error| struct is not supported in `trait`s or `impl`s                                                                                                                                                             
||    |
|| 34 |     struct DiceInformation {
||    |     ^^^^^^^^^^^^^^^^^^^^^^
lib/dice_system.rs|41 col 5 error| associated type in `impl` without body
||    |
|| 41 |     type DiceDisplay: Display;
||    |     ^^^^^^^^^^^^^^^^^^^^^^^^^-
||    |                              |
||    |                              help: provide a definition for the type: `= <type>;`
lib/dice_system.rs|41 col 23 error| bounds on `type`s in `impl`s have no effect
||    |
|| 41 |     type DiceDisplay: Display;
||    |                       ^^^^^^^

I didn't found a way to specify the --message-format used by rust.vim It is possible? I am willing to do a PR, but I don't know where to look. I can also modify the errorformat used by rust.vim to correctly parse the multiline error but I don't know either where to look.

Using rust.vim + syntastic is much nicer that calling :make by hand since you have instant feedback, and it also works even if you have autochdir set.

I assume it's not possible to add colors (I don't think it's possible to display ANSI colors in vim – I have no idea if it's possible for neovim). If it was possible, then ideally --message-format=json-diagnostic-rendered-ansi should be used.

Langage dominant
Vim Script
Étoiles
4.2k
Forks
323
Aucune PR mergée en 30 j

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de rust-lang/rust.vim

Toutes les issues de rust-lang/rust.vim

Issues similaires

Plus d'issues DevTools

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.