aboutsummaryrefslogtreecommitdiffstatshomepage
Commit message (Collapse)AuthorAge
* workflows/ci: upgrade actionsEgor Tensin2023-01-02
|
* workflows/ci: disable scheduled runsEgor Tensin2023-01-02
|
* workflows/ci: lintingEgor Tensin2021-05-04
|
* README: fix badge linkEgor Tensin2021-04-17
|
* workflows/ci: error out if no files to uploadEgor Tensin2021-04-07
|
* workflows/ci.yml: run the testsEgor Tensin2021-01-24
|
* README: updateEgor Tensin2021-01-24
|
* add GitHub workflowEgor Tensin2021-01-24
|
* bye-bye, AppVeyor!no_more_appveyorEgor Tensin2021-01-24
|
* AppVeyor: add some basic testsEgor Tensin2020-08-27
|
* AppVeyor: use choco to install stackEgor Tensin2020-08-27
|
* AppVeyor: fast_finishEgor Tensin2020-01-11
|
* appveyor.yml -> .appveyor.ymlEgor Tensin2020-01-11
|
* AppVeyor: prettify appveyor.ymlEgor Tensin2020-01-09
|
* AppVeyor: package the artifactsEgor Tensin2019-12-16
|
* AppVeyor: ditch PowerShellEgor Tensin2019-12-11
|
* AppVeyor: don't preserve Set-PSDebugEgor Tensin2019-08-24
|
* split root .gitattributesEgor Tensin2019-08-24
|
* AppVeyor: build all branchesEgor Tensin2019-08-24
|
* AppVeyor: better practicesEgor Tensin2019-08-22
|
* fix eolEgor Tensin2019-08-22
|
* add .gitattributesEgor Tensin2019-08-21
|
* AppVeyor: build master onlyEgor Tensin2019-08-21
|
* README: add AppVeyor badgeEgor Tensin2019-08-21
|
* add AppVeyor configurationEgor Tensin2019-08-21
|
* ignore stack.yaml.lockEgor Tensin2019-08-21
| | | | | | Stack 2.1.1 introduced lock files. I'm not sure whether to include them in the repository, here's some discussion on the subject: https://github.com/commercialhaskell/stack/issues/4795
* bump resolverEgor Tensin2019-08-21
| | | | | | | | It includes the required Win32 version, so there's no need to mess with extra-deps. Also, it uses a newer Cabal version, which seems to require the Paths_ module to be listed in other-modules (and adds the autogen-modules field).
* fix builds with Stack >= 2.1.1Egor Tensin2019-08-21
| | | | | Somehow it complained about the time package not being in extra-deps (it works with 1.9.3).
* README updateEgor Tensin2017-10-04
|
* bump versionv0.2.1.0Egor Tensin2017-06-17
|
* Win32's lower bound was always wrongEgor Tensin2017-06-17
| | | | | | | | I don't know why, the `failWith` fix was only released in Win32-2.5.0.0. Maybe it had to be >= 2.4.0.0 because previously Win32 was fetched from GitHub as a tarball of the commit with the fix, before the package version was actually bumped to 2.5.0.0.
* use windows_cconv.h from Win32Egor Tensin2017-06-17
|
* add --version flag to executablesEgor Tensin2017-06-17
|
* bump resolverEgor Tensin2017-06-17
| | | | | Also, put Win32 to extra-deps (the then-unreleased version was previously fetched in a .zip tarball from GitHub directly).
* refactoringEgor Tensin2017-06-13
|
* bump versionv0.2.0.0Egor Tensin2017-06-13
|
* fix HLint warningsEgor Tensin2017-06-13
|
* addpath: detect expandable pathsEgor Tensin2017-06-13
|
* feature registry value type in promptsEgor Tensin2017-06-12
|
* refactoringEgor Tensin2017-06-12
|
* setenv: crap, another bugEgor Tensin2017-06-12
| | | | | | | | I don't know what's happening. The latest string of commits is basically broken at every point. I'll tag as soon as I decide it's safe to use, which probably will become the default mode of development (instead of _every_ commit representing a working version).
* addpath: fix a sleep-deprived bugEgor Tensin2017-06-12
| | | | | | | | | | | | | | Yeah, so last night I added a Show instance to WindowsEnv.Value (ex-WindowsEnv.VarValue), which would simply call valueString (ex-varValueString). Then I replaced every valueString/varValueString with show. Then I decided that this Show instance was a mistake, and derived an instance instead. It obviously messed up all the show VarValue/Value calls. The lesson to learn is you should remove an instance first, fix all the call sites, and only then derive it. The disgusting part is that a few of the last commits are actually broken, which I hate.
* delpath: don't do anything if variable is missingEgor Tensin2017-06-12
|
* setenv: detect expandable valuesEgor Tensin2017-06-12
|
* WindowsEnv: {VarName,VarValue} -> {Name,Value}Egor Tensin2017-06-11
| | | | | Also, fix compiler warnings (I've got too used to building with `--ghc-options -w`).
* delenv: ignore missing variablesEgor Tensin2017-06-11
|
* refactoringEgor Tensin2017-06-11
|
* windows-env.cabal: fix formattingEgor Tensin2017-06-11
|
* refactoringEgor Tensin2017-06-11
| | | | | | | | | | The fact whether the registry value was a regular or an expandable string is now propagated up to the `Environment` module (and even further to the apps). This was done to get rid of these weird `setString*` functions (and the like). I don't feel like I've came up with the right abstractions yet though, so there's more work on this to come.
* code styleEgor Tensin2017-06-10
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-28 10:22:08 +0000