From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Fix doctype custom options
Date: Sat, 05 Oct 2024 11:20:51 -0400 [thread overview]
Message-ID: <FE65F4DDC78F2B315FB96729FCD5951F@eigenstate.org> (raw)
In-Reply-To: <6f9f6441-9413-409b-96e5-4f73cc42a8b7@sirjofri.de>
applied, thanks.
Quoth sirjofri <sirjofri+ml-9front@sirjofri.de>:
> Ping
>
> 01.10.2024 18:47:27 sirjofri <sirjofri+ml-9front@sirjofri.de>:
> > This fixes custom options fro doctype.
> >
> > For example: doctype -mpictures myfile.ms
> >
> > Without that fix, it will just output $1 instead of the custom option.
> >
> > sirjofri
> >
> > /rc/bin/doctype
> > - opt=$opt' $1'
> > + opt=$opt' '$1
>
prev parent reply other threads:[~2024-10-05 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 16:46 sirjofri
2024-10-05 13:20 ` sirjofri
2024-10-05 15:20 ` ori [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=FE65F4DDC78F2B315FB96729FCD5951F@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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).