Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Aug 04 02:03
    matu3ba commented #8
  • Apr 19 17:59
    Dylan-DPC synchronize #58
  • Apr 19 17:59

    Dylan-DPC on master

    Fix README link (#162) (compare)

  • Apr 19 17:59
    Dylan-DPC closed #162
  • Apr 19 16:56
    feidtmb opened #162
  • Mar 25 12:56
    XAMPPRocky closed #146
  • Feb 06 18:33
    trevordmiller commented #161
  • Dec 12 2019 20:36
    stappersg commented #144
  • Dec 11 2019 12:53
    JohnTitor closed #144
  • Dec 11 2019 12:53
    JohnTitor commented #144
  • Dec 10 2019 13:17
    killercup transferred #154
  • Dec 08 2019 13:06
    spacekookie synchronize #58
  • Dec 08 2019 13:06

    spacekookie on master

    Clarify source position Make i… (compare)

  • Dec 08 2019 13:06
    spacekookie closed #159
  • Dec 07 2019 00:50
    Dylan-DPC added as member
  • Dec 07 2019 00:50
    spacekookie added as member
  • Dec 07 2019 00:50
    yoshuawuyts added as member
  • Dec 07 2019 00:50
    killercup added as member
  • Dec 07 2019 00:50
    Dylan-DPC removed as member
  • Dec 07 2019 00:50
    spacekookie removed as member
Daniel Sockwell
@codesections
What's the etiquette within CLIque for merging ones own PRs? I know some groups dislike that/want more code review but others like it to keep the pace of development up/avoid blockers
Pascal Hertleif
@killercup
@codesections don't think we have a specific etiquette established here, so let me come up with something: it's fine if the PRs implement what the core maintainers decided to do
Daniel Sockwell
@codesections
Makes sense :+1:
Pascal Hertleif
@killercup
which leads us to: who are the core maintainer of that repo? i'd propose you, @yoshuawuyts, and @Dylan-DPC who volunteered earlier :)
yes this is super informal and boils down to: best just have a quick chat about it and then get coding :)
Daniel Sockwell
@codesections
:) Sounds about right to me! I think though, that at least in the short term, there's no a whole lot that roff-rs needs to support the core work in man. So, unless anyone has particular features they'd like to see in roff-rs, I expect the majority of my time will be spent on man
It feels like man is very close to being usable for most CLI apps (even if better integration with clap would be great in a post-clap-3.0.0 world)
Pascal Hertleif
@killercup
sounds great!
(that reminds me to add the clique maintainers as owners of the crate on crates.io too. done)
Yoshua Wuyts
@yoshuawuyts
killercup: hi, yes — totally on board with having codesections on the project!
Input has been super helpful; I love that it's active again; never saw it through to the end, so happy it's getting there ^_^
Pascal Hertleif
@killercup
@yoshuawuyts great!
killercup @killercup is revising the CLIque 2019 roadmap to include "stick it to the man"
Ricky
@deg4uss3r
Any other rust cli nerds at LCA?
Pascal Hertleif
@killercup
i don't even know what that is :sweat_smile:
Daniel Sockwell
@codesections
^^^
Ricky
@deg4uss3r
Linux Conference Australia
Pascal Hertleif
@killercup
ah, okay, not the Life Cycle Initiative :D
Daniel Sockwell
@codesections
That sounds more fun than the Louisiana Correctional Association
Ricky
@deg4uss3r
lol probably a bit more @codesections
Pascal Hertleif
@killercup
maybe it's really just a bunch of people in front of a whiteboard finding the Lowest Common Ancestor in a graph 🤷‍♂️
Ricky
@deg4uss3r
plz2no
Daniel Sockwell
@codesections
Could we do a patch version bump on man sometime? I've been working on a CLI app that uses the example method we added to man, and I can't publish it on crates.io with man as a dependency from github
Pascal Hertleif
@killercup
@codesections I've only seen the amount of PRs you made, not read their contents but I'd be amazed if there was no breaking change in there :) also: you should have the rights to publish the crate
Daniel Sockwell
@codesections
Haha, fair enough. I don't have write access to the man repo, though, just to roff-rs
Dylan DPC
@Dylan-DPC
will publish a new verson in a few days
Daniel Sockwell
@codesections
Actually, nevermind about the version bump on my account. I didn't realize it had already bumped to 0.3.0 yesterday (which has the changes I need)
Daniel Sockwell
@codesections
(By the way, the reason I first got involved in making PRs to man was yak-shaving when I realized I needed a better way to write a man page for a tiny little CLI app I wanted to release. And I just released it earlier today: https://github.com/codesections/mnemonic. That doesn't mean I plan to stop working on man, but I just wanted to share :) )
Ed Page
@epage
Nice!
Daniel Sockwell
@codesections
Thanks
Ed Page
@epage
I can sympathize with yak shaving.
  • I wanted to learn Rust by replacing a regex-based lint tool in Rust
  • I wanted to blog but didn't want to deal with python or ruby blog software, so looked for a rust one
  • The static site generator needed features
  • I found the CLI story needed work and was excited to jump on board the CLI-WG when it was announced.
  • I've been writing tools for CLIs and not been working on my static site generator nor my regex-lint tool
Daniel Sockwell
@codesections
haha, that sounds about right! Which static site generator was it?
Ed Page
@epage
I maintain cobalt.
I might take a short break from CLI-WG stuff because I am very curious about applying an ECS to cobalt.
Daniel Sockwell
@codesections
Oh, I didn't realize that—very cool! I've been using the other main Rust SSG (Zola f/k/a Gutenberg) and have been pretty happy with it—but I keep meaning to check out Cobalt
Ed Page
@epage
Cobalt is older, Zola is further ahead in features. One theory I have is that Cobalt had adoption sooner which makes changes harder.
Daniel Sockwell
@codesections
Ed Page
@epage
Yes
The breakthrough for me was to realize its a fancy term for custom, native, in-memory databAses
with column-oriented tables
Daniel Sockwell
@codesections
Hmm, very interesting. Sounds related to an idea I've had bouncing around in the back of my mind for building a comment system for static sites. Might need to read more about this, thanks
Ed Page
@epage
CLI name brainstorm (naming is hard): For a long time, I've wanted to rewrite scspell (source code spell checker in python) in Rust for performance reasons. Name ideas?
(and yes, misspell's recent announcement finally motivated me to write this. I was contributing to it but some policies made it not worthwhile for me)
Daniel Sockwell
@codesections
What was their recent announcement? I must have missed that
Daniel Sockwell
@codesections
As far as naming goes, would it be targeted at Rust code? (I know misspell has a golang focus). If so, you could do something referencing rustfmt. rustspll, maybe?
or rustspl
Screwtapello
@Screwtapello
Wait, there's a spell-checker for Go, and they didn't call it "gospel"? What a missed opportunity.
Ed Page
@epage

https://www.reddit.com/r/rust/comments/agmpts/my_first_useful_rust_program_misspell_any/?st=jra2cf4b&sh=b67e2920
Didn't realize its a port of go.

Not Rust specific. I've been wanting this at $DAYJOB for a mostly C++/Python code base

Daniel Sockwell
@codesections
hmmm, naming is hard. How about rusty-speller? I think I'm too stuck on the "rust" rut, though and a better idea would drop that alltogether
Dylan DPC
@Dylan-DPC
or we could do a clippy and call it cortana :P