From: "James K. Lowden" <jklowden@speakeasy.net>
To: help-gnu-emacs@gnu.org
Subject: Re: c-fill-paragrpah for code, not just comments
Date: Fri, 14 Dec 2018 13:33:54 -0500 [thread overview]
Message-ID: <20181214133354.cfaee65f9d809acc547a43bb@speakeasy.net> (raw)
In-Reply-To: mailman.5695.1544736484.1284.help-gnu-emacs@gnu.org
On Thu, 13 Dec 2018 16:28:20 -0500
Ken Goldman <kgoldman@us.ibm.com> wrote:
> (The use case is auto-generated code that has to be pasted into a
> Word document and has a line length limit.)
Ah, so what you really want to do is format the code to fit the
allotted space. That's not "filling", which usually means to re-flow
the lines as prose.
I don't know the emacs answer. I think you'll find that GNU indent has
all the knobs you need, though.
--jkl
next parent reply other threads:[~2018-12-14 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5695.1544736484.1284.help-gnu-emacs@gnu.org>
2018-12-14 18:33 ` James K. Lowden [this message]
2018-12-13 21:28 c-fill-paragrpah for code, not just comments Ken Goldman
2018-12-14 7:35 ` Eli Zaretskii
2018-12-16 20:56 ` Philipp Stephani
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181214133354.cfaee65f9d809acc547a43bb@speakeasy.net \
--to=jklowden@speakeasy.net \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).