From: kvik@a-b.xyz
To: 9front@9front.org
Subject: Re: [9front] Re: [Patch] Re: fmt Re: with Re: line Re: prefixes.
Date: Wed, 30 Oct 2019 23:16:02 +0100 [thread overview]
Message-ID: <279D29B18A7F8746F3E700AECD8E0BBC@a-b.xyz> (raw)
In-Reply-To: 2E7A6A1C7EC2C64348910B4B518151DE@eigenstate.org
I think this is a great feature.
> (regex prefixes?)
Regex prefixes would be a dream for source code comments
where you have a variable amount of prefix whitespace, esp.
for more complex forms like the classic C style:
/*
* I'm a comment.
* AMA.
*/
fmt -p '[ ]* ?(/\*|\*|\*/) ?'
--
kvik
reply other threads:[~2019-10-30 22:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=279D29B18A7F8746F3E700AECD8E0BBC@a-b.xyz \
--to=kvik@a-b.xyz \
--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).