unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jacob Gerlach <jacobgerlach@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: fill-paragraph with pre and postfix
Date: Wed, 5 Nov 2014 07:18:07 -0500	[thread overview]
Message-ID: <CAA6UvuHH=Gtr6vFZfrT3riqDRjP9ap=OQaNC9ahQ4gE33hLPfw@mail.gmail.com> (raw)
In-Reply-To: <CAA6UvuGBeVzLqqvzY5E8DX7kuMtRiJBuP6-AORsrjPR1uuxTtg@mail.gmail.com>

---------- Forwarded message ----------
From: "Jacob Gerlach" <jacobgerlach@gmail.com>
Date: Nov 5, 2014 7:17 AM
Subject: Re: fill-paragraph with pre and postfix
To: "Alexis" <flexibeast@gmail.com>
Cc:


On Nov 5, 2014 6:42 AM, "Alexis" <flexibeast@gmail.com> wrote:
>
>
> Jacob Gerlach writes:
>
> > A project I'm working on uses a handling function for some command line
> > documentation:
> >
> >   blk("  I want to format my documentation like this.
");
> >
> > In order to match the convention for our project, it should include the
two
> > leading spaces and be filled with spaces out to column 70.
>
> Will the text that gets padded with spaces always be less than 70
> columns in total?

No, the idea is to use this function on a paragraph of text and have it
broken into appropriately sized lines and then wrapped with the format
function. Something akin to fill paragraph.
>
>
> Alexis.
>


  parent reply	other threads:[~2014-11-05 12:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05  3:00 fill-paragraph with pre and postfix Jacob Gerlach
2014-11-05 11:34 ` Alexis
     [not found]   ` <CAA6UvuGBeVzLqqvzY5E8DX7kuMtRiJBuP6-AORsrjPR1uuxTtg@mail.gmail.com>
2014-11-05 12:18     ` Jacob Gerlach [this message]
2014-11-06  3:45       ` Alexis
2014-11-10 15:24         ` Jacob Gerlach
2014-11-11  0:19           ` Alexis
     [not found]             ` <CAA6UvuEQYgVUkgWD_MkU_mnjYVt6PSXA72RSe9S2YOJmxnNOUg@mail.gmail.com>
2014-11-11  8:26               ` Alexis
2014-11-24 19:26                 ` Jacob Gerlach
2014-11-26  8:48                   ` Alexis

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='CAA6UvuHH=Gtr6vFZfrT3riqDRjP9ap=OQaNC9ahQ4gE33hLPfw@mail.gmail.com' \
    --to=jacobgerlach@gmail.com \
    --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).