9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Brdline() and continuation lines
Date: Wed, 19 Sep 2012 14:49:25 +0100	[thread overview]
Message-ID: <CAOw7k5g4JEeevnc2zY0yKFDfMA4LLETvPETOnHurp9QYoKgeXQ@mail.gmail.com> (raw)
In-Reply-To: <22e43e02e32dd37beb7f8c52105e45b6@quintile.net>

[-- Attachment #1: Type: text/plain, Size: 239 bytes --]

I don't see how it can do it.

On 19 September 2012 09:48, Steve Simon <steve@quintile.net> wrote:

> I am happy if the answer is "Brdline() cannot do this", I just feel like
> I am missing a trick, and there is elegant solution.
>

[-- Attachment #2: Type: text/html, Size: 519 bytes --]

      parent reply	other threads:[~2012-09-19 13:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19  8:48 Steve Simon
2012-09-19 13:35 ` erik quanstrom
2012-09-19 13:49 ` Charles Forsyth [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=CAOw7k5g4JEeevnc2zY0yKFDfMA4LLETvPETOnHurp9QYoKgeXQ@mail.gmail.com \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    /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).