{"action":"opened","issue":{"url":"https://api.github.com/repos/benekastah/neomake/issues/196","labels_url":"https://api.github.com/repos/benekastah/neomake/issues/196/labels{/name}","comments_url":"https://api.github.com/repos/benekastah/neomake/issues/196/comments","events_url":"https://api.github.com/repos/benekastah/neomake/issues/196/events","html_url":"https://github.com/benekastah/neomake/issues/196","id":110371161,"number":196,"title":"Allow file to be excluded from file maker","user":{"login":"jason0x43","id":1042866,"avatar_url":"https://avatars.githubusercontent.com/u/1042866?v=3","gravatar_id":"","url":"https://api.github.com/users/jason0x43","html_url":"https://github.com/jason0x43","followers_url":"https://api.github.com/users/jason0x43/followers","following_url":"https://api.github.com/users/jason0x43/following{/other_user}","gists_url":"https://api.github.com/users/jason0x43/gists{/gist_id}","starred_url":"https://api.github.com/users/jason0x43/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jason0x43/subscriptions","organizations_url":"https://api.github.com/users/jason0x43/orgs","repos_url":"https://api.github.com/users/jason0x43/repos","events_url":"https://api.github.com/users/jason0x43/events{/privacy}","received_events_url":"https://api.github.com/users/jason0x43/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-10-08T04:28:48Z","updated_at":"2015-10-08T04:28:48Z","closed_at":null,"body":"It seems like project level builders such as `go build` and `tsc` would generally work fine as filetype builders if the builder definition had a way of excluding the filename. Consider the `go` plugin. It currently includes filetype builders for `go` and `golint`. It's nice to use the filetype mode with go files since you can see both syntax errors (from `go build`) and style errors (from `golint`). However, it doesn't make sense to run `go build` with a filename argument since you'll get spurious errors if the current file uses things defined in other files, so using `Neomake` (not `Neomake!`) with go files as it stands can be kind of annoying.\r\n\r\nIf the filename could be excluded, either by providing something like a 'nofile' option or by making the ':p' placeholder non-optional for filename inclusion, then filetype-specific project builders like `go build` could run with other filetype builders. I mean, `go build` *is* a filetype builder,it just makes more sense to run it without a file argument."}}