Package Details: comchan-bin 0.14.0-1

Git Clone URL: https://aur.archlinux.org/comchan-bin.git (read-only, click to copy)
Package Base: comchan-bin
Description: A blazingly fast minimal serial monitor with plotter TUI and more
Upstream URL: https://github.com/Vaishnav-Sabari-Girish/ComChan
Keywords: tui,embedded,uart,braille,wireframe,ratatui
Licenses: MIT
Conflicts: comchan
Provides: comchan
Submitter: vaishnav
Maintainer: vaishnav
Last Packager: vaishnav
Votes: 1
Popularity: 0.72
First Submitted: 2026-06-14 17:14 (UTC)
Last Updated: 2026-07-06 11:31 (UTC)

Latest Comments

vaishnav commented on 2026-06-15 07:49 (UTC)

Another tip.

If you decide later to have real man pages.But are not confortable writing them by hand. And still prefer markdown.

Description : Tool for generating roff manual pages URL : https://sr.ht/~sircmpwn/scdoc/

Extremely usefull, simple tool, very widely used.

Got it. Thank you. I'll look into it. I was planning man pages anyway. This helps a lot.

m040601 commented on 2026-06-15 06:15 (UTC) (edited on 2026-06-15 06:16 (UTC) by m040601)

Another tip.

If you decide later to have real man pages.But are not confortable writing them by hand. And still prefer markdown.

Description     : Tool for generating roff manual pages
URL             : https://sr.ht/~sircmpwn/scdoc/

Extremely usefull, simple tool, very widely used.

vaishnav commented on 2026-06-15 05:48 (UTC)

Yeah ... not an easy way, since you decided to structure the project this way.

You do say on the README to check the wiki, which is good.

Seems you want the wiki to be a "live" thing open to contributions.

My suggestion would be to just leave it that way.

Then everytime just before you do a release, just review, check aprove those wiki files. Simply copy and commit them to a "docs" folder on the main repo. Ship that in the tar.xz. That way end users would have a "authorative" fixed version of the docs on their computer. Guaranted and known to work with that specific release.

If they want something "fresher" online they go to the wiki.

Hm. Got it. Maybe I could symlink them somehow so that I do not need to manually update stuff. Lemme try that. Thank you for the advice.

m040601 commented on 2026-06-15 05:41 (UTC) 

... not able to add the docs since it is in GitHub wiki which is a separate git repository

Yeah ... not an easy way, since you decided to structure the project this way.

You do say on the README to check the wiki, which is good.

Seems you want the wiki to be a "live" thing open to contributions.

My suggestion would be to just leave it that way.

Then everytime just before you do a release, just review, check aprove those wiki files. Simply copy and commit them to a "docs" folder on the main repo. Ship that in the tar.xz. That way end users would have a "authorative" fixed version of the docs on their computer. Guaranted and known to work with that specific release.

If they want something "fresher" online they go to the wiki.

vaishnav commented on 2026-06-15 05:25 (UTC)

I have added the CHANGELOG.md. I was not able to add the docs since it is in GitHub wiki which is a separate git repository. If there is a way around that please do let me know. Thank you.

vaishnav commented on 2026-06-15 05:08 (UTC)

Thanks for the "-bin" PKGBUILD. You forgot the CHANGELOG.md

Oh you're right. I'll make that change real quick. Thank you for the heads-up

m040601 commented on 2026-06-15 03:47 (UTC)

Thanks for the "-bin" PKGBUILD. You forgot the CHANGELOG.md,

/usr/share/doc/comchan-bin/CHANGELOG.md