[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: |
João Távora |
Subject: |
Re: feature request: public API to get new flymake's errors/warnings |
Date: |
Fri, 20 Oct 2017 14:49:59 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (gnu/linux) |
Stefan Monnier <address@hidden> writes:
>>> +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!"
I admit to being easily thistracted...
> Texinfo doc, but in the docstrings, we traditionally just say
>
> Get flymake diagnostics in region BEG..END
If it helps, BEG non-nil and END nil are a special case here, so maybe
that justifies the non-standard "determined by BEG and END"
phrasing. Feel free to change though.
João
- 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, 2017/10/20
- 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 <=