From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: info-gnus-english@gnu.org
Subject: Re: rss, links and external browser
Date: Wed, 6 Aug 2008 07:23:13 -0700 (PDT) [thread overview]
Message-ID: <c292cc4e-43e4-4b96-9e1a-ef272e026aad@s50g2000hsb.googlegroups.com> (raw)
In-Reply-To: <b4mvdyextnb.fsf@jpl.org>
Hi!
On Aug 6, 1:36 pm, Katsumi Yamaoka <yama...@jpl.org> wrote:
> Hm, do you use emacs-w3m that is really recent? I tried
> `fc-choose-browser' and didn't reproduce such an odd behavior.
Okay, my fault. I thought my debian testing would have a fairly
new version. Now, I installed the tar.gz you suggested in your
first email. Works :)
> > Another question: Where did you find this information?
[...]
> > Customizability (is this a word ? ;) is as much a gift as a curse ;)
> Sorry for inconvenience. We emacs-w3m team don't have enough
> capability and time.
Oh no! This was not meant to be a reproach. I just try to improve my
method. It is often suggested to use information included in emacs and
not search the web. Lots of stuff out there is outdated. I could not
find anything and so thought I did not search carefully enough.
Only question left is why emacs suddenly thinks every single
link is unsecure and keeps asking me if I really want to
visit it, using prefix argument.
w3m-safe-url-regexp is nil, so AFAI understand it, this should not
happen. But leave this to me ;) This is a nice little training to
learn how to get around ;)
thanks!
memnon
prev parent reply other threads:[~2008-08-06 14:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 15:26 Memnon Anon
2008-08-06 1:03 ` Katsumi Yamaoka
2008-08-06 10:27 ` Memnon Anon
2008-08-06 11:36 ` Katsumi Yamaoka
2008-08-06 14:23 ` Memnon Anon [this message]
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=c292cc4e-43e4-4b96-9e1a-ef272e026aad@s50g2000hsb.googlegroups.com \
--to=gegendosenfleisch@googlemail.com \
--cc=info-gnus-english@gnu.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.
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).