From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: bookshare.org
Date: Fri, 23 Jun 2017 18:40:27 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1.1706231837570.2940@southernprince> (raw)
In-Reply-To: <8b453d26-9bc2-a8de-65a1-7121e59b70ce@gmail.com>
Hmm, that's odd. I dunno how that happened. Error should be corrected now.
Mark Peveto
Registered Linux user number 600552
Everything happens after coffee!
On Fri, 23 Jun 2017, Linux for blind general discussion wrote:
>
> Hey Mark, may I borrow that time machine? I'd like to revisit my vacation to
> San Diego and SF back in March.
>
> Emacs has Bookshare support but I haven't tested it yet. I'll do so and get
> back to you.
> On 06/23/2017 06:15 PM, Linux for blind general discussion wrote:
> > Mark P here.
> > What would a linux user use to access bookshare.org material?
> > Thanks.
> >
> >
> > in2014
> > Mark Peveto
> > Registered Linux user number 600552
> > Everything happens after coffee!
> >
> > _______________________________________________
> > Blinux-list mailing list
> > Blinux-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/blinux-list
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://www.redhat.com/mailman/listinfo/blinux-list
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
bookshare.org Linux for blind general discussion
` bookshare.org Linux for blind general discussion
` Linux for blind general discussion [this message]
` bookshare.org Linux for blind general discussion
` bookshare.org Linux for blind general discussion
` bookshare.org Linux for blind general discussion
` bookshare.org Linux for blind general discussion
` bookshare.org Linux for blind general discussion
` bookshare.org Linux for blind general discussion
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.DEB.2.21.1.1706231837570.2940@southernprince \
--to=blinux-list@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).