From: Jude DaShiell <jdashiel@panix.com>
To: Skip Montanaro <skip.montanaro@gmail.com>,
Jamie Beardslee <jdb@jamzattack.xyz>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: gopher from Emacs
Date: Thu, 17 Sep 2020 23:08:46 -0400 [thread overview]
Message-ID: <alpine.NEB.2.23.451.2009172307420.20502@panix1.panix.com> (raw)
In-Reply-To: <CANc-5Uxc+CgORQBbjjkzySRe0Wwk++M8sfDP9N9J5hDJuAq2_A@mail.gmail.com>
It's still a thing, and it forgot to get inaccessible too. Use a screen
reader with gopher you'll have much better luck than with html in many
cases.
On Thu, 17 Sep 2020, Skip Montanaro wrote:
> Date: Thu, 17 Sep 2020 21:08:16
> From: Skip Montanaro <skip.montanaro@gmail.com>
> To: Jamie Beardslee <jdb@jamzattack.xyz>
> Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
> Subject: Re: gopher from Emacs
>
> > There are two gopher clients for emacs, neither of which are builtin.
> >
> > http://thelambdalab.xyz/elpher
> >
> > https://github.com/ardekantur/gopher.el
>
> Wow... I didn't know gopher was still a thing.
>
> Skip
>
>
--
next prev parent reply other threads:[~2020-09-18 3:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 22:01 gopher from Emacs Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-18 0:12 ` Jamie Beardslee
2020-09-18 1:08 ` Skip Montanaro
2020-09-18 1:53 ` 황병희
2020-09-18 2:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-18 3:08 ` Jude DaShiell [this message]
2020-09-18 1:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-18 3:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-18 3:36 ` Jamie Beardslee
2020-09-18 3:56 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-18 7:24 ` Iñigo Serna
2020-09-28 0:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-28 0:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=alpine.NEB.2.23.451.2009172307420.20502@panix1.panix.com \
--to=jdashiel@panix.com \
--cc=help-gnu-emacs@gnu.org \
--cc=jdb@jamzattack.xyz \
--cc=skip.montanaro@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.