profile
viewpoint
Casey Rodarmor casey The Blue Planet https://rodarmor.com 😻A N A R C H O ー ネ コ バ ス 😻

casey/boot 7

boot / ⠛⠕⠞⠞⠁⠀⠃⠕⠕⠞⠀⠮⠀⠍⠑⠞⠁⠍⠁⠡⠔⠑

casey/blaster 3

✯ Audio reactive visuals engine in C++/OpenGL

casey/bak 2

📦 Move files out of the way

casey/brev 2

💀 Do or die: quick and dirty utility functions in rust

casey/bulb 2

Tulip Farm Discord bot

casey/9x 1

Plan 9 for Unix

casey/annotated-torrents 1

Rich, structured content metadata for BitTorrent

casey/askama 1

Type-safe, compiled Jinja-like templates for Rust

casey/clap-config 1

Generate a config parser from a clap argument parser

casey/colour-lovers-rs 1

🎨Tools for interacting with COLOURlovers

pull request commentcasey/just

Strip leading spaces after line continuation

Just my two cents. After this broke my justfiles (they are private so no way you would have known) I found this ticket.

Ahh, sorry this broke your justfiles. Did they have slashes without spaces before them? Like this:

foo:
  echo bar\
   baz

I think I assumed that having no space before line continuation slashes is less common than it actually is.

I think that it would have been nice to make this work like Make in that it stripped all the spaces equal to the indent. I think that is what happens for the shebang polyglot code.

Do you mean that in this justfile:

foo:
  echo bar \
   baz

The first line of foo would be:

echo bar baz

I.e. two spaces between bar and baz?

casey

comment created time in 10 hours

create barnchcasey/data

branch : master

created branch time in 12 hours

issue commenttaiwangoldcard/website

Suggestion: List of private firms and/or individuals that can advise a gold card applicant

Since there may not be immigration lawyers that have any experience with the gold card process at the moment, I think this issue could be closed, since it isn't immediately actionable.

casey

comment created time in a day

issue commenttaiwangoldcard/website

Suggestion: List of private firms and/or individuals that can advise a gold card applicant

Thanks so much for jumping in and providing ideas @casey, very much appreciated.

You're totally welcome, I really appreciate the site!

Eventually, we want to gather knowledge from the community of people who have successfully applied and provide real-life examples of the kind of documents people submitted for each category.

I think that would be super helpful, along with knowing a little bit about the background of successful applicants. (Which could be anonymized to avoid giving away personal details.)

To date, I haven't heard much feedback about any legal/migration shops helping applicants, which makes sense given that this is designed as a self-application approach.

That makes sense. I suspect that since it's self-help, immigration firms might not have much advice because they haven't helped many people through the process.

If you're used to working iteratively, and have a little bit of time up your sleeve, one thing you can do is simply pick a category and apply. This is possible because 1) if the documents you provide are insufficient, you get several chances to revise them and 2) you can change the application category after submission free of charge. The only issue with this approach is each time you need to run through the skill verification process it will take ~20 days.

Thanks for the suggestion, I'll give that a shot.

I might try to collect all relevant documentation I can think of and submit everything, since I can't imagine that extra documents would hurt me.

casey

comment created time in a day

startedaleferri/casmeleon

started time in 3 days

issue commenttaiwangoldcard/website

Suggestion: List of private firms and/or individuals that can advise a gold card applicant

Out of curiosity, what information do you feel the website is currently lacking in terms of helping you figure out which category you would qualify for? Any feedback would really help us to improve the content!

Absolutely! I'm a programmer, and have worked in VR and blockchain, as well as for major companies, but I'm unsure if having worked in those areas is enough to qualify for the technology track, or if I would additionally need to have demonstrable research achievements, like patents, etcetera.

I'm guessing you've already checked the Gold Card Qualification Checker? https://visafinder.tw/gold-card-qualification/

I have, but it wasn't clear to me whether I qualified. It said that I might qualify, but for instance, I don't know if having been a software engineer in VR and blockchain was enough to make me "exceptional".

If you need professional advice, your best bet is probably to find a Taiwan based immigration lawyer that can help you.

It was easy to find Taiwanese immigration lawyers, but I wasn't sure if any of them were good, so a list with some pointers to firms that others have had a good experience with would be the kind of thing that would be very helpful.

casey

comment created time in 3 days

issue openedtaiwangoldcard/website

Suggestion: List of private firms and/or individuals that can advise a gold card applicant

I'm considering applying for a gold card, but am unsure about if I qualify, what category I should apply under, and what supporting documents I sould include in my application.

I'm reaching out to the government agencies listed on the site, but they are slow to respond, and not always super helpful.

It might be nice to include links to private firms, like immigration lawyers, that can be contacted for paid advice and assistance regarding a gold card application.

Thanks so much for the site, it's an awesome resource!

created time in 4 days

delete branch casey/intermodal

delete branch : v-release

delete time in 8 days

push eventcasey/intermodal

Casey Rodarmor

commit sha a2a4ea143008d72f9faabac81e0992e35152e8dc

Mark tags that start with `v` as releases type: development

view details

push time in 8 days

PR opened casey/intermodal

Mark tags that start with `v` as releases

type: development

+1 -0

0 comment

1 changed file

pr created time in 8 days

create barnchcasey/intermodal

branch : v-release

created branch time in 8 days

delete branch casey/intermodal

delete branch : v-release

delete time in 8 days

PR closed casey/intermodal

Mark tags that start with `v` as releases

type: development

+1 -0

0 comment

1 changed file

casey

pr closed time in 8 days

PR opened casey/intermodal

Mark tags that start with `v` as releases

type: development

+1 -0

0 comment

1 changed file

pr created time in 8 days

delete tag casey/just

delete tag : v-gha-test

delete time in 8 days

delete tag casey/just

delete tag : gha-test

delete time in 8 days

create barnchcasey/intermodal

branch : v-release

created branch time in 8 days

push eventcasey/just

Casey Rodarmor

commit sha cea4a1608199672934f9db1b1b2c11f0feb3fd2f

Mark tags that start with `v` as releases (#654)

view details

push time in 8 days

delete branch casey/just

delete branch : pre-release-tag

delete time in 8 days

PR merged casey/just

Mark tags that start with `v` as releases
+1 -1

0 comment

1 changed file

casey

pr closed time in 8 days

PR opened casey/just

Mark tags that start with `v` as releases
+1 -1

0 comment

1 changed file

pr created time in 8 days

create barnchcasey/just

branch : pre-release-tag

created branch time in 8 days

delete tag casey/just

delete tag : v-gha-test

delete time in 8 days

delete tag casey/just

delete tag : v-gha-test

delete time in 8 days

delete tag casey/just

delete tag : gha-test

delete time in 8 days

delete tag casey/just

delete tag : cygpath-test

delete time in 8 days

created tagcasey/just

tagv-gha-test

🤖 Just a command runner

created time in 8 days

created tagcasey/just

taggha-test

🤖 Just a command runner

created time in 8 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

No worries, releases are easy. I just cut v0.6.1, available here. It looks like the Linux and Mac artifacts are done, and Windows binaries should be done soon. Let me know if you run into any issues!

pfmoore

comment created time in 11 days

created tagcasey/just

tagv0.6.1

🤖 Just a command runner

created time in 12 days

push eventcasey/just

Casey Rodarmor

commit sha 7384307fdca839598ff9d9599480b44c3ba28083

Release v0.6.1 (#653) - Bump version: 0.6.0 → 0.6.1 - Update dependencies - Update changelog - Update man page - Update config test

view details

push time in 12 days

delete branch casey/just

delete branch : release

delete time in 12 days

PR merged casey/just

Release v0.6.1
  • Bump version: 0.6.0 → 0.6.1
  • Update dependencies
  • Update changelog
  • Update man page
  • Update config test
+41 -34

0 comment

5 changed files

casey

pr closed time in 12 days

PR opened casey/just

Release v0.6.1
  • Bump version: 0.6.0 → 0.6.1
  • Update dependencies
  • Update changelog
  • Update man page
  • Update config test
+41 -34

0 comment

5 changed files

pr created time in 12 days

create barnchcasey/just

branch : release

created branch time in 12 days

startedIdrisMiles/cliquers

started time in 12 days

issue closedcasey/just

Allow an alternative runner for shebang tasks

Currently the shell setting lets users customise the runner for single-line commands. But this doesn't affect shebang tasks. On Windows, the default shell may not exist, so this makes shebang tasks unusable. However, the "Python Launcher" shipped with Python includes a shebang interpreter, so it would be entirely possible on Windows to say

set shebang_shell := ["py"]

at the top of the justfile to get shebang support.

This should be a different setting variable, not shell, as py doesn't handle command lines, and a shell like Powershell doesn't handle shebangs. So a single setting won't work for both.

On an unrelated note, it would be nice to have systemwide settings, so that I didn't have to set shell (and shebang_shell, if it was added) in every justfile.

closed time in 12 days

pfmoore

issue commentcasey/just

Allow an alternative runner for shebang tasks

I just merged #652. Let me know if you'd like me to cut a release! (Not sure if you needed one, since py doesn't work.) I'm going to close this issue, since I think the underlying problem is fixed.

pfmoore

comment created time in 12 days

push eventcasey/just

Casey Rodarmor

commit sha 5533073f565102419fe581934c9fb23a477dcc69

Only use `cygpath` on shebang if it contains `/` (#652) On Windows, skip conversion if a shebang path does not include `/`. In this case it is not a Unix path, and does not need to be converted to a Windows path before running.

view details

push time in 12 days

delete branch casey/just

delete branch : windows-shebang

delete time in 12 days

PR merged casey/just

Only use `cygpath` on shebang if it contains `/`

On Windows, skip conversion if a shebang path does not include /. In this case it is not a Unix path, and does not need to be converted to a Windows path before running.

+55 -12

0 comment

4 changed files

casey

pr closed time in 12 days

push eventcasey/just

Casey Rodarmor

commit sha d5d808a96a4342ea5a4f8bd0e748c9b19ee00308

Build and package on all tags

view details

push time in 12 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

It's definitely unfortunate that py works this way, but it's only indirectly related to the change. I.e. the PR just makes it so that cygpath isn't always needed, so I think with cygpath installed, infinite recursion is still possible if you try to use #!py.

pfmoore

comment created time in 12 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

It took me a while to work out why my laptop was slowing down. I don't know how many py.exe processes I had when I killed it 🙁

Ah, interesting. So I guess the py launcher just isn't intended to be used in a shebang.

To be honest, I think this is probably sufficiently bad that I'd suggest abandoning this idea altogether. Better to wait for a more robust solution using recipe annotations.

It's definitely annoying, but it still seems like the PR is somewhat nice for windows users, since they can at least do #!powershell.

pfmoore

comment created time in 13 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

Absolutely! Thanks so much for doing this. It may be a few days before I get a chance to test, but I'll get back to you.

You bet!

My two main use cases would be #!powershell/#!pwsh and #!py, so that's fine for me. With path searches working, quoting is far less important.

One vague worry I have is that #!python3 will potentially work on Windows, but not Unix. I could make it work on Unix too, but I think at that point I'll probably add an #[interpreter(…)] annotation which works consistently across all platforms.

pfmoore

comment created time in 14 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

I just made some modifications to the github actions config to build and package all tags (previously, only new release tags would be built). If the modification is correct, binaries with the change in this PR should be build and uploaded automatically to this tag: https://github.com/casey/just/releases/tag/cygpath-test

pfmoore

comment created time in 14 days

release casey/just

cygpath-test

released time in 14 days

created tagcasey/just

tagcygpath-test

🤖 Just a command runner

created time in 14 days

issue commentcasey/just

Add extensible recipe annotations/attributes

I do think that C# attributes are more attractive, and the syntax highlighting argument is persuasive. C# uses curly braces for arrays (e.g. {1,2,3,4}), so there's no ambiguity there. Using […] for annotations would mean that we couldn't use […] for arrays in Just, which doesn't seem ideal.

casey

comment created time in 14 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

Hoo, boy, you haven't lived yet! I've worked on a number of Python packages (pip and virtualenv in particular) that deal with shebangs, and the Unix behaviour is incredibly inconsistent 🙂 Some Unix systems have a limit on the length of the shebang, some silently ignore everything after a space, some treat the whole line as an executable name, whitespace and all. If you stick to Linux, the rules are consistent (because the kernel handles it) but I'm not even sure MacOS works the same. But in practice, things work for 99% of the uses people make of them, so it's good enough.

I've never run into a cross-platform issue with shebangs, so I didn't know any of that. Yikes!

That sounds like a much better solution in the long term, TBH.

A lot of improvements are kind of waiting for annotations, since they seem to be the best way to add a wide variety of features without coming up with a whole lot of custom syntaxes.

I opened a PR that skips cygpath translation for shebang paths if the interpreter path doesn't contain a /. Would you be interested in trying it out and seeing if it works for your use cases? It doesn't support quoting, unfortunately, but #!powershell should work.

https://github.com/casey/just/pull/652

pfmoore

comment created time in 14 days

push eventcasey/just

Casey Rodarmor

commit sha 738b446367e429cb697063d51a728fc3cf5e5462

Only use `cygpath` on shebang if it contains `/` On Windows, skip conversion if a shebang path does not include `/`. In this case it is not a Unix path, and does not need to be converted to a Windows path before running.

view details

push time in 14 days

push eventcasey/just

Casey Rodarmor

commit sha 663a144b5198772a6a3888fae823e4e1d8728dfa

Wording

view details

push time in 14 days

push eventcasey/just

Casey Rodarmor

commit sha 2b5469dc537d46ff93b2c5280c3a482f3cf83306

Fix test

view details

push time in 14 days

push eventcasey/just

Casey Rodarmor

commit sha 7e62ced0346700854f577f75ae844240a2ca04bf

Only use `cygpath` on shebang if it contains `/` On Windows, skip conversion if a shebang path does not include `/`. In this case it is not a Unix path, and does not need to be converted to a Windows path before running.

view details

push time in 14 days

delete branch casey/intermodal

delete branch : irc

delete time in 14 days

PR merged casey/intermodal

Remove Keybase and IRC links from readme

Keybase and IRC chat never got any users, and since I never check them and they get no traffic, it's probably best to remove them from the readme.

type: documentation

+2 -6

0 comment

2 changed files

casey

pr closed time in 14 days

push eventcasey/intermodal

Casey Rodarmor

commit sha a53c2bc5dbfd834cefdeb25fb7b8c5ba8712c1e1

Remove Keybase and IRC links from readme Keybase and IRC chat never got any users, and since I never check them and they get no traffic, it's probably best to remove them from the readme. type: documentation

view details

push time in 14 days

PR opened casey/intermodal

Remove Keybase and IRC links from readme

Keybase and IRC chat never got any users, and since I never check them and they get no traffic, it's probably best to remove them from the readme.

type: documentation

+2 -6

0 comment

2 changed files

pr created time in 14 days

create barnchcasey/intermodal

branch : irc

created branch time in 14 days

pull request commentmitsuhiko/indicatif

Add `binary_bytes_per_second` state formatter

@mitsuhiko Rebased, and added docs!

casey

comment created time in 15 days

push eventcasey/indicatif

djugei

commit sha d1609cc6819ffcc623a70148c7812d23a075b81a

unicode-awareness part 1/2

view details

djugei

commit sha 3cbd533da3eda9162da8955ead6218a022b0604b

unicode-awareness part 2/2

view details

djugei

commit sha 166082a963cc011a320018cfe1fd137efa70760a

collect instead of fold

view details

Nick Linker

commit sha b160d94eb6f2383b113a8320944913966a9b6c10

Implement `insert` method for `MultiProgress` (#178)

view details

djugei

commit sha 9ac7c2b01a864712afc63c0667d753983f2b3f23

fixed doc warnings (#173)

view details

Armin Ronacher

commit sha 0596151a8c8698ece509cbacb16c2ab981a80bd1

Move unicode features behind feature flag and rename with_rayon feature to rayon

view details

Armin Ronacher

commit sha cbd01335e06e08bd644aec279b4bb60646204a8d

Merge branch 'unicode'

view details

Michael

commit sha 0df2c37d1ea39df603f1de4b4320df1721307e21

Fix `download-continued` ETA (#171)

view details

Michael

commit sha c19ae2d29283542fef1fb152b4fc6c8d96f61d41

Update tokio example to 0.2 (#165)

view details

Michael

commit sha 7e935fd9d62a8bc7dd945ec27435a22894b8658b

Add WeakProgressBar (#161)

view details

Michael

commit sha 0f4f1a632a762cca8e5bf777cd23fb9a817e68e9

Implement update grouping (#166) * Implement update grouping If there are multiple progress bar updates happening concurrently only one update will be shown immediately. The rest of the updates will only be shown upon the next update that's happening after the refresh rate cooldown in ProgressDrawTarget elapses. This change implements grouping updates to prevent that behavior. * Properly handle orphan lines in update grouping

view details

Armin Ronacher

commit sha 44ec738061d0ae3ee67d9f7e8155438ea76da867

Fix readme links

view details

Armin Ronacher

commit sha b28cd22bba33294655e8e7c5a79e33820e162d8b

0.15.0

view details

Casey Rodarmor

commit sha 7d3f1921fb0bc8739e80c285e9d4606fd077dd71

Add `binary_bytes_per_second` state formatter Add formatter for bytes per second using power-of-two units, i.e. `MiB`, `KiB`, etc.

view details

push time in 15 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

Hmm, OK. So you probably need to consider #!"C:\Program Files\Python3.8\python.exe" in that case (the path has spaces, so you need to quote it).

Man, I'm really loathe to introduce weird quoting rules in the shebang. The nice thing about the shebang feature on Unix is that it works in a very obvious way with no surprises, since uses the same mechanism as standalone scripts. (Just extracts the recipe, places it in its own file, and executes it.)

I'm not sure it would be wise of me to add special quoting rules for Windows, especially it would be an entirely different string parser from the main string parser.

An alternative would be to finally add recipe annotations, and use normal just strings to specify an interpreter:

#[interpreter("C:\Program Files\Python3.8\python.exe")]
foo:
  print("Hello!")

This is probably a better long-term alternative, since it uses a general, extensible mechanism, and leverages the existing lexer and parser, instead of introducing a special purpose lexer/parser/rules for a small feature.

I'm just learning Rust, so I'd struggle to follow that, I'm afraid! (Also, apologies that I can't provide a PR for this, for the same reason...)

No worries at all! Rust is rough, definitely the hardest language I've ever learned. Just keep at it! Writing little command line apps is a great way to learn. Just was the first program I wrote in Rust, and it started out small, delegating execution to Make, until I eventually added the custom parser and it turned into a much larger project.

pfmoore

comment created time in 15 days

push eventcasey/just

Casey Rodarmor

commit sha 38bef1ad3e6242531233418500f76416b24e3cda

Fool around with paths

view details

push time in 15 days

push eventcasey/just

Casey Rodarmor

commit sha 9e5d0d131d4fa02b87fc5b9c681c50715132d2a7

Fix

view details

push time in 15 days

push eventcasey/just

Casey Rodarmor

commit sha 9121830ed63d24dde86222e60dabfa26133da664

Test translation

view details

push time in 15 days

push eventcasey/just

Casey Rodarmor

commit sha 316433668428db33e2b76c8e3ff5762f64c5f25a

Powershellll

view details

push time in 15 days

push eventcasey/just

Casey Rodarmor

commit sha 11f01d2a3b29f295498a1014294b79aef3270455

Try no exe

view details

Casey Rodarmor

commit sha b32375fb33104edb4eee2b071932df68a190970c

Add garbage command line

view details

push time in 15 days

push eventcasey/just

Casey Rodarmor

commit sha 6da970583313c33819a13c510f84408464e9d61c

More docs, remove `/c`

view details

push time in 15 days

push eventcasey/just

Casey Rodarmor

commit sha 30d90ead4ad363558ae7f57e79e7b0ce5650b640

Try powershell

view details

push time in 15 days

PR opened casey/just

Only use `cygpath` on shebang if it contains `/`

On Windows, skip conversion if a shebang path does not include /. In this case it is not a Unix path, and does not need to be converted to a Windows path before running.

+29 -7

0 comment

2 changed files

pr created time in 15 days

create barnchcasey/just

branch : windows-shebang

created branch time in 15 days

create barnchcasey/foo

branch : master

created branch time in 15 days

created repositorycasey/foo

created time in 15 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

That sounds reasonable to me (or at least, it would work for my use - I'm not really interested, personally, in cross-platform Justfiles, so I may not have thought of some edge cases).

Thinking some more about it, I assume that on Unix you just pass the script to the shell so #! lines get processed by the kernel. What do you do on Windows? Read and process the #! line to find the executable, and then feed the script to that exe? If so, what rules do you use?

Yup, that's right. I believe I implemented parsing exactly how it's done on Unix, which means that it only processes one space. I.e. a binary and one argument. I'm not sure why Unix does it this way, it's probably a historical accident. Here's the code.

You would have to allow whitespace in the path, to cover things like C:\Program Files - unless you wanted to get into the mess that is quoting 🙂

I do process whitespace, to separate the program from the arguments, so things like #!/usr/bin/env python3 work. It's

Hopefully you also allow commands to be found on PATH (so that, for example, #!powershell would work¹).

I'll have to try that, but hopefully I can make that work. I delegate to rust's std::process::Command for running commands, so it mostly depends on how that works.

pfmoore

comment created time in 16 days

delete branch casey/intermodal

delete branch : release

delete time in 16 days

PR merged casey/intermodal

Release v0.1.10
  • Bump version: 0.1.9 → 0.1.10

type: release

+2 -2

0 comment

2 changed files

casey

pr closed time in 16 days

push eventcasey/intermodal

Casey Rodarmor

commit sha 705014c87ea42947ca59a168a6622f7a819dd52f

Release v0.1.10 - Bump version: 0.1.9 → 0.1.10 type: release

view details

push time in 16 days

created tagcasey/intermodal

tagv0.1.10

📦 Intermodal: A 40' foot shipping container for the internet

created time in 16 days

PR opened casey/intermodal

Release v0.1.10
  • Bump version: 0.1.9 → 0.1.10

type: release

+2 -2

0 comment

2 changed files

pr created time in 16 days

create barnchcasey/intermodal

branch : release

created branch time in 16 days

delete branch casey/intermodal

delete branch : no-git-book

delete time in 16 days

PR merged casey/intermodal

Add `--no-git` flag to `gen book`

Skip generating the changelog for the book when --no-git is passed to gen book or gen all.

type: added

+24 -10

0 comment

3 changed files

casey

pr closed time in 16 days

push eventcasey/intermodal

Casey Rodarmor

commit sha 04b58464c98c5638bdac3f77dbaf666bccbfaea6

Add `--no-git` flag to `gen book` Skip generating the changelog for the book when `--no-git` is passed to `gen book` or `gen all`. type: added

view details

push time in 16 days

PR opened casey/intermodal

Add `--no-git` flag to `gen book`

Skip generating the changelog for the book when --no-git is passed to gen book or gen all.

type: added

+24 -10

0 comment

3 changed files

pr created time in 16 days

create barnchcasey/intermodal

branch : no-git-book

created branch time in 16 days

delete branch casey/intermodal

delete branch : release

delete time in 16 days

PR merged casey/intermodal

Release v0.1.9
  • Bump version: 0.1.8 → 0.1.9
  • Update dependencies
  • Publish to cargo as last step in publish recipe

type: release

+125 -107

0 comment

3 changed files

casey

pr closed time in 16 days

push eventcasey/intermodal

Casey Rodarmor

commit sha 5951139fdfb59df69c5392835bc3432c5f8fa720

Release v0.1.9 - Bump version: 0.1.8 → 0.1.9 - Update dependencies - Publish to cargo as last step in publish recipe type: release

view details

push time in 16 days

created tagcasey/intermodal

tagv0.1.9

📦 Intermodal: A 40' foot shipping container for the internet

created time in 16 days

PR opened casey/intermodal

Release v0.1.9
  • Bump version: 0.1.8 → 0.1.9
  • Update dependencies
  • Publish to cargo as last step in publish recipe

type: release

+125 -107

0 comment

3 changed files

pr created time in 16 days

create barnchcasey/intermodal

branch : release

created branch time in 16 days

delete branch casey/intermodal

delete branch : gen-no-git

delete time in 16 days

PR merged casey/intermodal

Add `--no-git` flag to `gen all`

The flag skips steps whichr require a git checkout, currently only the changelog generator.

type: added

+29 -20

0 comment

4 changed files

casey

pr closed time in 16 days

push eventcasey/intermodal

Casey Rodarmor

commit sha 047b36639db7d6ed2e8c124618f8070987c3e5a6

Add `--no-git` flag to `gen all` The flag skips steps whichr require a git checkout, currently only the changelog generator. type: added

view details

push time in 16 days

PR opened casey/intermodal

Add `--no-git` flag to `gen all`

The flag skips steps whichr require a git checkout, currently only the changelog generator.

type: added

+29 -20

0 comment

4 changed files

pr created time in 16 days

create barnchcasey/intermodal

branch : gen-no-git

created branch time in 16 days

issue commentcasey/just

Allow an alternative runner for shebang tasks

Hmm, this is tricky. Just thinking out loud:

Passing shebang paths to cygpath is done so that shebang recipes can work on both Unix and Windows with Cygwin. (For a while, installing Cygwin was the only way to get Just working on Windows, which is why this feature assumes that it will be present.

I'd rather not switch the behavior of Just depending on whether or not cygpath is installed, since I think that would be confusing. Users might write justfiles that work when cygpath is not installed, but then break when they install cygpath.

One ideas is that if there are no forward slashes (/) in a path, cygpath isn't invoked. I think this is safe, because cygpath in this case cygpath will be a no-op anyways. This would allow you to just write windows paths in shebang recipes.

What do you think?

pfmoore

comment created time in 16 days

pull request commentcasey/just

powershell recipe autocomplete implementation

Definitely let me know if you need any help!

Insomniak47

comment created time in 16 days

pull request commentcasey/just

powershell recipe autocomplete implementation

Thanks for this! Completions are generated in a somewhat weird way. First, completions are generated by Clap, the command-line argument parser that Just uses. Then, they're modified in code to add recipe name completions.

There are tests which check that the completions on disk match the completions that are output by the code, so that they don't get out of sync.

In order to make the tests pass, the modifications to the PowerShell completions should be done here. If you're not comfortable with Rust, I can move the changes for you.

Either way, the whitespace/formatting changes should be reverted, to match what is output by Clap and keep the diff minimal.

Insomniak47

comment created time in 17 days

more