all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: jgart <jgart@dismail.de>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Texinfo, Free Beer
Date: Sat, 06 Aug 2022 13:43:35 +0000	[thread overview]
Message-ID: <5fQ7uqkVOMe_sS0Ch-N5LSLJ2dTl9DOrnoDmP-RhWL3H3jTM-DCXuLVhqBGtHZHRi-16uDXLkKodWgEx_GfsjOXtCLRnQkW5OQPWuvu5bVU=@elenq.tech> (raw)
In-Reply-To: <20220806083001.GC4096@gac>

Hi,

------- Original Message -------
On Saturday, August 6th, 2022 at 3:30 PM, jgart <jgart@dismail.de> wrote:


> Hi Guixers,
>
> wdyt of having some modern TLDR entry in the cookbook for getting Guix neophytes up to par with texinfo?
>
> Since texinfo is the defacto markup for the GNU Guix project and we're not likely to change it any time soon,
> I was think we could have some distilled/TLDR docs for users who mostly write and consume markdown.
>
> I was thinking something along the lines of what chicken has for rubyists or pythonistas:
>
> https://wiki.call-cc.org/chicken-for-ruby-programmers
> https://wiki.call-cc.org/chicken-for-python-programmers
>
> "Texinfo for MDs"
>
> roptat started a TLDR Texinfo guide on the learnxinyminutes series*.
>
> Should we just improve on roptat's guide and link it in a Guix doc somewhere so
> that it is more discoverable or integrate/fork it or similar into our docs?
>
> Same way we have a Scheme crash course, we can have a Texinfo crash course?


I could use that!



  reply	other threads:[~2022-08-06 13:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 13:30 Texinfo, Free Beer jgart
2022-08-06 13:43 ` Ekaitz Zarraga [this message]
2022-08-09  9:22 ` pinoaffe
2022-08-09 23:03   ` jgart

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='5fQ7uqkVOMe_sS0Ch-N5LSLJ2dTl9DOrnoDmP-RhWL3H3jTM-DCXuLVhqBGtHZHRi-16uDXLkKodWgEx_GfsjOXtCLRnQkW5OQPWuvu5bVU=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.