From: Karl Dahlke <eklhad@comcast.net>
To: tspivey@pcdesk.net, edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Pre tag and |
Date: Sat, 11 May 2013 00:08:42 -0400 [thread overview]
Message-ID: <20130411000842.eklhad@comcast.net> (raw)
In-Reply-To: <518D340D.2040002@pcdesk.net>
There is some post-processing of pipes and spaces and braces,
to try to clean things up, which usually does the right thing,
but not always.
In format.c starting at line 403.
So yes an example with just spaces and pipes could come out funny.
Karl Dahlke
prev parent reply other threads:[~2013-05-11 4:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 17:53 Tyler Spivey
2013-05-11 4:08 ` Karl Dahlke [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=20130411000842.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=edbrowse-dev@lists.the-brannons.com \
--cc=tspivey@pcdesk.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).