public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: How many of y'all use Emacspeak?
Date: Sat, 17 Jun 2017 12:59:49 -0400 (EDT)	[thread overview]
Message-ID: <alpine.NEB.2.20.1706171259020.7773@panix1.panix.com> (raw)
In-Reply-To: <df3b5921-186f-ffa6-5b05-0f3beb9c1949@gmail.com>

You don't have the following line in your .emacs file yet, that should 
fix it.

(setq browse-url-browser-function 'eww-browse-url)

On Sat, 17 Jun 2017, 
Linux for blind general discussion wrote:

> Date: Sat, 17 Jun 2017 12:16:31
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: Linux for blind general discussion <blinux-list@redhat.com>
> Subject: Re: How many of y'all use Emacspeak?
> 
>
> M-x browse-url <ret> just produces an error sound.
> On 06/17/2017 08:42 AM, Linux for blind general discussion wrote:
>> try mx-browse-url <cr> and see what happens.
>> On Fri, 16 Jun 2017, Linux for blind general discussion wrote:
>> 
>>> Date: Fri, 16 Jun 2017 20:46:39
>>> From: Linux for blind general discussion <blinux-list@redhat.com>
>>> To: Linux for blind general discussion <blinux-list@redhat.com>
>>> Subject: Re: How many of y'all use Emacspeak?
>>> 
>>> How do you get w3m to work? I've installed both w3m and emacs-w3m and 
>>> restarted emacs, but M-x w3m fails.
>>> 
>>> Which other email programs and browsers work with emacs? I've had no luck 
>>> with eww. It gives the error that function requires libxml2. I have 
>>> libxml2.
>>> 
>>> On 06/15/2017 04:40 AM, Linux for blind general discussion wrote:
>>>> I use speechd-el but I believe that's similar.
>>>> 
>>>> I manage my e-mail with gnus, Web with w3m, the dired mode, code editing, 
>>>> shell.
>>>> 
>>>> Rapha?l
>>>> On 06/14/2017 07:13 PM, Linux for blind general discussion wrote:
>>>>> It appears powerful and customizable and I'm interested in learning it
>>>>> despite the steep curve. The manual is also easy to read. For those of
>>>>> you who use it regularly, what are your favorite features?
>>>>> 
>>>>> _______________________________________________
>>>>> 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
>>> 
>>> _______________________________________________
>>> 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
>

-- 

  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
 ` Linux for blind general discussion
 ` Linux for blind general discussion
   ` Linux for blind general discussion
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion [this message]
     ` Linux for blind general discussion
       ` Linux for blind general discussion
         ` Linux for blind general discussion
     ` 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.NEB.2.20.1706171259020.7773@panix1.panix.com \
    --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).