From: jgarte <jgarte@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Request: Wiki or Cookbook
Date: Thu, 12 May 2022 02:17:27 +0200 [thread overview]
Message-ID: <20220512001727._ya6mPy_Zi57_0-yCcPe_NVHG5uixeXY0J-LLbvJstQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-227@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
New comment by jgarte on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/227#issuecomment-1124232506
Comment:
@leahneukirchen
Thanks!
Hopefully people who use mblaze regularly can share their tips and advice on it. Just reading the man page is not enough for me to learn a program unless I know it already to some degree or it's very trivial. I imagine also that only having a man page as a means of learning mblaze might not fit the learning styles of various individuals. This is where the wiki might prove useful and welcoming for those types of learners, atleast at the outset, before they dive into the man pages and/or source code.
For mblaze, I'd prefer to have various/extensive direct examples to get an idea for what the author's original intended regular use looks like.
Equipped with that knowledge, I can then find my own unique ways to use and compose other tools in the [Unix IDE](https://blog.sanctum.geek.nz/series/unix-as-ide/) with mblaze.
I'll try to add what I can to the [wiki](https://github.com/leahneukirchen/mblaze/wiki) given my current knowledge of mblaze.
prev parent reply other threads:[~2022-05-12 0:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 23:47 [ISSUE] " jgarte
2022-05-11 11:41 ` leahneukirchen
2022-05-11 19:58 ` [ISSUE] [CLOSED] " jgarte
2022-05-11 19:58 ` jgarte
2022-05-12 0:12 ` jgarte
2022-05-12 0:12 ` jgarte
2022-05-12 0:12 ` jgarte
2022-05-12 0:13 ` jgarte
2022-05-12 0:13 ` jgarte
2022-05-12 0:15 ` jgarte
2022-05-12 0:17 ` jgarte [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220512001727._ya6mPy_Zi57_0-yCcPe_NVHG5uixeXY0J-LLbvJstQ@z \
--to=jgarte@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).