# Ats flymake - does it not work for you?
**URL:** https://discourse.ats-lang.org/t/ats-flymake-does-it-not-work-for-you/787
**Category:** Google Group
**Created:** [January 10, 2014, 2:32am UTC](https://discourse.ats-lang.org/t/ats-flymake-does-it-not-work-for-you/787 "2014-01-10T02:32:49Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Brandon\_Barker](https://discourse.ats-lang.org/u/Brandon_Barker)
#### Post date: [January 10, 2014, 2:32am UTC](https://discourse.ats-lang.org/t/ats-flymake-does-it-not-work-for-you/787/1 "2014-01-10T02:32:49Z")
flymake mode used to work wonderfully with highlighting errors in ATS1.
Recently I haven’t had any luck with ats-flymake or ats2-flymake on my
environments.
(flymake-compile works in both cases).
Once I get a chance to test some clean installations, I’ll report back here.
---
### Author:  [@Brandon\_Barker](https://discourse.ats-lang.org/u/Brandon_Barker)
#### Post date: [January 10, 2014, 3:55am UTC](https://discourse.ats-lang.org/t/ats-flymake-does-it-not-work-for-you/787/2 "2014-01-10T03:55:48Z")
ats2-mode certainly has some advantages, I will try this approach for a
while until I get some VMs set up to do more testing (removing everything
else from .emacs did not seem to help). I believe the immediate feedback of
flymake is slightly more nice for a beginner (that may still include
myself).
As for clean installs, tested so far:
A clean install with emacs 24.3.1 in cygwin works fine for ATS(1)-mode,
though the highlighting is bad (maybe a cygwin issue).
Finally, I think my issue on (“unclean”) sytems may have something to do
with a buffering issue, which occurs even when just using ats2-mode
facilities, and I believe it has propagated to flycheck and flymake as well:
If I press C c C c to compile, or use flymake-compile, etc, I’ll see the
following:
-_- mode: compilation; default-directory: “~/FBA/FALCON/” -_-
Compilation started at Thu Jan 9 22:46:50
patscc -tcats /home/brandon/FBA/FALCON/sstream.dats
exec(patsopt --typecheck --dynamic /home/brandon/FBA/FALCON/sstream.dats)
Hello from ATS2(ATS/Postiats)!
Loading [fixity.ats] starts!
Loading [fixity.ats] finishes!
Loading [basics\_pre.sats] starts!
Loading [basics\_pre.sats] finishes!
Loading [basics\_sta.sats] starts!
Loading [basics\_sta.sats] finishes!
Loading [basics\_dyn.sats] starts!
Loading [basics\_dyn.sats] finishes!
Loading [basics\_gen.sats] starts!
Loading [basics\_gen.sats] finishes!
Loading [stream.dats] starts!
Loading [stream.dats] finishes!
Loading [stream\_vt.dats] starts!
Loading [stream\_vt.dats] finishes!
— end of what i see in the Compilation buffer—
Now if I press any key, I’ll get the rest of the text involving errors
showing up in the buffer:
The 1st translation (fixity) of [/home/brandon/FBA/FALCON/sstream.dats] is
successfully completed!
/home/brandon/FBA/FALCON/sstream.dats: 1447(line=62, offs=3) –
1464(line=62, offs=20): error(2):
[/media/RAID5/home/brandon/ATS-Postiats/src/pats\_trans2\_dynexp.dats]:
d1exp\_tr\_app\_dyn\_dqid: the dynamic ide
ntifier [string1\_of\_strbuf] is unrecognized.
…On Thursday, January 9, 2014 9:49:35 PM UTC-5, gmhwxi wrote:
> I tried it recently. It seems to be able to highlight the location of the
> source
> of a type-error pretty well but it needs more work.
>
> Currently, I myself prefer to use C-x ` (that is backquote) to locate the
> source
> of a type-error. Basically, I do the following (with ats2-mode for emacs
> being turned on):
>
> C-c C-c // for compilation
> C-x ` // for locating the source of the first error C-x` // for locating the source of the next error
>
> On Thursday, January 9, 2014 9:32:49 PM UTC-5, Brandon Barker wrote:
>
> > flymake mode used to work wonderfully with highlighting errors in ATS1.
> >
> > Recently I haven’t had any luck with ats-flymake or ats2-flymake on my
> > environments.
> > (flymake-compile works in both cases).
> >
> > Once I get a chance to test some clean installations, I’ll report back
> > here.
---
### Author:  [@gmhwxi](https://discourse.ats-lang.org/u/gmhwxi)
#### Post date: [January 10, 2014, 2:49am UTC](https://discourse.ats-lang.org/t/ats-flymake-does-it-not-work-for-you/787/3 "2014-01-10T02:49:35Z")
I tried it recently. It seems to be able to highlight the location of the
source
of a type-error pretty well but it needs more work.
Currently, I myself prefer to use C-x ` (that is backquote) to locate the
source
of a type-error. Basically, I do the following (with ats2-mode for emacs
being turned on):
C-c C-c // for compilation
C-x ` // for locating the source of the first error C-x` // for locating the source of the next errorOn Thursday, January 9, 2014 9:32:49 PM UTC-5, Brandon Barker wrote:
> flymake mode used to work wonderfully with highlighting errors in ATS1.
>
> Recently I haven’t had any luck with ats-flymake or ats2-flymake on my
> environments.
> (flymake-compile works in both cases).
>
> Once I get a chance to test some clean installations, I’ll report back
> here.