edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] statically linked edbrowse executable for Linux is...
Date: Tue, 10 Jun 2014 10:53:06 -0400	[thread overview]
Message-ID: <20140510105306.eklhad@comcast.net> (raw)

Well this is just awesome!

A) Should you put a description and link in your edbrowse home page,
much like the email you sent around, explaining what it is and why?

B) Should I do the same in the users guide?
The only issue there is linkrot, and I already have
an uncomfortable number of links to external sources.
In theory a manual page shouldn't be pointing to things on the internet,
but mine does.

Yes I still use the perl version, I plopped it into my Wife's macbook
so I feel at home when I ssh in.
I would likely do the same for any computer I log into.

Karl Dahlke

             reply	other threads:[~2014-06-10 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10 14:53 Karl Dahlke [this message]
2014-06-10 16:53 ` Chris Brannon
2014-06-11  8:51   ` 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=20140510105306.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).