edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] wiki v2
Date: Wed, 26 Feb 2014 16:58:48 +0000	[thread overview]
Message-ID: <20140226165848.GC6911@toaster.adamthompson.me.uk> (raw)
In-Reply-To: <20140126080618.eklhad@comcast.net>

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

On Wed, Feb 26, 2014 at 08:06:18AM -0500, Karl Dahlke wrote:
> Every now and then I pop back and fiddle with the wiki article,
> making some of the changes you suggested.
> I still think there should be some mention of the command line approach,
> as that was the seed for edbrowse, but as you say it is not the focus,
> so I have reduced it to a small paragraph;
> followed by an overview of the features as Adam suggested.

It definitely reads better now, and I think it's probably worth a shot at submiting it.

> I wanted to put features in a bullet list, and as best I could tell
> from their docs, that is done using traditional html.
> It's a weird markup: part html, part their own syntax,
> and part tags that look like html but aren't, like the tag
> <syntaxhighlight lang=c>
> which I think we're suppose to use when writing code
> similar to C code.
> Well I don't really know.

That sounds like a weird mess.  Well done for working it out.

> fortunately there is a button you can push that says <preview>,
> to see how it would look befure submitting it,
> so I can check all these guesses I am making in markup language and format.

Yeah.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-02-26 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-26 13:06 Karl Dahlke
2014-02-26 16:58 ` Adam Thompson [this message]
2014-02-27 21:07 ` Chris Brannon
2014-02-27 21:20 Karl Dahlke

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=20140226165848.GC6911@toaster.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.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).