[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: feature request: public API to get new flymake's errors/warnings
From: |
Stefan Monnier |
Subject: |
Re: feature request: public API to get new flymake's errors/warnings |
Date: |
Fri, 20 Oct 2017 08:47:01 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) |
>> +Since overlays also support arbitrary keymaps, you can this along with
> ^^^^^^^^^^^^
> The "use" part is missing.
Maybe we should just lobby for the new verb "to this", as in "boy, he
really thissed it hard!"
>> +(defun flymake-diagnostics (&optional beg end)
>> + "Get Flymake diagnostics in region comprised between BEG and END.
> Same comment here about the "comprised between" part.
I don't have an opinion on what's the best phrasing for that in the
Texinfo doc, but in the docstrings, we traditionally just say
Get flymake diagnostics in region BEG..END
-- Stefan
- feature request: public API to get new flymake's errors/warnings, Yuta Yamada, 2017/10/16
- Re: feature request: public API to get new flymake's errors/warnings, João Távora, 2017/10/16
- Re: feature request: public API to get new flymake's errors/warnings, Yuta Yamada, 2017/10/17
- Re: feature request: public API to get new flymake's errors/warnings, João Távora, 2017/10/19
- Re: feature request: public API to get new flymake's errors/warnings, Yuta Yamada, 2017/10/19
- Re: feature request: public API to get new flymake's errors/warnings, Eli Zaretskii, 2017/10/20
- Re: feature request: public API to get new flymake's errors/warnings, João Távora, 2017/10/20
- Re: feature request: public API to get new flymake's errors/warnings,
Stefan Monnier <=
- Re: feature request: public API to get new flymake's errors/warnings, Yuri Khan, 2017/10/20
- Re: feature request: public API to get new flymake's errors/warnings, João Távora, 2017/10/20