From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Images
Date: Mon, 28 Apr 2014 08:06:27 +0000 [thread overview]
Message-ID: <20140328080627.eklhad@comcast.net> (raw)
> I'm fairly used to brackets, I think this comes from when I used to browse the
> web with the links2 browser though so I don't mind.
Wow. I knew it looked familiar but couldn't remember why.
That was it.
Good, then this convention makes sense.
Although it doesn't come up very often because most images are clickable hyperlinks, hence the braces.
Well braces are sort of enhanced brackets, so again good.
I'll scan through and see if I documented this anywhere.
Karl Dahlke
next reply other threads:[~2014-04-28 12:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 8:06 Karl Dahlke [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-04-27 15:37 Karl Dahlke
2014-04-28 11:54 ` Adam Thompson
2014-04-28 15:29 ` Chris Brannon
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=20140328080627.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/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).