all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuta Yamada <sleepboy.zzz@gmail.com>
To: emacs-devel@gnu.org
Subject: feature request: public API to get new flymake's errors/warnings
Date: Mon, 16 Oct 2017 09:41:16 -0700	[thread overview]
Message-ID: <CAK=dAsPchum1ZQiqY1rdk4Ydgx2RNjo8ar=m6Fcdvu4dGyyFkQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 819 bytes --]

Hello Emacs devel.

First of all, thank you to rewritten of flymake!

I'm an emacs' package maintainer of flycheck-tip and flycheck-nimsuggest
(nim language's flycheck backend) and I could convert to
flycheck-nimsuggest.el for flymake very easy.

But, as for flycheck-tip (which show flycheck/flymake's errors and warning
on a tooltip), or other
flymake related packages, could you support public API to get errors and
warnings object? (I mean a public function for it)

I think I can implement and extract data if I steal some stuff from
`flymake--diagnostics-buffer-entries', but having public API is better
because I don't feel the fear of devel's change.

just FYI I was using following flymake functions to get the data:

---
(flymake-find-err-info flymake-err-info (line-number-at-pos))
---

Regards,
Yuta Yamada

[-- Attachment #2: Type: text/html, Size: 1086 bytes --]

             reply	other threads:[~2017-10-16 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 16:41 Yuta Yamada [this message]
2017-10-16 18:23 ` feature request: public API to get new flymake's errors/warnings João Távora
2017-10-17 14:32   ` Yuta Yamada
2017-10-19 11:36     ` João Távora
2017-10-19 12:31       ` Yuta Yamada
2017-10-20  6:53       ` Eli Zaretskii
2017-10-20  9:10         ` João Távora
2017-10-20 12:47         ` Stefan Monnier
2017-10-20 13:40           ` Yuri Khan
2017-10-20 13:49           ` João Távora

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK=dAsPchum1ZQiqY1rdk4Ydgx2RNjo8ar=m6Fcdvu4dGyyFkQ@mail.gmail.com' \
    --to=sleepboy.zzz@gmail.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.