This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (2)
- # babashka (64)
- # beginners (41)
- # calva (4)
- # cider (1)
- # clj-kondo (78)
- # cljdoc (31)
- # cljsrn (4)
- # clojars (2)
- # clojure (109)
- # clojure-germany (1)
- # clojure-italy (8)
- # clojure-nl (2)
- # clojure-spec (8)
- # clojure-uk (28)
- # clojurescript (61)
- # code-reviews (2)
- # cryogen (2)
- # cursive (23)
- # datomic (21)
- # duct (15)
- # fulcro (37)
- # graalvm (17)
- # graphql (3)
- # jackdaw (3)
- # joker (11)
- # lein-figwheel (4)
- # malli (42)
- # off-topic (97)
- # pathom (4)
- # pedestal (1)
- # portkey (3)
- # re-frame (7)
- # reagent (13)
- # reitit (2)
- # shadow-cljs (54)
- # spacemacs (1)
I'm getting this with the windows executable:
PS C:\Users\roger\Downloads\clj-kondo-2019.11.08-SNAPSHOT-windows-amd64> cat .\foo.clj (def x (def x 1)) PS C:\Users\roger\Downloads\clj-kondo-2019.11.08-SNAPSHOT-windows-amd64> .\clj-kondo.exe --lint .\foo.clj .\foo.clj:1:1: error: unresolved symbol ?? .\foo.clj:1:12: error: unresolved symbol x .\foo.clj:1:16: error: unresolved symbol .\foo.clj:1:18: error: unresolved symbol def .\foo.clj:1:30: error: unresolved symbol 1 linting took 16ms, errors: 5, warnings: 0
Although the very first test worked:
PS C:\Users\roger\Downloads\clj-kondo-2019.11.08-SNAPSHOT-windows-amd64> echo '(def x (def x 1))'| .\clj-kondo.exe --lint - <stdin>:1:8: warning: inline def
@roger429 I think there might be something wrong with that file? When I lint it locally (thanks for sending it):
$ clj-kondo --lint ~/Downloads/foo.clj /Users/borkdude/Downloads/foo.clj:1:1: error: unresolved symbol �� /Users/borkdude/Downloads/foo.clj:1:12: error: unresolved symbol x /Users/borkdude/Downloads/foo.clj:1:16: error: unresolved symbol /Users/borkdude/Downloads/foo.clj:1:18: error: unresolved symbol def /Users/borkdude/Downloads/foo.clj:1:30: error: unresolved symbol 1 linting took 120ms, errors: 5, warnings: 0
This is what I see in hexl-mode:
fffe 2800 6400 6500 6600 2000 7800 2000 ..(.d.e.f. .x. .
VSC shows that file to have an UTF-16LE encoding (little endian?). Probably has to do with the way Powershell pipes the result of echo into the file. I created a file in VSC and it has UTF8 encoding. That file is handled as expected by clj-konde.exe.
The UTF-8 file is 17 bytes; the UTF-16 LE 36 bytes: double the UTF-8 + a BOF marker or some such thingy.
ok. any specific feedback? e.g. technical inaccuracies or omissions? aesthetic points fine too 🙂
I think it's better to discuss in a PR, since Slack gets a little bit all over the place for me
I wonder if it will recognize the binary correctly... .exe is different from other platform names
Windows has Opinions about binary names. We had fun porting our golang “build agent” at CircleCI to Windows.
We first ran the Linux version of the code on Windows, - we copy the binary into a tmp folder, and invoke it.
Windows will see if the path that you are invoking has a corresponding .exe or .cmd file, and it runs that.
I would test this in a Windows VM, but for some reason VirtualBox crashes often on my new Macbook Pro
binary execution on windows is further complicated by the fact that some extensions are only picked up from a given shell
ah... hm. maybe that also conflicts with how scoop does things, because it makes these .cmd wrappers?
so depending on how you try to spawn the process, it might fail to find some executable
I understand the feeling from a maintainers point of view, but from a consumer POV it is also a pain that half the open source software doesn't work on windows
everyone can install linux, but in practice development happens not on linux but on mac
Please don't claim your experiences are the same everyone else has. I have done all my professional development work, since 1997, on Linux. Working around Europe I noticed most development machines my colleagues had were a ThinkPad running Linux. I would not presume to tell anyone that there is only one machine that development is done on, as it would make me sound quite arrogant.
you know what, I was totally wrong to assume that and should have copped on when I linked the stack overflow survey
my experience was indeed most of my colleagues were on osx and I was always the lone windows
but I guess that's mostly a siloed thing, where whole places buy in to one OS or another
if you don't work on a mac, you're a second class citizen in the open source world 🙂
I don't hear this topic being discussed as much but I think it ended up being yet another mac-related lock-in
windows sure could be easier to work on but at the end of the day windows hosts around half the developers
That's a very sweeping generalisation. At our place of work, it's 99% linux, with one windows machine.
There may be many more people using mac's - but how many of those are using mac's for the adobe range of software, rather than just cutting code.
Also, there's probably a reason why people gravitate towards linux or mac for development. The shell experience has been behind for years in Windows.
In regards the stackoverflow survey, 1. it's stackoverflow so inherently biased and 2. what is the error margin? One survey does not make a statement about fact.
I've never considered myself a second class citizen by using linux (and I also have a few macs) - I would indeed argue with the recent changes that Apple are pushing out to developers with the changes to their OS, life for a developer on mac's is becoming more difficult! I've always found - as a linux user - to be catered for in terms of development - software, documentation, processed, tools - everything I need is available on Linux. I've never had to go scrambling to a Mac to continue working.
interested in seeing what kind of quantified evidence there is for "development happens not on linux but on mac" -- a bit broad perhaps too. in terms of actually making command line tools, my impression has been that stuff gets ported to the mac, but often starts on some other *nix. i wonder if there is some way to comb repository histories for evidence.
i've used macos on and off for a while, but for the kinds of things i wanted to do, found i often had to reach for another *nix because what i wanted wasn't available for macos (yet). may be this would make an interesting topic for #off-topic.
@jr0cket called me out on that as well, and it true: that was an unwarranted generalization based on my experience
but to be fair I never argued that Linux users were second class to mac users, I argued that windows users are second class in open source (on the topic above)
I think linux is a first class citizen in open source, because it's the gold standard for where the software should run
still think it would make for an interesting discussion on #off-topic -- not to mention an interesting study (especially if evidence could be gathered in a semi-automated fashion)
i would argue that closed source operating systems compose way worse with open source development systems. linux is still poor, it is no match to the integration lisp machines had, but at least you can go in and adapt parts, if needed. despite all the open source propaganda from microsoft they still have not open sourced any of their core infrastructure. they just make it convenient enough for people to integrate all the free labor on their platform so that they don't become obsolete
that is the same strategy that apple has used to great success. yet i would never consider running infrastructure on macs, because you have to buy into a giant black box.
i also would like to say that countless open source man years have been put into proving the microsoft model of developing software wrong. that they have adapted does not mean that they are really for open source. the github source code is also not open source for instance, although it would be maybe the most logical thing to do from an open source perspective.