[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: :alnum: broken?
From: |
Clément Pit-Claudel |
Subject: |
Re: :alnum: broken? |
Date: |
Sat, 29 Feb 2020 17:34:14 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 |
On 2020-02-29 17:22, Marcin Borkowski wrote:
> +1. I consider myself fairly proficient in Elisp; I authored quitee
> a few packages, some of them distributed on Github, some of them for
> private use for a few people. I admit that even that I know about
> compiler warnings, I never got into a habit of compiling my files. (I
> know I should, but consider me as a datapoint suggesting that compiler
> warnings are not enough.)
Did you consider flycheck or flymake? Both will compile your files in the
background and report errors.
- Re: :alnum: broken?, (continued)
- Re: :alnum: broken?, Mattias Engdegård, 2020/02/28
- Re: :alnum: broken?, Eli Zaretskii, 2020/02/28
- Re: :alnum: broken?, Mattias Engdegård, 2020/02/29
- Re: :alnum: broken?, Eli Zaretskii, 2020/02/29
- Re: :alnum: broken?, Stefan Monnier, 2020/02/29
- Re: :alnum: broken?, Stefan Monnier, 2020/02/29
- Re: :alnum: broken?, Óscar Fuentes, 2020/02/29
- Re: :alnum: broken?, Stefan Monnier, 2020/02/29
- Re: :alnum: broken?, Óscar Fuentes, 2020/02/29
- Re: :alnum: broken?, Marcin Borkowski, 2020/02/29
- Re: :alnum: broken?,
Clément Pit-Claudel <=
- Re: :alnum: broken?, Andrea Corallo, 2020/02/29
- Re: :alnum: broken?, Stefan Monnier, 2020/02/29
- Re: :alnum: broken?, Óscar Fuentes, 2020/02/29
- Re: :alnum: broken?, Paul Eggert, 2020/02/26
- Re: :alnum: broken?, Andreas Schwab, 2020/02/26
- Re: :alnum: broken?, Mattias Engdegård, 2020/02/26
- Re: :alnum: broken?, Andreas Schwab, 2020/02/27
- Re: :alnum: broken?, Mattias Engdegård, 2020/02/27
- Re: :alnum: broken?, Eli Zaretskii, 2020/02/22
- Re: :alnum: broken?, Richard Stallman, 2020/02/22