zsh-workers
 help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh Workers List <zsh-workers@zsh.org>
Subject: Re: Dead Link on page http://zsh.sourceforge.net/Intro/
Date: Fri, 20 Dec 2019 14:42:58 -0600	[thread overview]
Message-ID: <74A68EE7-0253-4EE7-BEAE-5E4DE0D64522@dana.is> (raw)
In-Reply-To: <20191220201422.ki4xufghzh2ahh77@tarpaulin.shahaf.local2>

On 20 Dec 2019, at 14:14, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> The href attributes need leading slashes, else they'd be broken.

Oops, copy/paste errors from the other links i guess. Thanks

On 20 Dec 2019, at 14:14, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> The workshop was written when version 3.1.5 was current....
> This link is also broken («wget: unable to resolve host address
> ‘a.gp.cs.cmu.edu’»), and in any case, when was it last updated?  We should
> be linking to current documentation.

Yeah, the release script mentions that the texi file is no longer available,
so the HTML doesn't get updated. The PostScript version is generated from
intro.ms in the main repo, but, with one very small exception (workers/30430),
that file hasn't been touched in 20+ years either, so...

Like i said, they are *all* extremely out-of-date. Much of the basic stuff
still applies, but i don't think i'd personally use or recommend any of these
documents. Just thought we might err on the side of caution, as Peter
(basically) suggested. If there's a more recent document that can serve as an
introduction, we can use that, but i'm not aware of anything myself. Or, if
you guys prefer, we can just get rid of the entire page, idk

dana


  reply	other threads:[~2019-12-20 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 16:03 Glenn Travis
2019-12-18 22:14 ` dana
2019-12-19  9:34   ` Peter Stephenson
2019-12-20  6:35     ` dana
2019-12-20 20:14       ` Daniel Shahaf
2019-12-20 20:42         ` dana [this message]
2020-01-16  1:51           ` dana
2020-01-16  4:34             ` Bart Schaefer

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=74A68EE7-0253-4EE7-BEAE-5E4DE0D64522@dana.is \
    --to=dana@dana.is \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).